Tony,<br><br>A couple of things.<br><br>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.<br><br>Second, I've been sidetracked by an existing client and business development opportunities so I've been unable to work on this project.<br>
<br>More as I have time.<br><br>Thanks,<br><br>David<br><br><div><span class="gmail_quote">On 1/30/08, <b class="gmail_sendername">Tony Garnock-Jones</b> <<a href="mailto:tonyg@lshift.net">tonyg@lshift.net</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi David,<br><br>How did you get on with file transfers over AMQP? Did it work out, or<br>have you switched to something else?<br><br>David Pollak wrote:<br>> PS -- I'm currently implementing an encrypted session mechanism that<br>
> does a handshake with authentication and all the subsequent messages are<br>> encrypted using the secret shared during the handshake. It solves the<br>> "using Rabbit in the Wild" problem without SSL. I should have some code<br>
> posted in a few days.<br><br>This sounds very interesting! Are there any further details available?<br>Would support for this style of encryption be a useful addition to<br>RabbitMQ? Does it require cooperation from the broker, or is it a<br>
decentralised, peer-to-peer style thing? (with Bob Frankston-style<br>innovation-at-the-edge)<br><br>Tony<br>--<br> [][][] Tony Garnock-Jones | Mob: +44 (0)7905 974 211<br> [][] LShift Ltd | Tel: +44 (0)20 7729 7060<br>
[] [] <a href="http://www.lshift.net/">http://www.lshift.net/</a> | Email: <a href="mailto:tonyg@lshift.net">tonyg@lshift.net</a><br></blockquote></div><br><br clear="all"><br>-- <br>lift, the secure, simple, powerful web framework <a href="http://liftweb.net">http://liftweb.net</a><br>
Collaborative Task Management <a href="http://much4.us">http://much4.us</a>