Live data from Hacker News

Adam Langley's Pond: Secure Async Messaging

pond.imperialviolet.org

31–40 of 43 posts

Re: Adam Langley's Pond: Secure Async Messaging

#31
If anyone wants to test this with me, you'll find my contact details in my HN profile and on https://grepular.com/

Both of which contain my PGP details. So by sending my your handshake message encrypted with my key, I'll reply with my handshake message encrypted with your key, then we can test.

Re: Adam Langley's Pond: Secure Async Messaging

#32

> For secure, synchronous communication we have OTR and, when run over Tor, this is pretty good. But while we have secure asynchronous messaging in the form of PGP email, it's not forward secure and it gratuitously leaks traffic information. This is probably a stupid question, but what exactly is the distinction here? Why can't we just think of the "asynchronous messaging" email-equivalent as long, drawn-out synchron…

Can you send a message to someone who's currently offline using OTR? It seems to use diffie helman, so I'd expect not.

That's an implementation detail. You could pack the handshake into automated email messages handled by a proper client. Obviously this would not work with any old client since you're effectively layering another protocol on top of email.

Re: Adam Langley's Pond: Secure Async Messaging

#35
post #10

Earlier quoted context omitted.

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

Why? Because DNSSEC can be attacked by the DNS root? It seemed to be our best attempt to get SSL for every website. CA-based certificates just won't cut it.

Because replacing a PKI run by companies that the NSA can coerce with a PKI run by the US Government doesn't seem like a good plan? That, along with the litany of reasons why DNSSEC is a terrible design; that it doesn't secure queries from stub resolvers where the need is greatest; that it publishes internal zone names; that it breaks the resolver API and will inevitably create outages; I can go on.

(I doubt this is what's held up DANE; rather, the unreliability of DNS compared to hyper-optimized HTTPS/TLS connections is the issue there; browser vendors care about milliseconds.)

Re: Adam Langley's Pond: Secure Async Messaging

#37
post #28

(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…

I think it's just that nobody knows the answers, mostly. HN is not great for questions that require thought. Also, btw, I still have your AMOP,a nd it would be awesome to see you again.

we've not visited argentina for years so we must be due a trip. if/when we do i'll ping you and you can give me that back during a meal at some nice restaurant...

Re: Adam Langley's Pond: Secure Async Messaging

#38
post #17
post #13

I don't know about you people but I can't access this site in latest firefox: Secure Connection Failed An error occurred during a connection to pond.imperialviolet.org. Peer attempted old style (potentially vulnerable) handshake. (Error code: ssl_error_unsafe_negotiation) The page you are trying to view cannot be shown because the authenticity of the received data could not be verified. Please contact the website own…

This is kind of ironic considering it's Adam Langley's website, but it appears his server is not indicating that it supports secure renegotiation, and apparently in the latest Firefox that's grounds to refuse a connection[1]. See: https://www.ssllabs.com/ssltest/analyze.html?d=pond.imperial... https://wiki.mozilla.org/Security:Renegotiation https://community.qualys.com/blogs/securitylabs/2010/10/06/d... If you set se…

iirc renegotiation in openssl is mad broken, in which case, mad props to adam :)

Re: Adam Langley's Pond: Secure Async Messaging

#39

Earlier quoted context omitted.

Here we go again :-)

can anyone point to a link that explains X.509 s shortcomings? I'd really like to read up on that but can't find any sane info.

Haha consider the possibility that some of the insane ranting you hear about x.509 is actually balanced and accurate criticism :-)

Re: Adam Langley's Pond: Secure Async Messaging

#40
post #28

Earlier quoted context omitted.

I think it's just that nobody knows the answers, mostly. HN is not great for questions that require thought. Also, btw, I still have your AMOP,a nd it would be awesome to see you again.

we've not visited argentina for years so we must be due a trip. if/when we do i'll ping you and you can give me that back during a meal at some nice restaurant...

awesome! :)
Post reply on HN