True Crypt is Not Secure

[oshwm]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

So is anyone working on building an 'openfab' or is it such a big task that everyone just backs away in horror? :D


On 28 July 2015 22:04:38 BST, grarpamp <grarpamp at gmail.com> wrote:
>> TrueCrypt has been audited[0] and come through relatively unscathed;
>> I'd trust it over a Microsoft product I'd need to disassemble to
>> examine any day.
>
>You may trust your opensource code but would still need to
>disassemble and audit any critical and closed windows libs and
>system interfaces you compile against, let alone run in / under.
>This is the trouble with closed platforms. You have some luck
>with open unix, but the luck buck currently stops at the iron and
>the hardware is getting worse. And we don't have any open fabs on
>the horizon to solve it. This is BAD.
-----BEGIN PGP SIGNATURE-----
Version: APG v1.1.1

iQI7BAEBCgAlBQJVuAT2Hhxvc2h3bSA8b3Nod21Ab3Blbm1haWxib3gub3JnPgAK
CRAqeAcYSpG1iCCOD/0YW09ajR9GYClZ4eD4bbwxvjBbe7AfhBDurbFYiMm07dM5
wRtbjeheWOLFjBWHVGWFaA7TnUN+z2qAvPqzvJzRXu78tBOXtNtgXh7Ey541Z836
mONsRDeuD7EHOxy4RN/bNsqIanWGUjgAfpuaP7hcgMNF5R2ihcWli2Fl7kdfgv1H
6mFqoMB20NDUetIRqJlr4T8yyRJk3GuRi1netkHL1AW/VAvXECD3HCz3Hj2hAwXK
lKqA2XHFYoZkhdD6/vWTqe8wtiUNd5ICjU5RxqVLbqpQzlnliKARKQpPcKCqTiFZ
BMcPSQHsNKyulGEgZsphXg33edvBoUcud5+a+mE4Cn2UleHbgm3bp/X0P6vBcXv9
A46PlHAEuO+DJaGX3Ophg4yCmC6d97tN2xOQv1lfuJGF5hytPJpDcQQbZDwg0Lxw
T69cl16rQe0lZO/6lXxkOLRo8iex6DEtP98fEEdbvmJyC49SKWEZVGq9663J+ZwI
Qmry6ob1JbKnz9MwlroOm6jGdQZ08sM+1wQzA6hONo0MGhi8ZbKSKjIhumr5TQVy
gHp1FFojxVUctsfTGneHNo8tvk2WJRzezNiH/cLJ41A6yYPVVOyASlxT2tkn9DlO
h0NIDD4UH9juHLDOvdNK4BNKWdDV7khP6bGYx/NwV2RVHys8HhpX+NPq+QeZbw==
=3fLH
-----END PGP SIGNATURE-----