on 6-21-2009 2:31 AM Kai Schaetzl spake the following:
Barry Brimer wrote on Sat, 20 Jun 2009 22:51:44 -0500 (CDT):
Many years ago I used portsentry for this. You can find an article about
portsentry at http://www.securityfocus.com/infocus/1580
and can be downloaded here:
Barry Brimer wrote on Sat, 20 Jun 2009 22:51:44 -0500 (CDT):
Many years ago I used portsentry for this. You can find an article about
portsentry at http://www.securityfocus.com/infocus/1580
and can be downloaded here:
http://sourceforge.net/project/showfiles.php?group_id=80573
Kai
--
Kai
Bob Hoffman b...@... writes:
So I have been reading the ssh attack thread and finally want to ask about
something.
I doubt there is a program like this, but I would love to have a program
that listens at common ports that I do not use at all...and only allow that
program to listen to it,
On Sun, Jun 21, 2009 at 1:03 AM, Joseph L.
Casalejcas...@activenetwerx.com wrote:
Very carefully...
Lol, you missed the point. It's impossible. I was bluntly suggesting the
reply was not applicable nor on topic to the op's post. Port scanning
and packet sniffing have nothing to do with each
So I have been reading the ssh attack thread and finally want to ask about
something.
I doubt there is a program like this, but I would love to have a program
that listens at common ports that I do not use at all...and only allow that
program to listen to it, especially the usual ssh port (using
On Sat, 20 Jun 2009 20:35:00 -0400
Bob Hoffman wrote:
So...does something like this exist?
fail2ban
--
MELVILLE THEATRE ~ Melville Sask ~ http://www.melvilletheatre.com
___
CentOS mailing list
CentOS@centos.org
In other words, anyone hitting those ports that are not being used at all
except by our sniff protector, would allow instant banning.
So...does something like this exist?
I don't know of a program that specifically listens to defined ports and
acts on that, but fail2ban would accomplish the end
However if you are referring to packet sniffers there is no solid way of
blocking them.
On Sun, Jun 21, 2009 at 3:49 AM, Joseph L. Casale jcas...@activenetwerx.com
wrote:
In other words, anyone hitting those ports that are not being used at all
except by our sniff protector, would allow
However if you are referring to packet sniffers there is no solid way of
blocking them.
How exactly would I sniff the packets from say my work computer between
someone's home computer and work server?
___
CentOS mailing list
CentOS@centos.org
On Sat, Jun 20, 2009 at 10:38 PM, Joseph L.
Casalejcas...@activenetwerx.com wrote:
However if you are referring to packet sniffers there is no solid way of
blocking them.
How exactly would I sniff the packets from say my work computer between
someone's home computer and work server?
On Sat, Jun 20, 2009 at 8:35 PM, Bob Hoffmanb...@bobhoffman.com wrote:
So I have been reading the ssh attack thread and finally want to ask about
something.
I doubt there is a program like this, but I would love to have a program
that listens at common ports that I do not use at all...and
That program would then, upon receiving a 'sniff' or 'user' would then add
that ip to the deny hosts lists..for either a long or short time.
Using this would seem like a win as you can easily grab someone before they
can get somewhere one hopes.
Also, by opening up a few other ports
I doubt there is a program like this, but I would love to have a program
that listens at common ports that I do not use at all...and only allow that
program to listen to it, especially the usual ssh port (using a different
one for real ssh)...
That program would then, upon receiving a
13 matches
Mail list logo
