You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Alan Conway (JIRA)" <ji...@apache.org> on 2017/10/20 16:21:00 UTC

[jira] [Created] (PROTON-1647) [go] support for crypto.tls connections

Alan Conway created PROTON-1647:
-----------------------------------

             Summary: [go] support for crypto.tls connections
                 Key: PROTON-1647
                 URL: https://issues.apache.org/jira/browse/PROTON-1647
             Project: Qpid Proton
          Issue Type: Bug
          Components: go-binding
    Affects Versions: proton-c-0.18.0
            Reporter: Alan Conway
            Assignee: Alan Conway


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 an example of using TLS (maybe wit SASL PLAIN auth?)




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org