Return-Path: Delivered-To: apmail-geronimo-activemq-users-archive@www.apache.org Received: (qmail 52354 invoked from network); 18 Oct 2006 22:44:11 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 18 Oct 2006 22:44:11 -0000 Received: (qmail 40508 invoked by uid 500); 18 Oct 2006 22:44:07 -0000 Delivered-To: apmail-geronimo-activemq-users-archive@geronimo.apache.org Received: (qmail 40492 invoked by uid 500); 18 Oct 2006 22:44:07 -0000 Mailing-List: contact activemq-users-help@geronimo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: activemq-users@geronimo.apache.org Delivered-To: mailing list activemq-users@geronimo.apache.org Received: (qmail 40478 invoked by uid 99); 18 Oct 2006 22:44:06 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Oct 2006 15:44:06 -0700 X-ASF-Spam-Status: No, hits=2.5 required=10.0 tests=DNS_FROM_RFC_ABUSE,HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of chirino@gmail.com designates 66.249.92.174 as permitted sender) Received: from [66.249.92.174] (HELO ug-out-1314.google.com) (66.249.92.174) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Oct 2006 15:44:04 -0700 Received: by ug-out-1314.google.com with SMTP id 29so361962ugc for ; Wed, 18 Oct 2006 15:43:43 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth; b=lFoAZ1BktPVAJh5/AnC+ED8komG3GCmkUFqGfXQzXmrVxd/3N41slY2oWQp2MDnvM2UzOcdtJ/QR3GeBsR9ERPl+rke9c5pjUvZrt0NKCeUWu8yzXsC50LblanBOXY1Pp+1p0ZM7TTqJ0ck1qJ5L8j0NgmceJ0J0syrR3XKNmzk= Received: by 10.78.185.16 with SMTP id i16mr10796003huf; Wed, 18 Oct 2006 15:43:42 -0700 (PDT) Received: by 10.78.142.5 with HTTP; Wed, 18 Oct 2006 15:43:42 -0700 (PDT) Message-ID: Date: Wed, 18 Oct 2006 17:43:42 -0500 From: "Hiram Chirino" Sender: chirino@gmail.com To: activemq-users@geronimo.apache.org Subject: Re: Stomp over SSL In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_76503_25095020.1161211422933" References: <6875720.post@talk.nabble.com> X-Google-Sender-Auth: cd2720c594559985 X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N ------=_Part_76503_25095020.1161211422933 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline I think I'd actually prefer a protocol id that looks something like this: stomp+ssl:// On 10/18/06, James Strachan wrote: > > On 10/18/06, oferhalevi wrote: > > > > Hi, > > > > Does anybody have any ideas on how to add transport level security to > the > > Stomp connector? > > Is it down to configuration, or is this feature simply not available > (yet)? > > Its more a case of we've never tried yet. From the Java server side of > the fence it should be fairly simple to provide a stompssl transport > which reuses the ssl transport but uses the stomp wire format. > > I wonder if there's a stomp client we can experiment with on the SSL > side of things? Maybe the ruby client? > > -- > > James > ------- > http://radio.weblogs.com/0112098/ > -- Regards, Hiram Blog: http://hiramchirino.com ------=_Part_76503_25095020.1161211422933--