7 messages in org.freebsd.freebsd-security[Freebsd-security] Re: Hacked or not ...| From | Sent On | Attachments |
|---|---|---|
| Peter Rosa | Jun 12, 2004 12:01 pm | |
| Thordur Ivar | Jun 12, 2004 1:25 pm | |
| Alex Povolotsky | Jun 12, 2004 2:05 pm | |
| Lupe Christoph | Jun 12, 2004 2:31 pm | |
| Peter Jeremy | Jun 12, 2004 9:32 pm | |
| Remko Lodder | Jun 12, 2004 11:58 pm | |
| Peter Rosa | Jun 13, 2004 8:07 am |
| Subject: | [Freebsd-security] Re: Hacked or not appendice | |
|---|---|---|
| From: | Remko Lodder (rem...@elvandar.org) | |
| Date: | Jun 12, 2004 11:58:50 pm | |
| List: | org.freebsd.freebsd-security | |
Hey
Peter Jeremy wrote:
[Please wrap your mail before 80 characters]
Why would you trust the toolchain on a potentially hacked machine? There's an old paper by Ken Thompson that dicusses patching the C compiler to recognize the login sources and re-introduce a backdoor - even it was removed from the login sources.
You would be much better off booting a fixit CD-ROM and using that rather than trusting anything on the potentially hacked system.
Indeed, one should make a backup copy (if possible) of the potentially hacked computer (Drive) and take the machine offline.
Then insert the backupdisk in a other pc, (or the same, with the original hd stored safely) and startup your Live-cd kit (which can be a freebsd version from cd, or linux). Make sure that the tools necessary are on the live cd;-) and to forensics (tct might help (The Coroners Toolkit)..
After finding out what happened, format the disk, and reinstall from scratch, be hostile to every config file and stuff you backupped, because you might not be able to tell when the potential hack took place.....
Cheers :-)
-- Kind regards,