Sorry, meant to login FWIW before posting that:
Thank you. Mine:

sha1sum *
16e6d7675d63fba9bb75a9983397e3fb610459a1 *TrueCrypt 7.1a Mac OS X.dmg
7689d038c76bd1df695d295c026961e50e4a62ea *TrueCrypt Setup 7.1a.exe
1d503ddb5f619ca868ea42bd7435f0dff5975997 *TrueCrypt_v7.1a.zip
c2a8c78a23f97ffb17bf47448c9f2daa3c8f80cd *truecrypt-7.1a-linux-console-x64.tar.gz
a53a7a609a25d9a1e33f720ce5c0265ddd4e8b25 *truecrypt-7.1a-linux-console-x86.tar.gz
086cf24fad36c2c99a6ac32774833c74091acc4d *truecrypt-7.1a-linux-x64.tar.gz
0e77b220dbbc6f14101f3f913966f2c818b0f588 *truecrypt-7.1a-linux-x86.tar.gz


sha256sum *
04db58b737c05bb6b0b83f1cb37a29edec844b59ff223b9e213ee1f4e287f586 *TrueCrypt 7.1a Mac OS X.dmg
e95eca399dfe95500c4de569efc4cc77b75e2b66a864d467df37733ec06a0ff2 *TrueCrypt Setup 7.1a.exe
4b87892bf9f217deb28eb67570803664512613aee7cf92df6e31dcca6e26fab7 *TrueCrypt_v7.1a.zip
3f48210cca1c17f433572845586d5e2a1a717a545480d136cb970689a44e3c32 *truecrypt-7.1a-linux-console-x64.tar.gz
7871a40aaca4556d2c6f3377d62347bc38302f4f1ef191e7d07123bdf4a4d008 *truecrypt-7.1a-linux-console-x86.tar.gz
43f895cfcdbe230907c47b4cd465e5c967bbe741a9b68512c09f809d1a2da1e9 *truecrypt-7.1a-linux-x64.tar.gz
9d292baf87df34598738faef7305cddaa15ea9f174c9923185653fb28f8cfef0 *truecrypt-7.1a-linux-x86.tar.gz


md5sum *
89affdc42966ae5739f673ba5fb4b7c5 *TrueCrypt 7.1a Mac OS X.dmg
7a23ac83a0856c352025a6f7c9cc1526 *TrueCrypt Setup 7.1a.exe
2c664c527ee622b17da6fcd76979fba4 *TrueCrypt_v7.1a.zip
eb71d8108afec84d4dc72c523b57763a *truecrypt-7.1a-linux-console-x64.tar.gz
218d80bbe69cb63dba124efb62600e0f *truecrypt-7.1a-linux-console-x86.tar.gz
bb355096348383987447151eecd6dc0e *truecrypt-7.1a-linux-x64.tar.gz
09355fb2e43cf51697a15421816899be *truecrypt-7.1a-linux-x86.tar.gz

# file sizes
9526318 TrueCrypt 7.1a Mac OS X.dmg
3466248 TrueCrypt Setup 7.1a.exe
24467591 TrueCrypt_v7.1a.zip
1642506 truecrypt-7.1a-linux-console-x64.tar.gz
1648060 truecrypt-7.1a-linux-console-x86.tar.gz
2667681 truecrypt-7.1a-linux-x64.tar.gz
2644819 truecrypt-7.1a-linux-x86.tar.gz

The real issue at present is people trading freedom for convenience *without knowing they are doing so or being aware of exactly what their costs are*. And by the time they find out, it might well be too late. As you pointed out, the value of someone like RMS and his message is to illuminate what is happening so people can make that tradeoff in a more informed manner.

Stop spinning this as a personal responsibility/freedom issue. That's complete BS. The real issue at stake is the freedom of other people to exist, and to exist without injury caused by your stupidity.

I'd rather you get busted if you fuck up too, but instead, what will likely happen when you fuck up is, someone will lose an arm or leg...or a life. Stop thinking about whether you will be "found at fault," and start thinking about someone losing their life or limb, because that is the consequence of relevance here.

xkcd has this covered as usual:

http://xkcd.com/1279/

One other point to add to the parent: Whatever you give up now, whether it's metadata alone or metadata + content, consider that this will be stored forever. It might be become easier/legal to probe into these several years down the line. If the govt's storage systems are incompetent, they might all even become public at some point.

It is /still/ worth protecting what you can.

Parent is modded funny, but is actually more insightful than funny:
https://en.wikipedia.org/wiki/Bit_(horse)

Which is exactly what mailvelope (mailvelope.github.com) does (I'm in no way associated with them).

Here it is: http://mailvelope.com/


- works with Chrome, Firefox in development
- provides end-to-end encryption
- reduced the complexity of creating/setting up new keys etc. to a bare minimum. I've sent instructions to non-tech friends who set it up in a few minutes with some very basic handholding.
- is not mail client specific - all it does is encrypt a textarea, so you can get it to work, for instance, on google calendar in addition to yahoo mail or gmail or whatever
- uses its own editor so you can avoid using the web gmail provider's textarea (gmail, for instance, autosaves drafts)

Disclaimer: I am in absolutely no way connected with mailvelope. I'm just a very happy user.

And even if the arguments on the blog article are poorly made or outright incorrect, my personal hope is that it would initiate a more technically correct and interesting debate here that will help us all understand DDG and similar search engines better.

What's that? No, I'm not new here. I can still hope, can't I? :)

I agree that it seems to be a biased article with not much emphasis on quality. However:

1) Slashdot likely has a higher proportion of DDG users than the general population given the interest in privacy, security, and tech here.

2) Since there are very few DDG users in general (compared to google, etc.), it's difficult to find an opposing view to DDG's stance. An opposing view can be helpful in seeing where the problems lie, and what all a DDG user might want to be concerned about.

Hence, even though this blog might lack any credibility at all (and its misspellings and seeming bias don't help it any), it still holds some value here on Slashdot, IMHO.

This. And it gets even worse if you have a diagnosis that you don't agree with (much more common than you think). That stays on your centralized, global record forever too. It doesn't take much imagining to see the consequences.