Message from discussion
Self-destructing crypto
Received: by 10.66.89.195 with SMTP id bq3mr840934pab.35.1343694777520;
Mon, 30 Jul 2012 17:32:57 -0700 (PDT)
X-BeenThere: hackerspace_brisbane@googlegroups.com
Received: by 10.68.226.132 with SMTP id rs4ls285944pbc.6.gmail; Mon, 30 Jul
2012 17:32:57 -0700 (PDT)
Received: by 10.68.220.230 with SMTP id pz6mr2547589pbc.3.1343694777180;
Mon, 30 Jul 2012 17:32:57 -0700 (PDT)
Received: by 10.68.220.230 with SMTP id pz6mr2547588pbc.3.1343694777158;
Mon, 30 Jul 2012 17:32:57 -0700 (PDT)
Return-Path: <thejollygrimrea...@gmail.com>
Received: from mail-pb0-f49.google.com (mail-pb0-f49.google.com [209.85.160.49])
by gmr-mx.google.com with ESMTPS id vo7si1250689pbc.1.2012.07.30.17.32.57
(version=TLSv1/SSLv3 cipher=OTHER);
Mon, 30 Jul 2012 17:32:57 -0700 (PDT)
Received-SPF: pass (google.com: domain of thejollygrimrea...@gmail.com designates 209.85.160.49 as permitted sender) client-ip=209.85.160.49;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of thejollygrimrea...@gmail.com designates 209.85.160.49 as permitted sender) smtp.mail=thejollygrimrea...@gmail.com; dkim=pass header...@gmail.com
Received: by pbbrq13 with SMTP id rq13so11237706pbb.8
for <hackerspace_brisbane@googlegroups.com>; Mon, 30 Jul 2012 17:32:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20120113;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:content-type;
bh=+HEsnsGyymrTedfufZF4UNGmWo5hxaeD//3Pimy8fGM=;
b=oZmYQ4Awm7ZwRIe2Le2tz/0r7115QPfZKbUnLx80It69VMGEBayK7lDUtq1t7ovjLb
Umvhhh44wLFdAvYiDUdcDHS0nvSk1VGxOj/s/FQjX8VcamHyP+hJBiscHNP7I2SA1RWc
Wzd53l2pcfXpLBCfMtzwvgVlsHRGmEf2hbeSNI4XHb+RZSUS67J4zV37y7x5onsxTqvm
wzgTutv9okirZGxbAnHwuMt/iF/iyJ5+53ECAYSS0lddaj1kiDfFbDja6edSiHyex6AF
2hqZlbJRRO0l1Co6cSwHKCTR+ZloKgJkJTk95LPqKsyk9eaSHxaWuqKoc+HU8jdxCL/d
TvtQ==
MIME-Version: 1.0
Received: by 10.68.220.104 with SMTP id pv8mr32359888pbc.119.1343694776900;
Mon, 30 Jul 2012 17:32:56 -0700 (PDT)
Received: by 10.68.21.195 with HTTP; Mon, 30 Jul 2012 17:32:56 -0700 (PDT)
In-Reply-To: <CAH02DzrhyCXv8nazHZpsEGkTetbgNz2fPBcyHdR-QaKhQOb...@mail.gmail.com>
References: <23e448cf-9fe3-41f5-8ebf-5d6b607d18c4@googlegroups.com>
<CACiBCBZ9bfFw6CUAvOBbSnZjHzZHbxo1e-EMbgscGR_ojDs...@mail.gmail.com>
<CAPh9M+HfeqHn-e-JYTo2Mt=epjpdLOG-vbkji4VJEyj=--y...@mail.gmail.com>
<CAH02DzrhyCXv8nazHZpsEGkTetbgNz2fPBcyHdR-QaKhQOb...@mail.gmail.com>
Date: Tue, 31 Jul 2012 10:32:56 +1000
Message-ID: <CAP7Zm7kPdFSx4tNNcrKbHjt4ca6YvQRg35F7V8UX9Ewyycy...@mail.gmail.com>
Subject: Re: Self-destructing crypto
From: chris bate <thejollygrimrea...@gmail.com>
To: hackerspace_brisbane@googlegroups.com
Content-Type: multipart/alternative; boundary=e89a8ff254ccdd1bd404c615518c
--e89a8ff254ccdd1bd404c615518c
Content-Type: text/plain; charset=ISO-8859-1
how much data are we talking about?
On Tue, Jul 31, 2012 at 9:04 AM, Luke Irwin <bujinka...@gmail.com> wrote:
> I cannot speak for SSD's, but from what I was taught many years ago was
> that the only way to ensure data being recoverable from a disk, is to
> either melt it or granulate it ( so termite would do the trick nicely :) )
> Drilling holes in the platter will slow someone down and add to the cost
> of recovery, but will not prevent them (with significant time and money)
> getting back the data, and having it encrypted on there simply adds to the
> cost again.
>
>
>
>
>
>
> On 31 July 2012 08:56, Stuart Young <cef...@gmail.com> wrote:
>
>> Erasing an SSD properly would take a while. Just ask anyone who had one
>> of the slightly older ones that didn't support TRIM when they ran out of
>> free blocks (random hangs when writing while old blocks were erased to make
>> room for new). You'd also want to be sure that it actually erased the chip
>> too (as some manufacturers have a habit of cheating when it comes to
>> erasing stuff).
>>
>> If you're not worried about price of replacing it, thought about using
>> thermite? Just put it around the chips (key flash & SSD storage) and set it
>> off when you're 'worried'. Of course, there's OH&S concerns here.
>>
>> Might even be useful after you hit it with a high voltage (eg: 5kv) and
>> 'fry' the chips (possibly even use the same spark to start the thermite).
>>
>> All you need would be a tiny package that covers the chips and possibly
>> put a simple trigger system across the power rail of the chips that will
>> only fire on a high voltage.
>>
>> BTW: If you're using a spinning disk, you could wind a big electromagnet
>> around it and just continuously fire the magnet in pules to wipe the disk.
>> After that, as Joel suggests, physically damage the disk. If you had access
>> to a clean-room, I'd remove the cover and put the 'tamper device' that
>> destroys the disk inside the drive, as then you don't have to puncture the
>> top cover as well. Will of course void your warranty. ;)
>>
>> --
>> Stuart Young (aka Cefiar)
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "hackerspace_brisbane" group.
>> To post to this group, send email to
>> hackerspace_brisbane@googlegroups.com.
>> To unsubscribe from this group, send email to
>> hackerspace_brisbane+unsubscribe@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/hackerspace_brisbane?hl=en.
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "hackerspace_brisbane" group.
> To post to this group, send email to hackerspace_brisbane@googlegroups.com
> .
> To unsubscribe from this group, send email to
> hackerspace_brisbane+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/hackerspace_brisbane?hl=en.
>
--e89a8ff254ccdd1bd404c615518c
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
how much data are we talking about?<br><br><br><br><div class=3D"gmail_quot=
e">On Tue, Jul 31, 2012 at 9:04 AM, Luke Irwin <span dir=3D"ltr"><<a hre=
f=3D"mailto:bujinka...@gmail.com" target=3D"_blank">bujinka...@gmail.com</a=
>></span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">I cannot speak for SSD's, but from what =
I was taught many years ago was that the only way to ensure data being reco=
verable from a disk, is to either melt it or granulate it ( so termite woul=
d do the trick nicely=A0 :)=A0 )<br>
Drilling holes in the platter will slow someone down and add to the cost of=
recovery, but will not prevent them (with significant time and money) gett=
ing back the data, and having it encrypted on there simply adds to the cost=
again.<div>
<div><br>
<br><br><br><br><br><div class=3D"gmail_quote">On 31 July 2012 08:56, Stuar=
t Young <span dir=3D"ltr"><<a href=3D"mailto:cef...@gmail.com" target=3D=
"_blank">cef...@gmail.com</a>></span> wrote:<br><blockquote class=3D"gma=
il_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-lef=
t:1ex">
Erasing an SSD properly would take a while. Just ask anyone who had one of =
the slightly older ones that didn't support TRIM when they ran out of f=
ree blocks (random hangs when writing while old blocks were erased to make =
room for new). You'd also want to be sure that it actually erased the c=
hip too (as some manufacturers have a habit of cheating when it comes to er=
asing stuff).<br>
<br>If you're not worried about price of replacing it, thought about us=
ing thermite? Just put it around the chips (key flash & SSD storage) an=
d set it off when you're 'worried'. Of course, there's OH&a=
mp;S concerns here.<br>
<br>Might even be useful after you hit it with a high voltage (eg: 5kv) and=
'fry' the chips (possibly even use the same spark to start the the=
rmite).<br><br>All you need would be a tiny package that covers the chips a=
nd possibly put a simple trigger system across the power rail of the chips =
that will only fire on a high voltage.<br>
<br>BTW: If you're using a spinning disk, you could wind a big electrom=
agnet around it and just continuously fire the magnet in pules to wipe the =
disk. After that, as Joel suggests, physically damage the disk. If you had =
access to a clean-room, I'd remove the cover and put the 'tamper de=
vice' that destroys the disk inside the drive, as then you don't ha=
ve to puncture the top cover as well. Will of course void your warranty. ;)=
<span><font color=3D"#888888"><br clear=3D"all">
<br>-- <br>Stuart Young (aka Cefiar)<br>
<p></p>
-- <br>
You received this message because you are subscribed to the Google Groups &=
quot;hackerspace_brisbane" group.<br>
To post to this group, send email to <a href=3D"mailto:hackerspace_brisbane=
@googlegroups.com" target=3D"_blank">hackerspace_brisbane@googlegroups.com<=
/a>.<br>
To unsubscribe from this group, send email to <a href=3D"mailto:hackerspace=
_brisbane%2Bunsubscribe@googlegroups.com" target=3D"_blank">hackerspace_bri=
sbane+unsubscribe@googlegroups.com</a>.<br>
For more options, visit this group at <a href=3D"http://groups.google.com/g=
roup/hackerspace_brisbane?hl=3Den" target=3D"_blank">http://groups.google.c=
om/group/hackerspace_brisbane?hl=3Den</a>.<br>
</font></span></blockquote></div><br>
<p></p>
-- <br>
You received this message because you are subscribed to the Google Groups &=
quot;hackerspace_brisbane" group.<br>
To post to this group, send email to <a href=3D"mailto:hackerspace_brisbane=
@googlegroups.com" target=3D"_blank">hackerspace_brisbane@googlegroups.com<=
/a>.<br>
To unsubscribe from this group, send email to <a href=3D"mailto:hackerspace=
_brisbane%2Bunsubscribe@googlegroups.com" target=3D"_blank">hackerspace_bri=
sbane+unsubscribe@googlegroups.com</a>.<br>
For more options, visit this group at <a href=3D"http://groups.google.com/g=
roup/hackerspace_brisbane?hl=3Den" target=3D"_blank">http://groups.google.c=
om/group/hackerspace_brisbane?hl=3Den</a>.<br>
</div></div></blockquote></div><br>
--e89a8ff254ccdd1bd404c615518c--