Self-destructing crypto - hackerspace_brisbane

The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Message from discussion Self-destructing crypto
Received-SPF: pass (google.com: domain of fatal.exception.occur...@gmail.com designates 209.85.214.46 as permitted sender) client-ip=209.85.214.46;
MIME-Version: 1.0
In-Reply-To: <cd78285c-c47a-430f-b0a1-f1d8abc4a...@j7g2000vbx.googlegroups.com>
References: <23e448cf-9fe3-41f5-8ebf-5d6b607d18c4@googlegroups.com>
	<CAEN4MSS6_6DuAUjVwFq5LeFZjeGUUgKdTqjow3YLc9CHOvn...@mail.gmail.com>
	<CAAxzKbTaYRchfzMXw2EcVAkqhX0C-kb7HBXb8kjj8StRG96...@mail.gmail.com>
	<CAEN4MSReF7ChcjqjqZeB3xk4Q8jRi6-qXQCXE-P+UzF4067...@mail.gmail.com>
	<CA+g76aoBQVx0RqiYHkrWTeXc9bp75crd5+t9gq4dtLiyiGA...@mail.gmail.com>
	<CAEN4MSSTArsT_HqD0uSJvxSFGx_hahVuO9tygosx7yZUxWX...@mail.gmail.com>
	<CA+g76aou5duKs8tPH28VLGsRMXSKWvXh5gd7bTFORieXm2i...@mail.gmail.com>
	<CAEN4MSSYaoh_SHm3YQSnOtKA0imOuLTOm315hnOxQf-4fok...@mail.gmail.com>
	<CAEN4MSR+kmr+KV6m1i5Ju2V3E5UagiReQmq11xYVjbR3+bJ...@mail.gmail.com>
	<CA+g76arXwkt7++rZN0bNCUv7YPgXSDAiNfR3+rBKUGAJNMk...@mail.gmail.com>
	<CA+w-GAa9z45ijhCaiK7b=cLPwijAnmf63AGKsZd6WvZmfOu...@mail.gmail.com>
	<501892DD.8090...@shikadi.net>
	<99872D51-21FE-4397-A3E2-E3422EDA8...@gmail.com>
	<cd78285c-c47a-430f-b0a1-f1d8abc4a...@j7g2000vbx.googlegroups.com>
Date: Thu, 2 Aug 2012 11:01:36 +1000
Message-ID: <CANnr-csmEU=tu_FQ8bMJSff=mPJAw7KS+FMkgACS3LX+i2U...@mail.gmail.com>
Subject: Re: Self-destructing crypto
From: Joel Byrnes <fatal.exception.occur...@gmail.com>
To: hackerspace_brisbane@googlegroups.com
Content-Type: multipart/alternative; boundary=0015175cdb1a119ebd04c63df4fd

--0015175cdb1a119ebd04c63df4fd
Content-Type: text/plain; charset=ISO-8859-1

I'm sure you know more about this than me, but they said that about WEP
too, then WPA... :)

Generally encryption is not broken by brute force but by finding weaknesses
in the method, or patterns in the encrypted data (and hard drives have
patterns), and statistical methods to guess the key. However that can take
years to develop, so if it's a recent or well-designed encryption
technique, it should be fairly safe.

But then we come back to rubber-hose cryptanalysis, where it's
simpler/cheaper/faster to find out who knows the key and go to their house
instead of attack the data. So then we want to go back to destroying the
data instead of blocking access to it.

On Thu, Aug 2, 2012 at 10:30 AM, OperaMan <lione...@big.net.au> wrote:

> > In that scenario, the data still exists and there is some possibility it
> still could be cracked and recovered. It is merely a matter of time and the
> time depends on the crypto used.
>
> That's not really true. Most modern encryption is regarded as
> "practically" unbreakable. That means it can potentially be broken,
> but the effort required is impractical. So, while it may be "a matter
> of time", the time involved would be several times the age of the
> universe for most decent encryption.
>
> If a One Time Pad were used then the encryption is absolutely
> unbreakable; once the key is gone there is no chance of recovering the
> data. However, that would require a key at least as long as the data
> encrypted.
>
> Lionel...
>
> --
> 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.
>
>

--0015175cdb1a119ebd04c63df4fd
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I&#39;m sure you know more about this than me, but they said that about WEP=
 too, then WPA... :)<div><br></div><div>Generally encryption is not broken =
by brute force but by finding weaknesses in the method, or patterns in the =
encrypted data (and hard drives have patterns), and statistical methods to =
guess the key. However that can take years to develop, so if it&#39;s a rec=
ent or well-designed encryption technique, it should be fairly safe.</div>
<div><br></div><div>But then we come back to rubber-hose cryptanalysis, whe=
re it&#39;s simpler/cheaper/faster to find out who knows the key and go to =
their house instead of attack the data. So then we want to go back to destr=
oying the data instead of blocking access to it.=A0<br>
<br><div class=3D"gmail_quote">On Thu, Aug 2, 2012 at 10:30 AM, OperaMan <s=
pan dir=3D"ltr">&lt;<a href=3D"mailto:lione...@big.net.au" target=3D"_blank=
">lione...@big.net.au</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_q=
uote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1e=
x">
<div class=3D"im">&gt; In that scenario, the data still exists and there is=
 some possibility it still could be cracked and recovered. It is merely a m=
atter of time and the time depends on the crypto used.<br>
<br>
</div>That&#39;s not really true. Most modern encryption is regarded as<br>
&quot;practically&quot; unbreakable. That means it can potentially be broke=
n,<br>
but the effort required is impractical. So, while it may be &quot;a matter<=
br>
of time&quot;, the time involved would be several times the age of the<br>
universe for most decent encryption.<br>
<br>
If a One Time Pad were used then the encryption is absolutely<br>
unbreakable; once the key is gone there is no chance of recovering the<br>
data. However, that would require a key at least as long as the data<br>
encrypted.<br>
<br>
Lionel...<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
--<br>
You received this message because you are subscribed to the Google Groups &=
quot;hackerspace_brisbane&quot; group.<br>
To post to this group, send email to <a href=3D"mailto:hackerspace_brisbane=
@googlegroups.com">hackerspace_brisbane@googlegroups.com</a>.<br>
To unsubscribe from this group, send email to <a href=3D"mailto:hackerspace=
_brisbane%2Bunsubscribe@googlegroups.com">hackerspace_brisbane+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>
<br>
</div></div></blockquote></div><br></div>

--0015175cdb1a119ebd04c63df4fd--
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
Account Options
