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] Linux big bang theory.... |
|---|---|
| Date: | Mon, 21 May 2007 12:59:07 -0400 |
On Sun, 2007-05-13 at 23:07 -0700, Andrew Farmer wrote:I've added a function to hide the script from showing up on Samhain
This script really doesn't prove anything, though. All it shows is that a compromised machine can be difficult to impossible to clean properly - which has been known for a *long* time. Ken Thompson discussed a much cleverer one in "Trusting Trust". It's also worth noting that this is in no way specific to UNIX systems. It's simply an unalterable fact that, once an attacker has had full access to the machine, it's possible for them to make changes which will allow them reentry at a later date.
I don't have (and I doubt anybody around here can) the proof to make this a theorem, but it is a good postulate:
- It is impossible to prove the integrity of a computing system from within the same system.
In olden days, this created the fundamental rules for systems like Tripwire: place the signatures on non-alterable storage, run tripwire in single user mode (ahh, the naive assumption that single user mode would be safe enough).
Today, the preferred method of checking the integrity of a system involves virtualisation of said system, and verification from the hosting component of the hosted one. Or the hammer approach of erasing the state of the system after use, and rolling it back to a "proven" safe and stable one.
What is does when run now is look for the instance of its name (the backdoor's name) and rename it to Samhain. So if the file created is called foo.h and Samhain logs it, it will go and rename foo.h in the logs to Samhain. Tripwire is no difference unless both logs are kept offline. On a side note, I started tinkering with a triple threat mechanism of checksums: (SHA1 + MD5 + RIPE160)
http://www.infiltrated.net/scripts/saki.html
Just don't know if I want to devote time to doing a full blown program. It works as is, but does nothing more than checksum whatever is in my current path of which later I can do a diff etc.
"Wise men talk because they have something to say; fools, because they have to say something." -- Plato
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/
| Previous by Date: | Re: [Full-disclosure] Linux big bang theory...., Vincent Archer |
|---|---|
| Next by Date: | [Full-disclosure] [SECURITY] [DSA 1296-1] New php4 packages fix privilege escalation, Moritz Muehlenhoff |
| Previous by Thread: | Re: [Full-disclosure] Linux big bang theory...., Vincent Archer |
| Next by Thread: | Re: [Full-disclosure] Linux big bang theory...., gary sweet |
| Indexes: | [Date] [Thread] [Top] [All Lists] |