News for hackers. Stuff that matters.
Re:TrueCrypt, the final release, archive by miles on Friday May 30, 2014 @02:26AM (#7820540)
The writing style in this letter is completely different from that on the TrueCrypt page. If this letter had been posted originally, the whole episode would have been viewed much differently. And why does the author of this letter assure readers that "As far as we know, TrueCrypt is utterly uncrackable", while the TrueCrypt.org page (or rather, the truecrypt.sourceforge.net page to which it redirects) screams (in red at the very top), "WARNING: Using TrueCrypt is not secure as it may contain unfixed security issues"?

EDIT: Sorry - as brazzy and NickSharp kindly point out below, the letter was imagined and written by Steve Gibson. As the HN title at the moment is "One of the TrueCrypt Devs Responded", I missed that.

Re:TrueCrypt, the final release, archive by emiliobumachar on Friday May 30, 2014 @02:51AM (#7820594)
Misunderstanding aside, these two statements are not really incompatible:

-"As far as we know, TrueCrypt is utterly uncrackable"

-"WARNING: Using TrueCrypt is not secure as it may contain unfixed security issues"

It makes sense to post such a warning to a product with no known vulnerabilities, if it's to remain unsupported. What if a bug becomes public tomorrow? Are you going to keep current with the news and analyze allegations, despite having given up supporting the tool? These crypto attacks are often pretty hard to understand...

Re:TrueCrypt, the final release, archive by brazzy on Friday May 30, 2014 @02:33AM (#7820552)
Are you talking about the imagined letter that is, uh, not actually from the Truecrypt devs?
Re:TrueCrypt, the final release, archive by miles on Friday May 30, 2014 @02:37AM (#7820567)
Sorry - completely missed that. The title of the HN post at the moment is "One of the TrueCrypt Devs Responded".
Re:TrueCrypt, the final release, archive by NickSharp on Friday May 30, 2014 @02:35AM (#7820562)
I believe you are referring to the "imaginary letter" linked to in that post. As stated, that link is speculation, not an actual response from the devs.