From: Robert Nicholson <robert.nicholson@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Does the linux kernel contain support for ATA Security feature set?
Date: Sun, 19 Apr 2009 14:32:16 -0500 [thread overview]
Message-ID: <8AF7B5C5-FC88-443C-98BF-007E080B478E@gmail.com> (raw)
In-Reply-To: <C2111E25-C51B-4AB1-96F5-A7C313B4B487@gmail.com>
So when I do a hdparm --security-set-pass NULL /dev/sda
I get a
SECURITY_ERASE: Input/output error
This is with a kernel that doesn't have CONFIG_IDE_TASK_IOCTL=y defined
I'm also told that for SATA drives that's not necessary anyway. Is
that correct?
What should the response be for hdparm if CONFIG_IDE_TASK_IOCTL isn't
defined for a drive that needs it?
The drive is an Intel X-25M
HDDERASE won't work since I'm on a Mac.
I don't want to create a customized lived CD witth a new kernel unless
it's necessary.
On Apr 16, 2009, at 7:50 PM, Robert Nicholson wrote:
> So you're implying that it is possible to do a SECURE_ERASE using
> hdparm then.
>
> I don't know why but HDDERASE tool requires legacy IDE mode.
>
> On Apr 16, 2009, at 7:46 PM, Matthew Garrett wrote:
>
>> On Thu, Apr 16, 2009 at 06:49:59PM -0500, Robert Nicholson wrote:
>>> So, I've got an X-25M that I want to securely erase and it turns out
>>> on a Mac I'm not going to be able to issue the command because it
>>> doesn't support legacy IDE mode from what I understand. So the
>>> idea of
>>> a any boot CD that I could boot and run a program that can issue a
>>> SECURE_ERASE (SE) to the drive is only applicable to PC's.
>>
>> Why is the lack of legacy IDE an issue? hdparm works fine with SATA
>> setups.
>> --
>> Matthew Garrett | mjg59@srcf.ucam.org
>
next prev parent reply other threads:[~2009-04-19 19:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-16 23:49 Robert Nicholson
2009-04-17 0:46 ` Matthew Garrett
2009-04-17 0:50 ` Robert Nicholson
2009-04-17 0:55 ` Matthew Garrett
2009-04-19 19:32 ` Robert Nicholson [this message]
2009-04-17 9:29 ` Alan Cox
2009-04-17 16:37 ` Krzysztof Halasa
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=8AF7B5C5-FC88-443C-98BF-007E080B478E@gmail.com \
--to=robert.nicholson@gmail.com \
--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
all inboxes | Powered by JetHome®