linux-kernel - Re: Linux kernel - Libata bad block error handling to user mode program

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <87f94c371003140912g1a567458ic2d78da6eed7fdb3@mail.gmail.com>
Date:	Sun, 14 Mar 2010 12:12:06 -0400
From:	Greg Freemyer <greg.freemyer@...il.com>
To:	Mark Lord <kernel@...savvy.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	foo saa <foosaa@...il.com>, linux-kernel@...r.kernel.org,
	linux-ide@...r.kernel.org, Jens Axboe <jens.axboe@...cle.com>,
	linux-mm@...ck.org
Subject: Re: Linux kernel - Libata bad block error handling to user mode 
	program

On Sun, Mar 14, 2010 at 12:02 PM, Mark Lord <kernel@...savvy.com> wrote:
> On 03/11/10 13:29, Greg Freemyer wrote:
>>>
>>> But really.. isn't "hdparm --security-erase NULL /dev/sdX" good enough
>>> ???
>>>
>>
>> This thread seems to have died off.  If there is a real problem, I
>> hope it picks back up.
>>
>> Mark, as to your question the few times I've tried that the bios on
>> the test machine blocked the command.  So it may have some specific
>> utility, but it's a not a generic solution in my mind.
>
> ..
>
> Yeah, a lot of BIOSs do a "SECURITY FREEZE" command before booting,
> which disables things like "SECURITY ERASE" until the next hard reset.
>
> So, on a Linux system, just unplug the drive after booting, replug it,
> and usually it can then be erased.

I have a client that wipes 10,000+ drives a month. (They do this as a
service to banks, etc. as the machines they're in are retired, so they
use 10,000+ machines to wipe those 10,000+ drives.)

They tend not to open the case, just boot via PXE/USB/CD and run a wiping tool.

Opening the case to do as you propose is not really acceptable.  Also
they still have a lot of IDE inside those retiring machines.

fyi: If the wipe fails for whatever reason, they do open the case and
physically remove/disable/sanitize the drive.

Greg
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/