News for hackers. Stuff that matters.
Re:How Lavabit Melted Down by betterunix on Tuesday October 08, 2013 @02:47PM (#6516994)
"It was the best current technology could offer"

Sure, if we ignore the existence of things like PGP, S/MIME, smart cards, and the dozens of other ways we can have secure email without relying on some trusted third party like this.

"this technology was not meant to deal with the oppressive government that can compel any company to reveal any information"

Then it was not meant to deal with the evil hacker who takes control of the server and grabs valuable information.

"As soon as Ladar..."

There's the handwave. The security of the system depends not on technology, math, or physical laws, but on the whims of just one man. What if Ladar was less principled?

Re:How Lavabit Melted Down by michaelt on Tuesday October 08, 2013 @05:22PM (#6517940)

  Sure, if we ignore the existence of things like PGP, 
  S/MIME, smart cards, and the dozens of other ways we can 
  have secure email without relying on some trusted third 
  party like this.
As I understand it Snowden was using Lavabit to communicate with journalists who didn't themselves have/use/understand PGP. Lavabit is technology you can use even if no-one else uses it.

How do PGP and S/MIME solve the bootstrapping problem, where no-one uses them because no-one uses them?

Re:How Lavabit Melted Down by betterunix on Tuesday October 08, 2013 @05:57PM (#6518087)
There is no bootstrapping problem. Snowden was also able to get journalists to use OTR, without relying on some web interface with questionable security claims. The problem with PGP and S/MIME is that the existing software is too hard to set up. It is hard to tell journalists to go use Thunderbird, get Enigmail set up, and publish a key. The situation is even worse with S/MIME, despite the built-in support in many email clients.

Basically, the problem is that PGP and S/MIME as they exist today are (and I shudder to say it) too security conscious. The reality is that most users are not going to take the time to maintain their public keys, to verify others' public keys, etc., nor are most users going to spend the time to get their keys verified by a CA. We need a "lite" PGP client that is less obnoxious about using untrusted keys, and basically a "newbie" PGP that is more vulnerable to active MITM attacks (which are actually much harder to pull off than one might expect). It would also be nice if public keys could be easily published via QR codes, so that someone can literally hand their public key to another person.

The worst thing we can do is lie to people about the security they receive e.g. telling them things like "Lavabit is set up so that nobody but you can read your email!"

Re:How Lavabit Melted Down by lifeisstillgood on Wednesday October 09, 2013 @04:09AM (#6519952)
qr codes for gpg public keys - sounds a great idea. Any idea why no one done it yet - seems like it could be a simple transform from an ASCII armoured output.

Bookmarking reply

Re:How Lavabit Melted Down by XorNot on Wednesday October 09, 2013 @06:57AM (#6520473)
You have to use a very large QR code to do it. It won't fit on a business card and phones are picky about scanning them.
Re:How Lavabit Melted Down by betterunix on Wednesday October 09, 2013 @08:41AM (#6520861)
Sure, but we have key servers for distributing the actual keys. You would only need the fingerprint in the QR code.
Re:How Lavabit Melted Down by XorNot on Wednesday October 09, 2013 @11:05AM (#6521656)
Kind of defeats the point - how do you know you're downloading the private key you scanned?

While someone might have their business cards replaced, it's a lot easier just to send a different key to someone.

Re:How Lavabit Melted Down by betterunix on Wednesday October 09, 2013 @01:14PM (#6522495)
"Kind of defeats the point - how do you know you're downloading the private key you scanned?"

Assuming that "private key" is a typo (you download public keys), you can just check the fingerprint of the key against the fingerprint you were given. That is easily automated.

Re:How Lavabit Melted Down by XorNot on Thursday October 10, 2013 @05:02AM (#6526444)
This puts us back in the same kind of problem that was being complained about though - keyservers, publishing keys etc.
Re:How Lavabit Melted Down by betterunix on Thursday October 10, 2013 @07:54AM (#6526912)
Not really. The problem is not about publishing keys or key servers, but with the cumbersome process of having to enter a hexadecimal string (and having to check an even longer string). The point of using QR codes is to simplify things: the user just scans a QR code, and the key is fetched and assumed to be valid (i.e. no need for the user to check fingerprints).
Re:How Lavabit Melted Down by lifeisstillgood on Wednesday October 09, 2013 @12:32PM (#6522260)
I thought a QR code could be effectively any size - I certainly remember a Japanese billboard that used shadows etc.

A QR code can have ~4000 chars of a-z and ~3000 Latin1 iirc

so with my limited gpg knowledge that handles my public key quite happily.

would be interested on the business card front though

Re:How Lavabit Melted Down by smsm42 on Tuesday October 08, 2013 @06:16PM (#6518201)
The mere fact Snowden was talking to someone in Guardian would be quite damning even if the contents of the messages were not known. The problem in catching the leak is knowing who's talking, not what they're saying - finding out what is the easy part, who is the hard one. Access to envelope info solves the who part, and full access to mail server gives full access to envelope.
Re:How Lavabit Melted Down by smsm42 on Tuesday October 08, 2013 @06:13PM (#6518190)
How PGP or S/MIME would help you if any provider could be required to turn over all the traffic it gets, unencrypted? The only way you could securely communicate is peer-to-peer with the trusted party, but the email doesn't work this way. Unless you always send mail directly to your target's SMTP server which is hosted by the recipient himself (which kind of defies the whole idea of having email as a service and turns it into just a peer-to-peer chat with funny headers), the adversary would have access at least to the envelope information.

>>> Then it was not meant to deal with the evil hacker who takes control of the server and grabs valuable information.

Indeed, it is not. If the hacker gets full control of your mailserver, at least your envelope information is completely compromised.

>>> The security of the system depends not on technology, math, or physical laws, but on the whims of just one man

This is completely false. Security depended on adversary not having full access to the Lavabit servers, not on Ladar's "whim". As soon as Ladar realized there's no possibility of legally providing it in the US, he closed the service. Assuming your adversary doesn't have full access to your service is kind of a precondition of using the service as means of security. That's like using lock is assuming the adversary does not have the key, if he does, the lock is useless as a security measure. As soon as Lavabit became essentially useless for the purpose it was created, it was shut down.

Re:How Lavabit Melted Down by betterunix on Tuesday October 08, 2013 @11:52PM (#6519294)
"the adversary would have access at least to the envelope information."

This is a strawman, because Lavabit never did anything to protect headers. What you are missing is that Lavabit could respond to a demand for plaintext, if Ladar were willing to do so; on the other hand, Google cannot give anyone access to the plaintexts of PGP encrypted messages that I send through their servers because of technical barriers. That is the point of doing your encryption locally, and that is why security and privacy are not a service.

"Indeed, it is not. If the hacker gets full control of your mailserver, at least your envelope information is completely compromised."

Except that with Lavabit, an attacker could also get all your message bodies.

"Security depended on adversary not having full access to the Lavabit servers, not on Ladar's "whim"."

Let's put it this way: if you were involved in a lawsuit against Ladar, would you trust your communications with your lawyer to Lavabit? Of course not, because Ladar could have modified the code at any time and without alerting his users at all to read any plaintext that he wanted to read. If he had been willing to cooperate with the government, he could have and nobody would have a clue.

"Assuming your adversary doesn't have full access to your service is kind of a precondition of using the service as means of security."

In other words, security is not something you can get as a service. The entire model is fundamentally and fatally broken.

"That's like using lock is assuming the adversary does not have the key, if he does, the lock is useless as a security measure"

No, it is like storing your key with the bartender at your favorite night club and assuming that he will not allow your adversaries to use it.

"As soon as Lavabit became essentially useless for the purpose it was created, it was shut down."

It was shut down because Ladar chose to shut it down rather than capitulate. He could have chosen to keep it going while the government eavesdropped on it instead. That means that, as I said, security boiled down to Ladar and his principles. That is why PGP and S/MIME provide you with better security: mathematics are not subject to the choices that human beings make, and with PGP, S/MIME, etc. your security is a matter of mathematics.

Re:How Lavabit Melted Down by smsm42 on Wednesday October 09, 2013 @03:31AM (#6519870)
>>> This is a strawman, because Lavabit never did anything to protect headers.

Since SSL keys are mentioned, I assume SSL was used in communication. This means the claim that Lavabit did nothing to protect headers is false.

>>> Except that with Lavabit, an attacker could also get all your message bodies.

This is true, however body of the message may contain encrypted information, which is useless to observer. Envelope information can not be encrypted in a way that is not readable by the mail server, that's the point of the mail server.

>>> The entire model is fundamentally and fatally broken.

That is kind of what I was saying - that current technology of the email can not do what Lavabit tried to do if the adversary can do what the courts said it can do. I'm not sure what you're disagreeing with here.

>>> He could have chosen to keep it going while the government eavesdropped on it instead.

That would be a betrayal of his user's trust, since any claim about what his service does would be necessarily false and he would become a liar if he ever claimed his server allows to communicate securely. I agree that this boils down to one's principles. I think a principle of "don't lie to your customers" is a good one to have.

>>> That is why PGP and S/MIME provide you with better security

No they do not, unless you can establish a peer-to-peer channel with your other party. In which case you're not using email anymore. Neither PGP nor S/MIME can prevent adversary from collecting envelope information in emails, and unability to do this is what made Lavabit impossible to continue.

>>> mathematics are not subject to the choices that human beings make,

You seem to be either genuinely confused about how email works and what running a secure email server involves, or trying to say something else than you're actually saying, or not making any sense. There are no "choices" that allow you to create secure email server in situation in which Lavabit found itself.

Re:How Lavabit Melted Down by betterunix on Wednesday October 09, 2013 @08:56AM (#6520934)
"Since SSL keys are mentioned, I assume SSL was used in communication. This means the claim that Lavabit did nothing to protect headers is false."

That is like saying that GMail is protecting the privacy of your headers, because GMail uses SSL.

"This is true, however body of the message may contain encrypted information, which is useless to observer"

Except that in the case of Lavabit, that encryption was just a side show since all the cryptographic operations were performed on the server.

"current technology of the email can not do what Lavabit tried to do if the adversary can do what the courts said it can do"

Except that someone who encrypts their message bodies before sending the message i.e. performing cryptographic operations locally leaves the server unable to fulfill demands for plaintexts.

">>> That is why PGP and S/MIME provide you with better security

No they do not, unless you can establish a peer-to-peer channel with your other party. In which case you're not using email anymore."

Really, you think I am not using email anymore if I am running my own personal mail server? It is also false to claim that one must have a peer-to-peer system to protect header information, or that PGP on its own is not enough. You could broadcast an encrypted message via Usenet. You could use anonymous remailers (e.g. "Type I" remailers, which use PGP). In all these cases, however, you need to perform your cryptographic operations locally.

"There are no "choices" that allow you to create secure email server in situation in which Lavabit found itself."

Sure there are: Ladar could have sold smartcards instead of selling cryptography as a service. There, one design decision that could have given his users meaningful security while still maintaining the convenience of webmail. To boost security even more, those smartcards could be coupled with a thumb drive that includes the necessary client software, so that Lavabit could not pull a Hushmail on its users.

Re:How Lavabit Melted Down by smsm42 on Wednesday October 09, 2013 @01:40PM (#6522645)
>>> That is like saying that GMail is protecting the privacy of your headers, because GMail uses SSL.

It does. Unlike Lavabit, though, there is ample reason to assume they invalidate this protection by granting governmental adversaries access to the information stored on their servers - the thing that Lavabit refused to do, at least on mass scale.

>>> since all the cryptographic operations were performed on the server.

I don't see what precludes you from sending emails already encrypted. Security has layers. You are not limited to using just one.

>>> leaves the server unable to fulfill demands for plaintexts.

You forgot to read the part of my answer where I use the word "envelope".

>>> Really, you think I am not using email anymore if I am running my own personal mail server?

It is irrelevant what you personally are doing - it is relevant what Lavabit was trying to do. They were trying to provide certain service - for people that - like, I assume, most of Guardian journalists - are not technically advanced enough to run a secure mail server on their personal computer and set up everything else in a way that allows it to accept email from the internet. This proved impossible, thus Lavabit is not with us anymore. That was my whole point.

>>> Ladar could have sold smartcards instead of selling cryptography as a service.

He could also have sold hotdogs and Carribean timeshares, how that's related to the topic? He was trying to create a secure email as a service - for those that can not create the same by themselves, which in 99.999% of the population of email users. Not provide solution for completely different problem such as key exchange and creating VPNs and other stuff.

Re:How Lavabit Melted Down by intelliot on Tuesday October 08, 2013 @05:36PM (#6517993)
I want secure email but I have yet to figure it out. What are "the dozens of other ways we can have secure email"? Honest question
Re:How Lavabit Melted Down by vividmind on Tuesday October 08, 2013 @03:40PM (#6517321)
Have you heard about "thermorectal decryption"?