Mailing-List: contact users-help@qpid.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@qpid.apache.org
Subject: Re: qpid-proton 0.12.2 python broker and SSL
To: users@qpid.apache.org
References: <1470674257224-7648886.post@n2.nabble.com>
From: Gordon Sim <gsim@redhat.com>
Organization: Red Hat UK Ltd, Registered in England and Wales under Company
 Registration No. 3798903, Directors: Michael Cunningham, Michael O'Neill,
 Eric Shander
Message-ID: <712e12bb-c77a-8151-d9f2-5add2666c9a6@redhat.com>
Date: Mon, 8 Aug 2016 21:54:22 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
 Thunderbird/45.1.1
MIME-Version: 1.0
In-Reply-To: <1470674257224-7648886.post@n2.nabble.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
archived-at: Mon, 08 Aug 2016 20:54:30 -0000

On 08/08/16 17:37, Tobias Duckworth wrote:
> Hi,
>
> Quick question:
>
> Is it straightforward to run a python broker that can accept amqps (SSL/TLS)
> connections in qpid-proton 0.12.2?
>
> I've tried with the broker.py example, but get the following client side
> error on trying to connect to it:
>
> connection open: error: gnutls_handshake() failed: A TLS packet with
> unexpected length was received. in amqp.openconnection(url)
>
> The specific error is probably coming from libcurl, which is handling the
> socket and SSL/TLS, but I think the implication is that the python example
> broker.py does not support secure connections out of the box?

You can specify amqp as the scheme for the --address options, e.g. 
--address amqps://0.0.0.0:5671

However to actually set up a certificate with which to authenticate 
itself to clients, the example would require some modification.

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