Live data from Hacker News

Adam Langley's Pond: Secure Async Messaging

pond.imperialviolet.org

1–10 of 43 posts

Re: Adam Langley's Pond: Secure Async Messaging

#5

> "Pond seeks to prevent leaking traffic information against everyone except a global passive attacker." My favorite line in the article. It's a nice nod to the fact that this Achilles heel is an issue that he is aware of / takes seriously.

Contrasted with the "forward":

   |Note: recent events have lead to these topics being in the news quite often in recent weeks. However, Pond is not a reaction to those events - it was started nearly a year ago.
Traffic information, of course, isn't the whole conversation, so his wit is appreciated to make light air of the situation, but at the same time he's quite serious about this little project. I'm impressed that it compiles at all on my Arch machine, after his warning to Arch users.

On topic to your comment, unfortunately there's no way to avoid leaking traffic information, or at least the fact that there is traffic at all, to a "global passive attacker" :) gone are the days of radio silence

Re: Adam Langley's Pond: Secure Async Messaging

#8
(Or, how to better organise a discreet relationship with the Director of the CIA.) from https://github.com/agl/pond (the source) is a good elevator pitch, for people (like me) who are taking their time getting what this is.

also, is code like this https://github.com/agl/pond/blob/master/server/server.go#L15... just extreme defensive programming? or is there some other reason for the check (eg is not everything locked)?

also, does 2. A GPA can learn when messages are sent to a non-home server and which server that is. get weaker if there are many users?

and why is it so quiet here? am i asking dumb questions? i've been deleting the ones i work out answers to!

Re: Adam Langley's Pond: Secure Async Messaging

#9

> "Pond seeks to prevent leaking traffic information against everyone except a global passive attacker." My favorite line in the article. It's a nice nod to the fact that this Achilles heel is an issue that he is aware of / takes seriously.

Adam Langley is the real deal. He's also a large part of the reason Google managed to deploy forward secrecy, and the author of the Golang TLS stack.

Re: Adam Langley's Pond: Secure Async Messaging

#10
post #4

I can not forgive Adam he removed the DANE support from Chrome in spite of fact that he was the author of the draft standard http://datatracker.ietf.org/wg/dane/

Why does Langley need your forgiveness for not supporting DANE? DANE is arguably worse than X.509 CAs.
Post reply on HN