From: Mark Lord <liml@rtr.ca>
To: Greg Freemyer <greg.freemyer@gmail.com>
Cc: IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: hdparm-9.2 now available: w/ DCO and firmware support
Date: Tue, 04 Nov 2008 13:08:22 -0500 [thread overview]
Message-ID: <49108F96.8010902@rtr.ca> (raw)
In-Reply-To: <87f94c370811041001ucd76d27lc948c553ad2a381e@mail.gmail.com>
Greg Freemyer wrote:
> On Mon, Nov 3, 2008 at 1:17 PM, Mark Lord <liml@rtr.ca> wrote:
>> hdparm v9.2 is now available from sourceforge.
>>
>> http://sourceforge.net/projects/hdparm/
>>
>> New since v8.9 are:
>>
>> 1. Support for Device Configuration Overlay (DCO),
>> with the --dco-identify, --dco-freeze, and --dco-restore flags.
>> DCO is a feature set that enables vendors/OEMs to disable/hide
>> certain drive features (eg. NCQ, LBA48, ..) for whatever reason
>> (eg. compatibility with a specific b0rked BIOS).
>> This release of hdparm can display/reset DCO, but not selectively
>> disable features yet.
..
> I'm very happy to see the DCO support go in.
>
> There is a small army of "Computer Forensic" examiners which do their
> forensic imaging via Linux and I'm sure many will feel the same.
..
Mmm.. never thought about that much before now,
but DCO is a nifty way to hide much of a drive from prying eyes.
Eg. Use DCO to restrict the drive to LBA28 accessible sectors
and also turn off LBA48 support, and then a lot of space becomes "hidden".
Until now!
Cheers
next prev parent reply other threads:[~2008-11-04 18:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-03 18:17 hdparm-9.2 now available: w/ DCO and firmware support Mark Lord
2008-11-04 18:01 ` Greg Freemyer
2008-11-04 18:08 ` Mark Lord [this message]
2008-11-04 18:23 ` Greg Freemyer
2008-11-04 19:13 ` Mark Lord
2008-11-04 21:04 ` Greg Freemyer
2008-11-04 21:55 ` Greg Freemyer
2008-11-05 2:34 ` Mark Lord
2008-11-04 18:05 ` hdparm-9.3 now available: --idle-immediate & --idle-unload flags Mark Lord
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=49108F96.8010902@rtr.ca \
--to=liml@rtr.ca \
--cc=greg.freemyer@gmail.com \
--cc=linux-ide@vger.kernel.org \
/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).