Re: Following the upgrade to 6.8, sshguard is reporting that it fails to start

2020-10-28 Thread Daniel Jakots
On Wed, 28 Oct 2020 16:53:03 -0500, Todd wrote: > Following the upgrade to 6.8, rcctl is reporting that sshguard fails > to start. > > rcctl check sshguard > sshguard(failed) > [...] > apu$ rcctl get sshguard > > > sshguard_class=daemon >

Following the upgrade to 6.8, sshguard is reporting that it fails to start

2020-10-28 Thread Todd
I have been using the sshguard package for the last several releases. Following the upgrade to 6.8, rcctl is reporting that sshguard fails to start. rcctl check sshguard sshguard(failed) Below is the relevant information I can think of to provide. Are there additional troubleshooting

Re: sshguard

2012-07-27 Thread Chris Lobkowicz
Hmm, good point. I hadn't considered the potential issues at upgrade time. Thanks for pointing that out and saving me significant frustration in November. On 27/07/2012 03:04, Stuart Henderson wrote: > Editing scripts in /etc/rc.d will give you problems at upgrade time. > I don't know where else w

Re: sshguard

2012-07-27 Thread Stuart Henderson
On 2012-07-25, Chris Lobkowicz wrote: > > sshguard prefers to use the "log-sucker" way of parsing authlog. I don't > even have a mention of sshguard in syslog.conf. This is still using the "log-sucker" method, just on standard input rather than a file. > th

Re: sshguard

2012-07-26 Thread obsd
SshGuard are just a layer of the onion. Not the sole solution. Most methods you can, with certain degrees of effort and stubbornness, circumvent or break. /hasse -Ursprungligt meddelande- Från: owner-m...@openbsd.org [mailto:owner-m...@openbsd.org] För David Diggles Skickat: den 26 juli

Re: sshguard

2012-07-25 Thread David Diggles
the syslog behaving in a certain way under all conditions! On Wed, Jul 25, 2012 at 09:50:40AM -0600, Chris Lobkowicz wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > sshguard prefers to use the "log-sucker" way of parsing authlog. I don't > even

Re: sshguard

2012-07-25 Thread obsd
-Ursprungligt meddelande- Från: owner-m...@openbsd.org [mailto:owner-m...@openbsd.org] För Chris Lobkowicz Skickat: den 26 juli 2012 01:26 Till: misc@openbsd.org Ämne: Re: sshguard I use both. Sshguard seems to catch a lot, and the subsequent pf ruleset for max-src-conn seems to catch a

Re: sshguard

2012-07-25 Thread Chris Lobkowicz
I use both. Sshguard seems to catch a lot, and the subsequent pf ruleset for max-src-conn seems to catch a fair bit as well. Here is a snip of my pf.conf: # SSHguard protection table persist block in quick on em0 proto tcp from to any port ssh label "sshguard" # Bruteforce Protec

Re: sshguard

2012-07-25 Thread obsd
-Ursprungligt meddelande- Från: owner-m...@openbsd.org [mailto:owner-m...@openbsd.org] För Otto Moerbeek Skickat: den 25 juli 2012 16:05 Till: Hasse Hansson Kopia: misc@openbsd.org Ämne: Re: sshguard On Wed, Jul 25, 2012 at 02:25:44PM +0200, Hasse Hansson wrote: > Hello all. > # un

Re: sshguard

2012-07-25 Thread obsd
-Ursprungligt meddelande- Från: owner-m...@openbsd.org [mailto:owner-m...@openbsd.org] För Otto Moerbeek Skickat: den 25 juli 2012 16:05 Till: Hasse Hansson Kopia: misc@openbsd.org Ämne: Re: sshguard On Wed, Jul 25, 2012 at 02:25:44PM +0200, Hasse Hansson wrote: > Hello all. > # un

Re: sshguard

2012-07-25 Thread Alvaro Mantilla Gimenez
Is it a better solution than pf rules based on max-src-conn and/or max-src-conn-rate? According to the documentation sshguard add ip address to tablesowhat about if I want to "selectively" block ip address to some services and let other services open? (i.e.: one ip offending

Re: sshguard

2012-07-25 Thread Chris Lobkowicz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 sshguard prefers to use the "log-sucker" way of parsing authlog. I don't even have a mention of sshguard in syslog.conf. the rc script just basically daemonises sshguard, and points it at /var/log/authlog # /etc/rc.d/sshguard daemon=&

Re: sshguard

2012-07-25 Thread Otto Moerbeek
On Wed, Jul 25, 2012 at 02:25:44PM +0200, Hasse Hansson wrote: > Hello all. > # uname -a > OpenBSD odin.thorshammare.org 5.2 GENERIC#13 i386 > > sshguard-1.5 > Are we not supposed to use the entry in /etc/syslog.conf any more ? > " auth.info;authpriv.info

sshguard

2012-07-25 Thread Hasse Hansson
Hello all. # uname -a OpenBSD odin.thorshammare.org 5.2 GENERIC#13 i386 sshguard-1.5 Are we not supposed to use the entry in /etc/syslog.conf any more ? " auth.info;authpriv.info |/usr/local/sbin/sshguard " I get a message on my console saying: syslogd: unknown priority