On 27 November 2012 23:25, Aleksandr Miroslav wrote:
> Finally got sick of seeing tons of ssh break-in attempts in my logs. Am
> considering using denyhosts, or fail2ban. Anyone have any experience
> with these?
>
> I'm already using the AllowUsers facility of ssh to only al
On 11/27/12 22:25, Aleksandr Miroslav wrote:
Finally got sick of seeing tons of ssh break-in attempts in my logs. Am
considering using denyhosts, or fail2ban. Anyone have any experience
with these?
I'm already using the AllowUsers facility of ssh to only allow specific
users in, so I&
> From owner-freebsd-questi...@freebsd.org Tue Nov 27 16:26:46 2012
> Date: Tue, 27 Nov 2012 17:25:08 -0500
> Subject: denyhosts, fail2ban, or something else?
> From: Aleksandr Miroslav
> To: freebsd-questions@freebsd.org
>
> Finally got sick of seeing tons of ssh break-i
Hi,
On 27.11.2012 23:25, Aleksandr Miroslav wrote:
[...]
Finally got sick of seeing tons of ssh break-in attempts in my logs. Am
considering using denyhosts, or fail2ban. Anyone have any experience
with these?
I'm already using the AllowUsers facility of ssh to only allow specific
users i
> Finally got sick of seeing tons of ssh break-in attempts in my logs.
I invoke sshd from inetd with limit 3 connections/min in /etc/inetd.conf:
ssh stream tcp nowait/0/3 root/usr/sbin/sshd sshd -i -4
___
freebsd-questions@freebsd.or
On Tue, Nov 27, 2012 at 3:25 PM, Aleksandr Miroslav
wrote:
> Finally got sick of seeing tons of ssh break-in attempts in my logs. Am
> considering using denyhosts, or fail2ban. Anyone have any experience
> with these?
>
> I'm already using the AllowUsers facility of ssh to
Finally got sick of seeing tons of ssh break-in attempts in my logs. Am
considering using denyhosts, or fail2ban. Anyone have any experience
with these?
I'm already using the AllowUsers facility of ssh to only allow specific
users in, so I'm not overly concerned about the attempts.
Thi
On 5/3/11 2:32 PM, Janos Dohanics wrote:
>> Denyhosts has to be informed that the logfile has changed, so that
>> it can close and re-open the logfile. It may be possible by
>> sending it a 'signal', or you may have to kill/restart it. See
>> the documentati
On Tue, 3 May 2011 13:03:25 -0500 (CDT)
Robert Bonomi wrote:
> > From owner-freebsd-questi...@freebsd.org Tue May 3 12:17:12 2011
> > Date: Tue, 3 May 2011 12:40:37 -0400
> > From: Janos Dohanics
> > To: freebsd-questions@freebsd.org
> > Subject: /etc/newsyslog.c
What is the correct way to rotate denyhosts log files?
In /etc/newsyslog.conf I have:
/var/log/denyhosts 644 12 * $M1D0
JC /var/run/denyhosts.pid
However, denyhosts does not log in the new file.
--
Janos Dohanics
Glenn Sieb a écrit :
Nevermind :) I think I solved the issue.
Thanks anywho :)
Best,
--Glenn
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
"[EMAIL PROTECTED
Nevermind :) I think I solved the issue.
Thanks anywho :)
Best,
--Glenn
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Greetings!
Running:
7.0-STABLE FreeBSD 7.0-STABLE #27: Thu Apr 10 02:51:13 EDT 2008 amd64
DenyHosts 2.6_1
The suggested setup of using this stanza in /etc/hosts.allow does not
seem to work:
# Wrapping sshd(8) is not normally a good idea, but if you
# need to do it, here's how
> On December 09, 2007 at 12:14PM Andy Dills wrote:
> Not sure where that random /sshd came from, but the "line 1" bit is a
> pretty big hint as to where the problem is ;)
>
> Andy
I wondered about that to; however, until today, I have never even opened that
file. I have no idea where if came f
On Sun, 9 Dec 2007, Gerard wrote:
> I just installed 'denyhosts' on a FBSD-6.2 machine. I thought I had followed
> the directions correctly, however, I continually see an error message popping
> up on the screen. This is a line fro the /var/log/auth.log file.
>
>
>
I just installed 'denyhosts' on a FBSD-6.2 machine. I thought I had followed
the directions correctly, however, I continually see an error message popping
up on the screen. This is a line fro the /var/log/auth.log file.
Dec 9 10:56:01 scorpio sshd[1477]: warning: /etc/hosts.all
ort 47566 ssh2 Jun 17
>> 19:56:03 lists sshd[8081]:
>
> Of course, you have root logins via ssh disabled anyway.. right? ;)
Of course! But thanks for checking :) I see that denyhosts is blocking
hosts so I sleep better now :)
Zbigniew Szalbot
On Mon, 18 Jun 2007 07:51:23 +0200
Zbigniew Szalbot <[EMAIL PROTECTED]> wrote:
> Failed password for root from 218.9.127.236 port 47414 ssh2 Jun 17
> 19:56:00 lists sshd[8079]:
> Failed password for root from 218.9.127.236 port 47566 ssh2 Jun 17
> 19:56:03 lists sshd[8081]:
Of course, you have
On Sunday 17 June 2007, Zbigniew Szalbot said:
> Hello,
>
> I have denyhosts set with the following options:
>
> DENY_THRESHOLD_INVALID = 3
> DENY_THRESHOLD_VALID = 3
>
> In my understanding this should block all ssh login attempts from a
> host which fails to provide
Hello,
I have denyhosts set with the following options:
DENY_THRESHOLD_INVALID = 3
DENY_THRESHOLD_VALID = 3
In my understanding this should block all ssh login attempts from a host
which fails to provide correct login credentials 3 times (no matter if
the user actually exists or not at my
Richard Lynch wrote:
> I thought the security/denyhosts port looked good, even if just to
> slim down that report I get every day about the hundreds of SSH
> attempts...
>
> And, hey, reporting back to denyhosts HQ and letting them notify the
> sysadmins of hacked boxen is a
I thought the security/denyhosts port looked good, even if just to
slim down that report I get every day about the hundreds of SSH
attempts...
And, hey, reporting back to denyhosts HQ and letting them notify the
sysadmins of hacked boxen is a lot better than me doing it by hand.
Only problem is
Daniel Bye wrote:
On Thu, Sep 28, 2006 at 05:22:43PM +0100, Robin Becker wrote:
I'm trying to get denyhosts-2.5 to work in 6.0 and have inserted a line in
hosts.allow
ALL: xxx.myoffice.com : allow
sshd: /etc/hosts.deniedssh : deny
ALL: ALL : allow
but am finding that this causes my ho
On Thu, Sep 28, 2006 at 05:22:43PM +0100, Robin Becker wrote:
> I'm trying to get denyhosts-2.5 to work in 6.0 and have inserted a line in
> hosts.allow
>
>
> ALL: xxx.myoffice.com : allow
> sshd: /etc/hosts.deniedssh : deny
> ALL: ALL : allow
>
> but am findin
I'm trying to get denyhosts-2.5 to work in 6.0 and have inserted a line in
hosts.allow
ALL: xxx.myoffice.com : allow
sshd: /etc/hosts.deniedssh : deny
ALL: ALL : allow
but am finding that this causes my home ip to be denied even though I log in
with a pre-shared key.
The
On 4/25/06, David Stanford <[EMAIL PROTECTED]> wrote:
> Hello all,
>
> So I've recently just installed
> DenyHosts<http://denyhosts.sourceforge.net/>on my FreeBSD
> 6.1-RC box and can't, for the life of me, get this daemon to start on boot.
> I installed ver
Daniel,
Much thanks, you're the man! Actually, I initially installed it from ports
(ver. 2.2) and was having the same problem. I then went onto the DenyHosts
website and read the changelog for 2.3 which stated "daemon-control-dist
should now behave correctly on FreeBSD systems".
On Monday 24 April 2006 19:29, David Stanford wrote:
> Hello all,
>
> So I've recently just installed
> DenyHosts<http://denyhosts.sourceforge.net/>on my FreeBSD
> 6.1-RC box and can't, for the life of me, get this daemon to start on boot.
> I installed version 2
Hello all,
So I've recently just installed
DenyHosts<http://denyhosts.sourceforge.net/>on my FreeBSD
6.1-RC box and can't, for the life of me, get this daemon to start on boot.
I installed version 2.4b using the setup.py script. I'e moved daemon-control
to /usr/local/bin
Robin Becker wrote:
> I'm trying out the denyhosts port; it starts up and performs as expected,
> but it won't recognize a running instance as this python if test fails.
> Is there a more freebsd way for python to find out if a given process is
> running?
>
> if o
Robin Becker on 2006-02-22 10:08:14 +:
> I'm trying out the denyhosts port; it starts up and performs as expected,
> but it won't recognize a running instance as this python if test fails. Is
> there a more freebsd way for python to find out if a given process is
>
I'm trying out the denyhosts port; it starts up and performs as expected,
but it won't recognize a running instance as this python if test fails. Is there
a more freebsd way for python to find out if a given process is running?
if os.access(os.path.join("/proc"
32 matches
Mail list logo
