[rabbitmq-discuss] File transfers
tonyg at lshift.net
Wed Jan 30 14:18:44 GMT 2008
Thanks for the update. Yes, SSL is a good quick solution. For 0-11, the
AMQP group will be looking at encryption and authentication, so I'd be
interested to discuss your ideas in that context when you have time.
David Pollak wrote:
> A couple of things.
> First, I've been thinking it's easier for me to use the HTTPS stuff in
> trunk head and stunnel4 than to reimplement SSL handshaking in Rabbit.
> Second, I've been sidetracked by an existing client and business
> development opportunities so I've been unable to work on this project.
> More as I have time.
> On 1/30/08, *Tony Garnock-Jones* <tonyg at lshift.net
> <mailto:tonyg at lshift.net>> wrote:
> Hi David,
> How did you get on with file transfers over AMQP? Did it work out, or
> have you switched to something else?
> David Pollak wrote:
> > PS -- I'm currently implementing an encrypted session mechanism that
> > does a handshake with authentication and all the subsequent
> messages are
> > encrypted using the secret shared during the handshake. It solves the
> > "using Rabbit in the Wild" problem without SSL. I should have
> some code
> > posted in a few days.
> This sounds very interesting! Are there any further details available?
> Would support for this style of encryption be a useful addition to
> RabbitMQ? Does it require cooperation from the broker, or is it a
> decentralised, peer-to-peer style thing? (with Bob Frankston-style
>  Tony Garnock-Jones | Mob: +44 (0)7905 974 211
>  LShift Ltd | Tel: +44 (0)20 7729 7060
>   http://www.lshift.net/ | Email: tonyg at lshift.net
> <mailto:tonyg at lshift.net>
> lift, the secure, simple, powerful web framework http://liftweb.net
> Collaborative Task Management http://much4.us
 Tony Garnock-Jones | Mob: +44 (0)7905 974 211
 LShift Ltd | Tel: +44 (0)20 7729 7060
  http://www.lshift.net/ | Email: tonyg at lshift.net
More information about the rabbitmq-discuss