Uploaded image for project: 'Qpid Proton'
  1. Qpid Proton
  2. PROTON-1647

[go] support for crypto.tls connections

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: proton-c-0.18.0
    • Fix Version/s: None
    • Component/s: go-binding
    • Labels:

      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?)

        Attachments

          Activity

            People

            • Assignee:
              aconway Alan Conway
              Reporter:
              aconway Alan Conway
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: