From dev-return-19297-apmail-activemq-dev-archive=activemq.apache.org@activemq.apache.org Mon Mar 08 13:54:03 2010 Return-Path: Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: (qmail 48726 invoked from network); 8 Mar 2010 13:54:03 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 8 Mar 2010 13:54:03 -0000 Received: (qmail 1044 invoked by uid 500); 8 Mar 2010 13:53:39 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 992 invoked by uid 500); 8 Mar 2010 13:53:39 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 983 invoked by uid 99); 8 Mar 2010 13:53:39 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Mar 2010 13:53:39 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,SPF_HELO_PASS,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Mar 2010 13:53:37 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1NodOX-000436-Fp for dev@activemq.apache.org; Mon, 08 Mar 2010 05:53:17 -0800 Message-ID: <27819963.post@talk.nabble.com> Date: Mon, 8 Mar 2010 05:53:17 -0800 (PST) From: Garfield071 To: dev@activemq.apache.org Subject: Re: Stomp message and integrity In-Reply-To: <36e91d9d1003080322w28b0b2ccua18bdb806b0fdc1f@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: denis.sicard@videotron.ca References: <27797837.post@talk.nabble.com> <36e91d9d1003080322w28b0b2ccua18bdb806b0fdc1f@mail.gmail.com> Hello Dejan, Thank you for your answer. This is what I will do. Dejan Bosanac wrote: > > Hi, > > there is no such mechanism in Stomp protocol, but you can always do that > in > your application (sign message body, send CRC in a header or something > similar) > > Cheers > -- > Dejan Bosanac - http://twitter.com/dejanb > > Open Source Integration - http://fusesource.com/ > ActiveMQ in Action - http://www.manning.com/snyder/ > Blog - http://www.nighttale.net > > > On Fri, Mar 5, 2010 at 7:56 PM, Garfield071 > wrote: > >> >> Hi, >> >> I am using the Stomp c client with Amq. I would like to know how I can >> make >> sure that message has not been altered in the transport. Is there a way >> to >> add a signature of something like that to ensure integrity ? >> -- >> View this message in context: >> http://old.nabble.com/Stomp-message-and-integrity-tp27797837p27797837.html >> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com. >> >> > > > ----- > Dejan Bosanac > > Open Source Integration - http://fusesource.com/ > ActiveMQ in Action - http://www.manning.com/snyder/ > Blog - http://www.nighttale.net > -- View this message in context: http://old.nabble.com/Stomp-message-and-integrity-tp27797837p27819963.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.