[PROTON-1647] [go] support for crypto.tls connections

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: proton-c-0.18.0
• Fix Version/s: proton-c-future
• Component/s: go-binding
• Labels: tls
• Assignee: Alan Conway
• Reporter: Alan Conway
• Created: 20/Oct/17 16:20
• Updated: 01/Nov/21 10:19

Description

The electron and proton Go bindings do not expose proton's built-in SSL layer because Go provides it's own TLS layer in the crypto.tls package which is more portable, capable and familiar to Go programmers.

You can already use a tls.Conn with proton or electron, but there are several points that should be cleaned up:

• when a TLS connection is in use set allow-insecure-mechs in proton-C automatically
• make sure the AMQP virtual-host matches the TLS virtual-host by default
• provide access to the net.Conn used by an electron.Connection, which in turn will give access to TLS details if the user needs them
• provide an example of using TLS (maybe with SASL PLAIN auth?)