[148673] in cryptography@c2.net mail archive
Re: [Cryptography] Serious paranoia...
daemon@ATHENA.MIT.EDU (Phillip Hallam-Baker)
Tue Dec 24 16:59:18 2013
X-Original-To: cryptography@metzdowd.com
In-Reply-To: <CAOLP8p6uMVTakgBE4Wva5oqUXnaQt_54FLmAphyhXzEeG+3qkg@mail.gmail.com>
Date: Tue, 24 Dec 2013 16:45:42 -0500
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Bill Cox <waywardgeek@gmail.com>
Cc: "cryptography@metzdowd.com" <cryptography@metzdowd.com>
Errors-To: cryptography-bounces+crypto.discuss=bloom-picayune.mit.edu@metzdowd.com
--===============5484770775319382141==
Content-Type: multipart/alternative; boundary=001a113429c0877e6404ee4eaaa6
--001a113429c0877e6404ee4eaaa6
Content-Type: text/plain; charset=ISO-8859-1
Well my main machine suddenly shut down last night right after I managed to
successfully send an encrypted mail and read it at the other end.
The water cooling loop was out of coolant despite the claim of the
manufacturer that it was 'maintenance free'. So obviously a STUXNET type
attack.
In reference to the other thread on how to check code. My approach is to
use a code synthesizer and bring the code as close as possible to the spec.
If someone wants to audit the code they can read the generated code which
is very plain vanilla and exceptionally regular. They can also look at the
generator and see if it has special case handling for particular specs.
Sure someone could bongo the synthesizer, just like they could bongo the
compiler. But that would be very hard to sustain.
--001a113429c0877e6404ee4eaaa6
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Well my main machine suddenly shut down last night right a=
fter I managed to successfully send an encrypted mail and read it at the ot=
her end.<div><br></div><div>The water cooling loop was out of coolant despi=
te the claim of the manufacturer that it was 'maintenance free'. So=
obviously a STUXNET type attack.</div>
<div><br></div><div><br></div><div>In reference to the other thread on how =
to check code. My approach is to use a code synthesizer and bring the code =
as close as possible to the spec. If someone wants to audit the code they c=
an read the generated code which is very plain vanilla and exceptionally re=
gular. They can also look at the generator and see if it has special case h=
andling for particular specs.</div>
<div><br></div><div>Sure someone could bongo the synthesizer, just like the=
y could bongo the compiler. But that would be very hard to sustain.</div></=
div>
--001a113429c0877e6404ee4eaaa6--
--===============5484770775319382141==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
The cryptography mailing list
cryptography@metzdowd.com
http://www.metzdowd.com/mailman/listinfo/cryptography
--===============5484770775319382141==--
