Date: Thu, 15 Nov 2001 19:24:53 +0000 From: Colin Percival <colin.percival@wadham.ox.ac.uk> To: veedee@c7.campus.utcluj.ro, cperciva@sfu.ca Cc: Tobias Roth <roth@iamexwi.unibe.ch>, Stefan Probst <stefan.probst@opticom.v-nam.net>, freebsd-security@FreeBSD.ORG Subject: Re: Spoofing file information? Message-ID: <5.0.2.1.1.20011115191853.0e8c8598@popserver.sfu.ca> In-Reply-To: <20011115121351.A24535@c7.campus.utcluj.ro> References: <5.0.2.1.1.20011115083248.0e8cd548@popserver.sfu.ca> <5.1.0.14.2.20011115143223.04264050@MailServer> <5.1.0.14.2.20011115143223.04264050@MailServer> <20011115092433.A9120@roy.unibe.ch> <5.0.2.1.1.20011115083248.0e8cd548@popserver.sfu.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
At 12:13 15/11/2001 +0200, veedee@c7.campus.utcluj.ro wrote: > I'm just taking a wild guess here, but aren't some of you guys getting a >little bit paranoid? Next thing you're gonna advise Stefan is that someone >flashed some EEPROMs from his hardware that contain some code that activates >when blahblah, or simply say "just change the whole fucking thing (eg >server)". If he was operating with a writeable EEPROM BIOS, I would indeed be concerned (I note that there are also viruses which zero writeable EEPROMs, making system recovery rather more difficult). Fortunately most motherboards have jumpers which must be moved before the EEPROM can be written to; I therefore would assume that his EEPROM is most likely safe. Colin Percival To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5.0.2.1.1.20011115191853.0e8c8598>