Return-Path: X-Original-To: apmail-qpid-users-archive@www.apache.org Delivered-To: apmail-qpid-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B947DC35A for ; Wed, 16 May 2012 07:48:31 +0000 (UTC) Received: (qmail 69240 invoked by uid 500); 16 May 2012 07:48:31 -0000 Delivered-To: apmail-qpid-users-archive@qpid.apache.org Received: (qmail 69049 invoked by uid 500); 16 May 2012 07:48:28 -0000 Mailing-List: contact users-help@qpid.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@qpid.apache.org Delivered-To: mailing list users@qpid.apache.org Received: (qmail 69012 invoked by uid 99); 16 May 2012 07:48:27 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 May 2012 07:48:27 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [209.85.213.42] (HELO mail-yw0-f42.google.com) (209.85.213.42) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 May 2012 07:48:19 +0000 Received: by yhfq11 with SMTP id q11so481984yhf.15 for ; Wed, 16 May 2012 00:47:58 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:content-type:content-transfer-encoding :x-gm-message-state; bh=9dwC02VnFaC9Qg75WK+rMJh2kT5MrXoBBw6fEJZYazI=; b=Qoed/OY83G33SZimE5njUV8k0NT6H/v4tWKRjl+SchshOlbvcxSpIa0LcQj57ROHIP xR57/mkqgsVL3vg4SUxvnpnsaR1hoJgzoW/ruuVeCMzrpJ3pRoo2XK3R8iql/SkPUfq0 +l7jrHsd0obtKI2Otmob4svdsLqDpZ2eS1y11c6UUaeZD0ynDD9ekhFSk3FbaaAMbBLD mGw1Lpx4P7hd4jaFsyXY2m7tzGdTxaQiut0nYVZGQPS5RyhiZb12pecaavCYkr2hyrH7 CuPYD0VqwPn1hWL7FaDM0xPtIYJbHc875uEx9ffmC1fzKDs5bK2IVbCIzs24jIFvc5OQ aZUQ== MIME-Version: 1.0 Received: by 10.100.76.9 with SMTP id y9mr652697ana.59.1337154478751; Wed, 16 May 2012 00:47:58 -0700 (PDT) Received: by 10.236.75.5 with HTTP; Wed, 16 May 2012 00:47:58 -0700 (PDT) X-Originating-IP: [193.29.76.37] In-Reply-To: References: Date: Wed, 16 May 2012 09:47:58 +0200 Message-ID: Subject: Re: How to set ssl_keyfile / ssl_certfile for python tools from the command line? From: Jakub Scholz To: users@qpid.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Gm-Message-State: ALoCoQkC09HZwPf19/rgavkVqco/7U8I+BHVtcDRELx5ffi6oD+msWS0P0sBcUIoLghNpblK6s7j Hi Paul, I think right now there is just a first step - support for SSL EXTERNAL in the Python library. But someone needs to take it to the next level and include the appropriate support into the tools like qpid-config, qpid-tool etc. Regards Jakub On Wed, May 16, 2012 at 1:14 AM, Paul Colby wrote: > Hi guys, > > It's great to see python SSL support has been (mostly?) fixed up in 0.16!= :) > > Now, I've got qpid-config successfully using SSL to talk to my brokers li= ke: > > qpid-config -b amqps://localhost > > However, if I set ssl-require-client-authentication on the brokers, to > enable the EXTERNAL mechanism, then I also need to tell qpid-config which > client certificates to use... how do I do that? =A0I see that the python = code > maintains ssl_keyfile and ssl_certfile options internally, but how do I s= et > those from the command line? > > Thanks again! :) > > pc > ---- > http://colby.id.au --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org For additional commands, e-mail: users-help@qpid.apache.org