7 ms·
Hm, feels a bit weird. If they already got served with an order to share the data and they refused to comply, closing down the service instead, what can have ch
by diggan 10y ago
Hm, feels a bit weird. If they already got served with an order to share the data and they refused to comply, closing down the service instead, what can have changed today? Wouldn't this mean that someone else took up the service, agreed to the order and now this will become some sort of honeypot?
Maybe I'm misunderstanding something, but I don't understand how anyone could trust Lavabit to either stick around or actually be private and/or secure.
- maaaats 10y agoOne could hope they now have solved it technically in a way that would make it impossible for them to deliver that kind of data.
- ryanlol 10y agoThat's not exactly possible for an email service provided by a third party.
- imaginenore 10y agoEnd-to-end encryption. Only the users have the keys.
- nailer 10y agoAnd SMTP 571: 'Delivery not authorized' for anyone that sends a plain text message.
- Fnoord 10y agoInteresting but isn't the data already received in plaintext at that point?
- cryptarch 10y agoYou could have a hardened gateway server with read-only storage and that only temporarily stores messages in memory. Maybe a heterogenous bunch if them so you'd have to crack all of them to get all messages. You could periodically reset them in case they still get infected. You could add a transparant proxy that specifically looks for odd, repeated requests, to detect re-infectations. You'd set up alerts for attempts at communication/scanning from those servers, to detect virusses trying to move laterally between the different instances, and/or isolate them from eachother on the network layer. You could have a separare hardware device that scans the memory of these servers to detect tampering. It could also try to detect "plaintextness" and abort as soon as it detects that, so you only have the beginning of the message in memory. This doesn't help when the ISP is recording (and it probably is), but it makes it very hard to retrieve the data from inside the email datacenter.
- dom0 10y ago> You could periodically reset them in case they still get infected. Just have them rebuild themselves from ROM after each processed mail :)
- ryanlol 10y agoThis is retarded. If you try something this you will end up just like lavabit did. You can't rely on solutions that require the operator to remain honest.
- cryptarch 10y agoI don't think it is? Fact is, if you use SMTP, you can only see if the content is encrypted or not once you receive part of it. The techniques I mentioned are to reduce the risk of these (partial) plaintexts being captured, but should be paired with a refusal to deliver. There's no way to stop a user's contacts sending plaintext emails for all the ISP's/intelligence agencies to see, but you can make sure you touch them as little as possible when they do arrive (see GP) and discourage those contacts from doing it again by not delivering/returning error codes. Unless you drop SMTP altogether. I think Riot with E2E is looking pretty good, but it's not been hardened at all.
- ryanlol 10y agoSince you cannot realistically prevent unencrypted emails from being sent to your email service, that's not any kind of a solution. You can't rely on your ability to block them either, or you'll end up just like lavabit did.
- gravypod 10y agoForce end to end PGP encryption for all users? If they do that then I'd assume they could hand over data and say "good luck". They could also setup a P2P delivery & backup system so that it's not guaranteed they have the data. If all the data is encrypted, it's not really an issue to distribute everything (but then again we'd be talking AES512 or better for something crazy like that).
- JshWright 10y agoYou lost me at AES512...
- gravypod 10y agoIf you think AES512 isn't secure enough for your data you should not be hosting your mail server out of your network..... Also, if you have a way to break AES512 I know some people who'd pay a killing to get that information. No litterally there's people who'd kill for that.
- milansuk 10y agoAES512? Is there some 512-bit symmetric key cipher? They could encrypt with two(or more) 256bits keys, but I think just 256bits key is enough for at least next 5years.
- jimnotgym 10y agoI wonder if they will attempt to use a 'canary' system, where each day they post a message to say they have not had to hand over any data to law enforcement. Then if they do get an order that says they cannot discuss, they just don't post the canary.You can't force someone to say something in the US can you?
- geocar 10y ago> Then if they do get an order that says they cannot discuss, they just don't post the canary. There's no need for this (anymore). You're already allowed to disclose (coarsely) the number of NSL you've received[1]. [1]: https://www.justice.gov/iso/opa/resources/366201412716018407143.pdf https://www.justice.gov/iso/opa/resources/366201412716018407... > You can't force someone to say something in the US can you? Unclear. The EFF believes you can't be compelled to lie, however you should consult an attorney with details of the specifics.
- mcherm 10y agoBeing allowed to say "I received between 0 and 999 NSLs affecting 0 to 999 customers" doesn't really convey the same information as a canary.
- shshhdhs 10y agoHow so? Enabling the canary only tells you that one or more was served/obeyed, and can't be used again. To me, 0-999 also tells me that one or more was served/obeyed.
- jasonkostempski 10y agoIs the rule actually 0-999? Because they'd have to get 1000 or more before you knew there was 1 or more.
- geocar 10y agoIt is four pages, the first page is mostly dedications and the last page is mostly blank. It will not take you much time to read the remaining two pages and develop your own understanding. Here is how I am parsing it: The Office of the Attorney General proposes two options: 1. Separate category reports for NSL, FISA content, and FISA non-content requests and customers affected. 2. A single report for all NSL and FISA requests, and a report for customers affected. If you want to distinguish between the different kind of request (category 1) then you can report in blocks of 1,000, while if you don't, you can report in blocks of 250.
- simooooo 10y agoI had just this thought. I think your are correct. They'd have to be willing to hand over your data, or get served and taken down again.
- ycmbntrthrwaway 10y agohttps://darkmail.info/ https://darkmail.info/
- raptaml 10y agoMaybe they relaunched the service in a country where no one cares about US mass-surveillance law and it's enforcing entities...
- koheripbal 10y agoDoesn't using a .com TLD mean they are subject to DNS seizure in the US? ...although maybe it'll redirect once they launch.
- GTP 10y agoThis could be a solution. I'm courious to know, maybe they will give more information when the service will be back online.
- tombrossman 10y agohost lavabit.com && whois 72.249.41.52 Lavabit LLC - Dallas TX and Colo4, LLC - St Louis MO. (Insert your own joke here about Americans not caring about mass surveillance...)
- tr1ck5t3r 10y agoNot enough data yet. As court orders are served against entities, in this case a company, but agreements/contracts can also be made with an entity, a company has some unique properties many living organic entities do not posses, namely the ability to die, go bankrupt, cease to exist and then after a period of time come back to life again. Maybe Lavabit is a phoenix?
- chias 10y agoFeels very weird, especially after checking the page source: /* Count down until any date script- By JavaScript Kit (www.javascriptkit.com) Over 200+ free scripts here! Modified by Robert M. Kuhnhenn, D.O. on 5/30/2006 to count down to a specific date AND time, and on 1/10/2010 to include time zone offset. */ I mean, I get not reinventing the wheel, but given who they are, the fact that they're sourcing scripts from JavaScriptKit.com for something as simple as a countdown timer is odd. It's not even a good countdown script... like, it even has a y2k bug: var today=new Date(); var todayy=today.getYear(); if (todayy < 1000) { todayy+=1900; } Kudos for not just stripping the attribution I guess, but I wouldn't trust whoever put up that website with my email, encryption or no.
- insertnickname 10y agoMaybe it's just because he never bothered to learn JavaScript. The old website was pretty simple.
- chias 10y agoPerhaps. But if you're copy-pasting scripts from other sources into your platform without [being capable of] vetting them, then it fundamentally undermines the security of the platform.
- deleted 10y ago[deleted]
- deleted 10y ago[deleted]