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.




Network Security FullDisclosure
[Top] [All Lists]

Re: [Full-Disclosure] Bios programming...

Subject: Re: [Full-Disclosure] Bios programming...
Date: Thu, 03 Mar 2005 15:57:02 -0500
On Thu, 03 Mar 2005 15:33:09 EST, Matt Marooney said:

The intent of the BIOS portion of the program was just to have a small
bit of code that checked for the existence of the main monitoring
program on the disk, and if it was not there, reload it somehow.  

The main program would run from the disk, not the BIOS.  

Like I said - all it takes is a Knoppix disk to screw over most of these
schemes - you can't even disable booting from CD and put a BIOS password
on, because you have the following:

1) A motivated user

2) Unmonitored, unobserved physical access (if you don't, there's *bigger*
problems in this scenario ;)

3) Somewhere in there, there's a jumper that will reset the BIOS password....

There's really *NO* way to do this on today's commodity hardware in a way that
will stop a user who knows it's there and has physical access.  At best, you
can do it in a way that will surprise an *unsuspecting* person (which is what
most of these anti-theft beacon programs do - the only reason they work is
because the guy who jacked the laptop probably doesn't realize the program is
installed, and thus doesn't take precautions to stop it).

The only way you can make this work is if you have hardware that includes
something like the TPM chipsets from NatSemi or Atmel.  Unfortunately, if your
operating system contains enough support for the chipset to use it so the
person at the keyboard can't subvert it, it will almost certainly use it 
*itself*
to stop people from doing exactly the sort of code insertion you're trying to 
do.

So you're *still* screwed. :)

Attachment: pgpKdLB1A10BC.pgp
Description: PGP signature

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.netsys.com/full-disclosure-charter.html
<Prev in Thread] Current Thread [Next in Thread>