From: Ralph Corderoy <ralph@inputplus.co.uk>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ISP filtering - update (fwd)
Date: Sun, 8 May 2005 15:07:52 +0100 [thread overview]
Message-ID: <200505081407.j48E7q006578@blake.inputplus.co.uk> (raw)
In-Reply-To: <a6c.426ac806.5d71f@blake.inputplus.co.uk>
[-- Attachment #1: Type: text/plain, Size: 36 bytes --]
[Replace this with your comments.]
[-- Attachment #2: Type: message/rfc822, Size: 1883 bytes --]
From: Ralph Corderoy <ralph@inputplus.co.uk>
Subject: Re: [9fans] ISP filtering - update
Date: Mon, 25 Apr 2005 08:59:53 GMT
Message-ID: <a6c.426ac806.5d71f@blake.inputplus.co.uk>
Hi,
Presotto wrote:
> I wrote:
> > What I don't understand is why the worms don't trigger some harm at
> > some point in the future, like setting the hard drive password to a
> > random string. Requiring the `master' password from the drive
> > manufacturer or OEM would cause enourmous amounts of hassle. The
> > worm would have meanwhile re-produced elsewhere so its not `shooting
> > itself in the head'.
>
> I didn't even realize that there were hardware enforced passwords on
> disks. I just looked up ata specs and found a whole slew of security
> cruft I never knew about. Thanks.
c't have recently published an article covering the potential misuse of
the ATA security functions so perhaps we'll start seeing some exploits
of it now.
http://www.heise.de/ct/english/05/08/172/
Cheers,
Ralph.
prev parent reply other threads:[~2005-05-08 14:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-26 13:09 [9fans] ISP filtering - update David Presotto
2003-09-26 16:44 ` Dan Cross
2003-09-26 17:23 ` Wes Kussmaul
2003-09-26 17:31 ` David Presotto
2003-09-26 18:29 ` Wes Kussmaul
2003-09-26 18:51 ` Dan Cross
2003-09-26 17:33 ` David Presotto
2003-10-06 9:01 ` Ralph Corderoy
2003-10-06 12:55 ` David Presotto
2003-10-06 17:59 ` Christopher Nielsen
[not found] ` <a6c.426ac806.5d71f@blake.inputplus.co.uk>
2005-05-08 14:07 ` Ralph Corderoy [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200505081407.j48E7q006578@blake.inputplus.co.uk \
--to=ralph@inputplus.co.uk \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).