Building a serverless secured dead drop
I ran into this fascinating article (I wrote another blog post discussing it) and that got me thinking. How would I approach building a dead-drop implementation? For that matter, what do we need from a dead-drop system?I think that the following are reasonable (loosely based on what Secure Drop aims for):Completely anonymous:No accounts, no registrations.No server-side state about users. Prevent metadata tracking:It’s not just message contents that are hidden.Cannot tell if A talks to B or C.Acc...
Read more at ayende.com