qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Justin Ross (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (PROTON-1647) [go] support for crypto.tls connections
Date Wed, 02 May 2018 22:27:00 GMT

     [ https://issues.apache.org/jira/browse/PROTON-1647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Justin Ross updated PROTON-1647:
    Labels: tls  (was: )

> [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
>            Priority: Major
>              Labels: tls
> 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?)

This message was sent by Atlassian JIRA

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

View raw message