Mailing-List: contact users-help@qpid.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@qpid.apache.org
Received-SPF: pass (nike.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
MIME-Version: 1.0
In-Reply-To: 
 <CANs+FoVvXg9ED-+9ec8N+i+03-5LRRTGd8XPGB7jXTvbTiMYzQ@mail.gmail.com>
References: 
 <CANs+FoW5yQDDXDE6NjNT=CGa+OPZMv4-7UU2uZ9gZWHqeW17Lw@mail.gmail.com>
	<5267A111.2000900@redhat.com>
	<CANs+FoVbaZC-yiQYTF+RPku4piRDRcVHoX=u7eD5KD__kNPAtQ@mail.gmail.com>
	<5267D6C8.7090406@redhat.com>
	<CANs+FoWh2eNmrk7s1UJy8HLX0g+N1TdQg0Qy31j1ZAdAut7PxA@mail.gmail.com>
	<5267EF63.6010601@redhat.com>
	<CANs+FoVvXg9ED-+9ec8N+i+03-5LRRTGd8XPGB7jXTvbTiMYzQ@mail.gmail.com>
Date: Thu, 24 Oct 2013 00:38:04 +0200
Message-ID: 
 <CAOhBXQ4Ag0wPP=PWZbA44VBu28J=QQ0aLBHCqLJNtWFG7d8PSw@mail.gmail.com>
Subject: Re: QPid Ruby client and SSL
From: Jakub Scholz <jakub@scholz.cz>
To: users@qpid.apache.org
Content-Type: multipart/alternative; boundary=047d7b6dc1a89cfd9c04e9702b42

--047d7b6dc1a89cfd9c04e9702b42
Content-Type: text/plain; charset=ISO-8859-1

In the Java client, the SSL issues are very easy to analyse using the SSL
debugging mode which can be switched on using the system property
"javax.net.debug=ssl". It would be great to have something similar in the
C++ client (and in the scripting languages clients build on top of the C++
client). But to my understanding the C++ client is for the SSL negotiation
using the NSS library for which I never found such a nice debugging option.

Regards
Jakub


On Wed, Oct 23, 2013 at 6:15 PM, Trevor Vaughan <tvaughan@onyxpoint.com>wrote:

> No errors on the client side and adding trace to the QPID log didn't show
> anything except for dropped connections.
>
> That's when I started using openssl s_server to debug the SSL portion.
>
> We're using 0.14-22 currently.
>
>
> On Wed, Oct 23, 2013 at 11:46 AM, Gordon Sim <gsim@redhat.com> wrote:
>
> > On 10/23/2013 04:02 PM, Trevor Vaughan wrote:
> >
> >> amqp:ssl:myhost.mydomain:5671
> >> options << transport => 'ssl'
> >>
> >> But, no dice :-/
> >>
> >> Thanks for the help though!
> >>
> >
> > Do you get any errors on the client side? What if you export
> > QPID_LOG_ENABLE=trace+ before trying to run the ruby client, does that
> show
> > up anything unusual looking? (I'm wondering if the sslconnector.so module
> > is loaded, however if not then attempting to use ssl in the url should
> > result in an error not a hang).
> >
> > What version of the client are you using? (I ran a simple test from ruby
> > on trunk without a problem, so its either a different version or
> different
> > config in some way I think).
> >
> >
> > ------------------------------**------------------------------**---------
> > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.**org<
> users-unsubscribe@qpid.apache.org>
> > For additional commands, e-mail: users-help@qpid.apache.org
> >
> >
>
>
> --
> Trevor Vaughan
> Vice President, Onyx Point, Inc
> (410) 541-6699
> tvaughan@onyxpoint.com
>
> -- This account not approved for unencrypted proprietary information --
>

--047d7b6dc1a89cfd9c04e9702b42--