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: | Mon, 27 Nov 2006 21:21:38 +0000 |
On Mon, Nov 27, 2006 at 04:12:11PM -0500, J. Oquendo wrote:
So again dumbass... Look at the script. Although YOU'RE opening /var/log/authlog what is the script opening.
I'm opening authlog as I dont use secure, the same thing applies.
Please tell me you're really not that stupid. And if someone else decided to modify this script, what does that have to do with what I posted. How exactly is my script a backdoor as you claim.
It's a backdoor because your script doesnt account for out-of-order log entries, usernames or other data containing spaces thus making your field count incorrect, or other daemons using the string `error retrieving` in their log entries. The insecure temporary file creation allows a local user to add entries to the passwd file (for example), or create or modify any file as root. Although it doesnt directly allow them to control the data the fileis created with, combined with the other flaw this is possible. Even without the other flaw, the existence of some files is a problem, such as /etc/.nologin. the test -e and rm is insufficient, firstly as it's a race condition, and secondly as test -e will return 1 on broken (sometimes called dangling) symlinks.
Enquiring minds want to know this since you claim its a backdoor. Please tell me outside of your modification how this is going to backdoor someone.
I'm not sure what you mean by modification, I simply subsituted the name for the logfile I use. Thanks, Tavis. -- ------------------------------------- taviso@sdf.lonestar.org | finger me for my pgp key. -------------------------------------------------------
pgpF6Whw2cs2x.pgp
Description: PGP 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/
| Previous by Date: | Re: [Full-disclosure] SSH brute force blocking tool, gabriel rosenkoetter |
|---|---|
| Next by Date: | Re: [Full-disclosure] SSH brute force blocking tool, J. Oquendo |
| Previous by Thread: | Re: [Full-disclosure] SSH brute force blocking tool, J. Oquendo |
| Next by Thread: | Re: [Full-disclosure] SSH brute force blocking tool, J. Oquendo |
| Indexes: | [Date] [Thread] [Top] [All Lists] |