Why Station To Station protocol and not TLS?

I was wondering why have you implemented proprietary secured connection protocol intead of simply using TLS or mTLS?

Author: c0rwin on Riot

TLS was deemed way too complicated. Also existing implementation had there own problems. (Not sure about mTLS?)

The right thing to do today still might be to use some noise variant instead of TLS (still much simpler).

I think proprietary is not the right word here. Everything is open source and uses open source software, too.

Author: @ismail

The right thing to do today still might be to use some noise variant instead of TLS

What do you mean by noise variant? And still not sure why custom protocol is better than a standard one?

Is there a proof of security properties of secure connection protocol? Proof of forward secrecy?

@C0rWin there are definitely known vulnerabilities in the current Secure Connection protocol, namely it was vulnerable to this attack: vnhacker.blogspot.com The Internet of Broken Protocols: Showcase #1 (complete list of showcases: https://vnhacker.blogspot.com/search/label/The%20Internet%20of%20Broken%20Protocols ) Updated: scroll down f... There’s an open issue to migrate to one of the Noise key exchange patterns here: github.com/tendermint/tendermint A plan for switching to Secret Connection to the Noise handshake opened 09:06AM - 15 Feb 19 UTC closed 05:23PM - 15 Dec 19 UTC zmanian The Secret Connection handshake is broken. #3010 @jaekwon expressed a preference for having a fixed Secret Connection before switching to libp2p which... C:p2p Namely we are investigating one the newly described signature-based patterns: github.com noise_sig.pdf Specifically, the `XXsig` pattern appears to fit the key exchange performed by the current handshake. Aside from using a Noise AKE pattern, the existing protocol is close…

Excerpt (1197 of 1280 characters). Read the whole post on the forum ↗