News for hackers. Stuff that matters.
Re:True Goodbye: ‘Using TrueCrypt Is Not Secure’ by jxf on Thursday May 29, 2014 @01:04PM (#7817249)
My current favorite insane/facetious conspiracy theory on this:

    "WARNING: Using TrueCrypt is not secure as ..."
     WARNING: Using TrueCrypt is (n)ot (s)ecure (a)s ...
                    TrueCrypt is (n)ot (s)ecure (a)s ...
                                 (n)ot (s)ecure (a)s

                    TrueCrypt is (n)   (s)      (a)
Re:True Goodbye: ‘Using TrueCrypt Is Not Secure’ by sliverstorm on Thursday May 29, 2014 @01:58PM (#7817610)
I love this game!

    "WARNING: Using TrueCrypt is not secure as ..."
    "WARNING: Using True(C)rypt (i)s not secure (a)s ..."

                        (C)     (i)             (a)
Again!

    "WARNING: Using TrueCrypt is not secure as ..."
    "WARNING: Using TrueCrypt i(s) n(o)t (s)ecure as ..."

                               (s)  (o)  (s)
Re:True Goodbye: ‘Using TrueCrypt Is Not Secure’ by weaksauce on Thursday May 29, 2014 @07:21PM (#7819227)
Not that I think it was intentional, but putting something in that is not grammatically correct like the op version and with no spacing is much stronger than picking random letters from the words to prove a point.
Re:True Goodbye: ‘Using TrueCrypt Is Not Secure’ by claar on Thursday May 29, 2014 @10:26PM (#7819861)
It's grammatically correct, read the whole sentence. It just looks odd when you take half the sentence out of context.
Re:True Goodbye: ‘Using TrueCrypt Is Not Secure’ by ParkerK on Thursday May 29, 2014 @01:37PM (#7817472)
Another interesting thing is that in the diff for 7.1a and 7.2 the author changed U.S. to United States several times. Some people think this is to draw attention to it being related to the US government
Re:True Goodbye: ‘Using TrueCrypt Is Not Secure’ by danielweber on Thursday May 29, 2014 @01:48PM (#7817549)
But other people point out that Visual Studio changed its default name for America from the former to the latter.
Re:True Goodbye: ‘Using TrueCrypt Is Not Secure’ by detcader on Thursday May 29, 2014 @02:53PM (#7817903)
>>> s="""If you have files encrypted by TrueCrypt on Linux:

Use any integrated support for encryption. Search available installation packages for words encryption and crypt, install any of the packages found and follow its documentation"""

>>> ''.join(a[0] for a in s.split())

'IyhfebToLUaisfeSaipfweaciaotpfafid'

That short string contains "beast of the apocalypse" [1] plus some other letters ('iuififwaifafi')

[1] https://en.wikipedia.org/wiki/The_Beast_(Revelation) - "The second beast is described in Revelation 13:11-18 and is also referred to as the false prophet."

Re:True Goodbye: ‘Using TrueCrypt Is Not Secure’ by pekk on Thursday May 29, 2014 @04:59PM (#7818559)
When you harbor some pet assumption, the entire world conspires to verify your assumption.
Re:True Goodbye: ‘Using TrueCrypt Is Not Secure’ by eruditely on Thursday May 29, 2014 @07:20PM (#7819224)
More random tidbits of folk-wisdom. This neither helps us further along on any idea(for/against/neither). Merely a blank truism.
Re:True Goodbye: ‘Using TrueCrypt Is Not Secure’ by verytrivial on Thursday May 29, 2014 @01:14PM (#7817298)
Well the very next sentence continues "This page exists only to help migrate existing data encrypted by TrueCrypt" which could easily be read as a prepared response to the person brandishing the NSL who is now annoyed that the authors have suddenly decided that right NOW is an 'entirely natural' time to end the project.
Re:True Goodbye: ‘Using TrueCrypt Is Not Secure’ by ToastyMallows on Thursday May 29, 2014 @01:08PM (#7817269)
Obligatory Half-Life 3 is confirmed, 9/11 was an inside job, etc. etc.
Re:True Goodbye: ‘Using TrueCrypt Is Not Secure’ by madaxe_again on Friday May 30, 2014 @04:38AM (#7820821)
Yeah seriously, take of your tin-foil hat, why would the NSA be interested in an encryption product?

Oh, wait, it's entirely feasible.