Ethical Hacking Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package. | Computer Forensics Training at InfoSec Institute Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors. |

| Subject: | Re: [Full-disclosure] SSH brute force blocking tool |
|---|---|
| Date: | Tue, 28 Nov 2006 11:08:21 -0500 |
On Tue, Nov 28, 2006 at 10:56:33AM -0500, J. Oquendo wrote:Right... And as I stated on a different post... If an inexperienced admin allows that, it is on them. My attempt at making what I NEEDED and thought was helpful succeeded. If someone wants to nc insert arbitrary addresses, so be it. No different that someone spoofing random addresses at a firewall. What are you going to do, sift through every single address touching your network. Heck for what you just claimed "An attacker can still add arbitrary hosts to the deny list. ... it is not sufficient" ... TCP/IP is not sufficient with all of its issues. Give me a break
Incorrect did you look at the fix? It isn't unsanitized as you state:
J, you have made an attempt to fix it, but is is not sufficient.
An attacker can still add arbitrary hosts to the deny list.
Thanks, Tavis.
The happiness of society is the end of government. John Adams
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.grok.org.uk/full-disclosure-charter.html Hosted and sponsored by Secunia - http://secunia.com/
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [Full-disclosure] Sasser, ericscher@mac.com |
|---|---|
| Next by Date: | Re: [Full-disclosure] SSH brute force blocking tool, J. Oquendo |
| Previous by Thread: | Re: [Full-disclosure] SSH brute force blocking tool, Thierry Zoller |
| Next by Thread: | Re: [Full-disclosure] SSH brute force blocking tool, daylasoul |
| Indexes: | [Date] [Thread] [Top] [All Lists] |