Slashdot Mirror
Is Hushmail Still Safe?
Ringo Kamens writes to ask if the use of Hushmail can still be considered a secure method of communication:
"For a long time, Hushmail was considered a very secure email provider until an affidavit (PDF) from a DEA agent in 2007 showed that they had handed over 12 CDs of possibly decrypted data to law enforcement. Now, Cryptome has posted that the Hushmail encryption program is no longer the same program for which Hushmail releases their source. Is Hushmail even safe to use anymore?"
you're probably better off encrypting your emails yourself instead of allowing a third party to convince you that they have encrypted it.
...one can't trust encryptinon if it is done off site. Point.
If you want your communication secure encrypt it on your computer which you trust. This is the only way to keep it secure...
of course it is.
its just that simple.
unless you can review (and understand) what's going on, line by line, you can't REALLY trust it.
what is at stake, here? the gov's are at an all-time power-grabbing frenzy for violating your personal privacy. corporate, too, for that matter.
it was once said that no one would be allowed to sell or market encryption tech that 'the big guys' would not be able to break; meaning our government. I once worked at a picture phone company (mid 80's) that was starting to go down the 'encrypt your video phone call' path (using old switched56 tech) and we were told we could NOT do our own encryption unless it was 'breakable' by, well, certain agencies.
believe what you want, but no commercial (or even freeware) encryption that is avaiable to YOU AND I will be worth anything other than 'for show'.
I fully believe that. you would do well to mistrust your government, too, given how greedy they have become on the rights-grab thing.
locks only keep honest people out. there is NO WAY to keep the gov out, anymore. and that means that others, too, have backdoors (you think the gov is the only entity that can 'get to' this kind of stuff?)
anyone who trusts encryption for their life, in this day and age, is deluded.
--
"It is now safe to switch off your computer."
Depending on how you define secure then no, Hushmail is not.
Personally if I want to send encrypted mail I will do so on a PC I have direct control over, I will carry out the encryption before the email goes anywhere. And depending on the type of encryption used, I might even carry out the encryption on a terminal which has no network connections etc and after encrypting the mail will shutdown the PC and leave it shutdown for a while - this setup would have no swap partition etc, or if it did it would be a minimum of baseline encrypted.
As for Hushmail - its secure if you trust them to use suitable encryption algorithm, key material, psuedo random number generator, secure processes (not the program kind, the how to do the job kind), secure network, no shady or otherwise agreements with third parties (inc. governments) to provide decrypted data, not to store your orginal plain-text mail for any longer than the time it takes to encrypt it, securely erase the plain-text version etc etc etc. Probably enough holes to drive a bus through...
--- Users are like bacteria -> Each one causing a thousand tiny crises until the host finally gives up and dies.
Any developer that has worked closely with jar (zip) files should have immediately notice a possible issue with this announcement. If you use the jar tool to create a jar archive with its default options, it embeds a new MANIFEST.MF file which has a new creation time; therefore, you will get a different jar checksum even if you are archiving the same exact contents. It would have been simply possible that the Hushmail build process created a new jar file (with identical files) for each type of software distribution that they use. The only way we can be sure is to compare the file list and checksum for each file inside of the jar archives.
rely on face to face contact if you want your communications to be secure.
Are you smoking?
Meeting face to face is the worst possible way for secure communications. It allows for easy snooping by anyone on you and the person you're meeting, and even the fact that you are meeting with a person can taint you if they are on the terrorist list or "watch list".
Public email such as thepiratebay's slopsbox is way better. Be sure to post and read from a public library or similar, with no cameras.
It's just a matter of time. This almost always happens faster than the designer imagined it would take.
"The ability to delude yourself may be an important survival tool" - Jane Wagner -
Was either Thomas Jefferson or Lazarus Long. Both of them were well worth listening to.
Help stamp out iliturcy.
Oh, please. You've done a good job of using impressive terms to sound like you know what you're talking about. If you want to talk about the real-world risks of having your crypto broken, then you need to consider all the real-world methods by which your crypto could be broken. It doesn't matter that a one-time pad can be theoretically proved to be invulnerable to certain kinds of attacks, to which various symmetric and asymmetric ciphers are theoretically vulnerable. What matters is the actual types of attacks that are practical and likely, and the actual problems you'll have in the practical implementation of a particular method. If you're using a one-time pad, then there are several obvious, well-known things that can go wrong: (1) you have to physically exchange the one-time pads, which may be difficult to do (and do securely) if the NSA is really following you everywhere, opening your mail, etc.; (2) both parties have to maintain the security of their own copies of the one-time pads, which may be difficult to do if the NSA is really determined to get them; (3) there is a tendency for users to get lazy and reuse a one-time pad, which then makes you vulnerable to certain kinds of attacks. Standard symmetric and asymmetric ciphers are more or less immune to these problems (#1: swapping passwords securely is a lot easier than swapping large amounts of binary data securely; #2: you can keep the password in your head instead of stuffing a keychain drive under your mattress; #3: no such issue). Yes, there are also certain kinds of attacks to which standard ciphers are vulnerable and one-time pads invulnerable (e.g., dictionary attacks on your password, shoulder-surfing,...) One-time pads are not magic pixie dust for cryptography. There is no magic pixie dust for cryptography. The good news is that we're living in a golden age of privacy, in the sense that you can legally, publicly get software to do encryption so good that essentially your main worry is no longer the encryption, it's the social/personal/legal issues surrounding its implementation.
Find free books.
Anytime your private encryption key is "over there" you are at risk. If your private key is stored on *their* servers in such a manner that *they* can get to it, your privacy is at risk.
As a software developer, I'm in a pilot program to use encryption for digital signatures. Despite the relative simplicity of using openSSL functionality, it's been surprisingly painstaking and laborious to put everything together.
See, real security requires outright paranoia. How do you prevent your CA key from being compromised, in such a way that you can all-but guarantee that it hasn't been? To do this, you have to make it not only unlikely, but impossible to be compromised in every conceivable way. How do you prevent your client's private key from being compromised, in such a way that you can all but guarantee it? How do you prevent a malicious client from obtaining a signed certificate? How do you prevent 3rd parties from MITM attacks? How do you provide high-level security for all the above, while still providing redundancy for disaster recovery? How do you prevent compromises stemming from a social engineering attack?
Not including implementation and ongoing maintenance of these procedures, the cost of just proving that you have all these measures in place runs to many thousands of dollars!
A solution that answers all these and every conceivable related question is surprisingly difficult, and many, if not most, of the problems are not technical, but social.
I have no problem with your religion until you decide it's reason to deprive others of the truth.
That used to be funny before we discovered our governments were actually torturing people. Nowadays I don't find it funny.
Seriously if it's a commercial company based in the US, forget about security. They can easily be pressured to do everything the government wants.
If you want security you have to do it yourself. Install Gnu Privacy Guard and encrypt all your e-mails. Then use TOR hidden services to set up your own e-mail servers to be sure your traffic information will stay private.