Andrew Gould wrote:
Yes, it's probably time to move to certificates. Thanks for the suggestion.
If you realize this, then you also want to look at devising an
allow-allow-deny_by_default approach for other critical protocols that
you can't employ certificates for...
Instead of blocking huge
What information should I send to an ab...@* address when reporting a
break-in attempt?
My logs show a dictionary attack of invalid user names against port 22. I
obtained an ab...@* email address using 'whois' and reported the beginning
and ending date/times and the originating IP address.
Is
My logs show a dictionary attack of invalid user names against port 22. I
obtained an ab...@* email address using 'whois' and reported the beginning
and ending date/times and the originating IP address.
Is there any other information I need to send?
i don't think so.
anyway - if all password
On Feb 19, 2009, at 12:00 PM, Andrew Gould wrote:
What information should I send to an ab...@* address when reporting a
break-in attempt?
My logs show a dictionary attack of invalid user names against port
22.
So source of these is almost always some other compromised Unix-like
system.
From: Andrew Gould andrewlylego...@gmail.com
What information should I send to an ab...@* address when reporting a
break-in attempt?
My logs show a dictionary attack of invalid user names against port 22. I
obtained an ab...@* email address using 'whois' and reported the beginning
and
On Thu, Feb 19, 2009 at 2:01 PM, GESBBB ges...@yahoo.com wrote:
From: Andrew Gould andrewlylego...@gmail.com
What information should I send to an ab...@* address when reporting a
break-in attempt?
My logs show a dictionary attack of invalid user names against port 22.
I
obtained an
