From: Jeff Garzik <jeff@garzik.org>
To: Etienne Lorrain <etienne_lorrain@yahoo.fr>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: [RFC] ATA host-protected area (HPA) device mapper?
Date: Fri, 09 Jun 2006 10:48:50 -0400 [thread overview]
Message-ID: <44898A52.2010008@garzik.org> (raw)
In-Reply-To: <20060609104759.26001.qmail@web26913.mail.ukl.yahoo.com>
Etienne Lorrain wrote:
> Your hard disk is a lot more powerfull than what you think, only very old
No, it's not. I am well aware of what's in the ATA spec.
> hard disks only have ATA set max command. Nowadays, you can not only set the
Not true.
> Gujin also do the absolutely needed setup of the IDE hard disk which is to freeze
> the password system _and_ the config system of all the IDE hard disks present, so
> that no virus can put a random password and send you an E-mail with the address
> where to send the money to get the password to unlock the hard disk and so access
> again your data. Again, freezing means no more modifiable until next power cycle,
> so IMO it is the job of the bootloader to setup the hard disk, before running
> anything like Linux, a commercial OS, a bootable CDROM...
This is totally broken, and I am going to strongly recommend that no one
use this software.
It is the OS responsibility to do this. As a simple example, when the
libata ACPI patches are merged (soon), libata will send BIOS-specified
taskfiles to the device -- including the hard drive password, if any.
Then it will freeze the settings.
Gujin's behavior will prevent the user from accessing their data, if
they have protected it via BIOS.
> Gujin is assuming that your hard disk are accessible by the documented ATA ide
> system, and some (or all?) IDE SATA interface have (volumtary?) broken
> implementation: they are not IDE register compatible.
More evidence that Gujin is completely broken.
Host controller programming interfaces have _always_ been variable. PCI
IDE standard was never a requirement for all host controllers, indeed
such a requirement would be stupid, and widely ignored.
Modern SATA controllers are all FIS-based, and are not (and should not
be) limited by the legacy IDE register programming interface.
Jeff
next prev parent reply other threads:[~2006-06-09 14:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-09 10:47 [RFC] ATA host-protected area (HPA) device mapper? Etienne Lorrain
2006-06-09 14:48 ` Jeff Garzik [this message]
2006-06-09 15:55 ` RE : " Etienne Lorrain
2006-06-09 17:22 ` Alan Cox
2006-06-09 20:10 ` RE : " Etienne Lorrain
2006-06-10 11:56 ` Etienne Lorrain
2006-06-11 15:48 ` Arjan van de Ven
2006-06-13 10:00 ` Etienne Lorrain
-- strict thread matches above, loose matches on Subject: below --
2006-06-09 20:41 Etienne Lorrain
2006-06-08 7:30 [RFC] AHCI Command Completion Coalescing(CCC) proposal zhao, forrest
2006-06-08 15:01 ` Jeff Garzik
2006-06-09 2:27 ` zhao, forrest
2006-06-09 3:11 ` Another project for you... :) Jeff Garzik
2006-06-09 3:43 ` [RFC] ATA host-protected area (HPA) device mapper? Jeff Garzik
2006-06-09 4:51 ` Matthew Frost
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=44898A52.2010008@garzik.org \
--to=jeff@garzik.org \
--cc=etienne_lorrain@yahoo.fr \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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).