|
|||||||||||
|
Re: /bin/login listening?
From: Douglas Allan Tutty <dtutty(at)porchlight.ca>
Date: Sun Jul 29 2007 - 12:35:03 EDT
> So if I'm compromised nothing is safe, and the only guaranteed way to Try this: Boot the box from something like the install CD, go to a shell, mount your / partition ro, noexec. I think the install CD has md5sum installed. Run: #md5sum /bin/login. On my i386, I get: 2ee32ff74e474c4d9fc9df6f1460980f /bin/login If /bin/login is fine, then I'd forget about it. If it differs, I'd wipe the drive and reinstall; from backups before your first indication of a problem. Then examine the difference between that backup's data and your most recent backup. Actually, to put your mind at ease, I've attached a file bin-MD5SUMS which is the output of: $md5sum /bin/* > bin-MD5SUMS Put this onto a floppy and mount it when you boot your install CD. Then edit it so that, for example the /bin/login reads /mnt/bin/login. You can then verify the whole /bin with #md5sum -c bin-MD5SUMS Here's the file, and good luck. Doug. -- To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.orgReceived on Sun Jul 29 12:36:06 2007 This archive was generated by hypermail 2.1.8 : Thu Aug 09 2007 - 18:29:25 EDT |
||||||||||
|
|||||||||||