EvilZone

You're missing the point. The bulk data collection isn't about some schmuck flirting on Facebook. They're not tracking down terrorists either, that's bullshit. The reason for harvesting huge amounts of data like this, is to use it retroactively. You can smear political opponents, obtain vital economic intelligence (including trade secrets), aid domestic and crush foreign corporations, make predictions about societal behaviors at large through sentimental analysis, blackmail anyone you please and maintain information hegemony.

Go read up on the FBI under the administration of J. Edgar Hoover to see what happens in situations like these. Although, this is far, far worse than anything Hoover was ever capable of.

Are you honestly so blind that you do not realize the potential of full information awareness? This is the closest thing to omniscience there is. You do not want a government to be omniscient.

Apparently, they've officially announced that development is over and that people should migrate to BitLocker (Microsoft's integrated full disk encryption).

http://truecrypt.sourceforge.net/

Of course, nothing is as it seems.

Some insight from the /r/netsec thread:

TL;DR: Assumption #1 The website is presumed hacked, the keys are presumed compromised, the binary on the website is capable only to decode encrypted data, not encode, and may contain trojan (although I didn't find any, but don't believe me). The binary is signed with the valid (usual) key. All old versions are wiped, the repository is wiped too. Please do not download or run it. And please don't switch to bitlocker.

Latest working version is 7.1a. Version 7.2 is a hoax, although it's signed by a valid key and seems like was built on the usual developer PC (there are some paths like c:\truecrypt-7.2\driver\obj_driver_release\i386\truecrypt.pdb, which were the same for 7.1a).

On the SourceForge, the keys were changed before any TrueCrypt files uploaded, but now they are deleted and the old keys got reverted back.

Why I think so: strange key change, DNS record changed, why bitlocker?

Assumption #2 Something bad happened to TrueCrypt developers (i.e. take down or death) or to TrueCrypt itself (i.e. found the worst vulnerability ever) which made them do such a thing.

Why I think so: all files are with valid signatures, all the releases are available (Windows; Linux x86, x86_64, console versions, Mac OS, sources).

SourceForge sent emails on 22 May, they said they changed password algorithms and everybody should change their passwords.

TrueCrypt developers are unknown and currently there is no way to know who is who and who should we listen to.

From wikileaks twitter https://twitter.com/wikileaks/status/471769936038461440:

    (1/4) Truecrypt has released an update saying that it is insecure and development has been terminated http://truecrypt.sf.net

    (2/4) the style of the announcement is very odd; however we believe it is likely to be legitimate and not a simple defacement

    (3/4) the new executable contains the same message and is cryptographically signed. We believe that there is either a power conflict..

    (4/4) in the dev team or psychological issues, coersion of some form, or a hacker with access to site and keys.

From Matthew Green (one of TrueCrypt auditor) twitter https://twitter.com/matthew_d_green/status/471752508147519488:

    @SteveBellovin @mattblaze @0xdaeda1a I think this is legit.

TrueCrypt Setup 7.1a.exe:

    sha1: 7689d038c76bd1df695d295c026961e50e4a62ea
    md5: 7a23ac83a0856c352025a6f7c9cc1526

TrueCrypt 7.1a Mac OS X.dmg:

    sha1: 16e6d7675d63fba9bb75a9983397e3fb610459a1
    md5: 89affdc42966ae5739f673ba5fb4b7c5

truecrypt-7.1a-linux-x86.tar.gz:

    sha1: 0e77b220dbbc6f14101f3f913966f2c818b0f588
    md5: 09355fb2e43cf51697a15421816899be

truecrypt-7.1a-linux-x64.tar.gz:

    sha1: 086cf24fad36c2c99a6ac32774833c74091acc4d
    md5: bb355096348383987447151eecd6dc0e

Diff between latest version and the hoax one: https://github.com/warewolf/truecrypt/compare/master...7.2

Screenshot: http://habrastorage.org/getpro/habr/post_images/da1/1bf/6a5/da11bf6a5225fa718987ba4e54038fc1.png

See also the HN thread: https://news.ycombinator.com/item?id=7812133

Either this is a full compromise, a false flag psyop to undermine encryption, the developers found a critical security bug and decided to go out with a bang so as to avoid disclosing it and potentially threatening lives, or they got sick of developing the software and so are going out with a bang.

There's also some really interesting speculation that the TrueCrypt devs use a very old Visual C++ version and build system to compile TrueCrypt that is now fully obsoleted with the EOL of Windows XP, and after their inability to port it, decided to just end it all.

Whatever it is, this will be fascinating to watch.

The point here is that you're adding a completely unnecessary level of indirection. Why invoke the shell from an external interpreter when you can just invoke the shell directly?

I understand writing Python scripts for something more complex. But when it's just a bunch of os.system() calls that string together sequential shell commands, that's just idiotic.

Neural network was perhaps erroneous, I was using it as more of a metonym for training on data sets.

From your example, what you seem to be after is to implement a very limited subset of a computational knowledge engine, such as Wolfram Alpha. At least enough to map English phrases to standard Unix commands.

Something similar to this, in effect: https://github.com/pickhardt/betty

Of course, it's likely I'm misunderstanding the scope and purpose of your project.

I'm not sure why you would need to train neural networks for this, specifically. Simple parsers would probably be sufficient.

OpenBSD. Enough said. Look up the rest.

I know for a fact Red Hat and the Fedora Project have ties to the NSA, what with being the testing ground for SELinux, and often suspiciously avoiding cryptographic questions related to their products.

The rest is just rambling, however.