| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
From: digitalchaos at gawab.com (Digitalchaos) Subject: Bios programming... Matt, maybe you should not be so concerned with trying to put code into the bios; but, rather install it to the boot sector of the hard drive. That is copy the monitoring program to the boot sector That will launch the "service" you are talking about And that service can also rewrite itself to the boot Sector (*hint* *hint* a "boot sector virus", perhaps?) That can be spread to all of the people's email addresses That you harvest from this little operation (this would include An executable attachment that would restore the service to the hard drive, upon Execution). I mean, that is the only feasible means for you to Have this service installed remotely (that is you will probably Not be given direct, physical, access to the users computer -- which Means no hardware or bios chip modifications or EEPROM Reprogramming).
Powered by blists - more mailing lists