<br><br><div class="gmail_quote">On Wed, Jan 25, 2012 at 4:00 AM, <span dir="ltr"><<a href="mailto:rabbitmq-discuss-request@lists.rabbitmq.com">rabbitmq-discuss-request@lists.rabbitmq.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div id=":4cn"><br>
It would be a nice feature, but pretty low priority TBH.<br></div></blockquote><div><br></div><div>You should be able to do this already, out of the box, presuming that the Erlang SSL library supports it.</div><div> </div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":4cn">
Set up a compressed SSH tunnel? Or if the overhead of encryption is too<br>
great, hook up netcat and gzip in front of Rabbit?<br></div></blockquote><div><br></div><div>Instead of using SSH, you could use the built-in SSL functionality. If SSLv2 is disabled and both the client and server are compiled against zlib, then OpenSSL should negociate compression, and if you select a cipher with no encryption or authentication, you can avoid the crypto overhead.</div>
<div><br></div><div>Don't know enough about the Erlang ssl library to know how you'd go about specifying what cipher it should use.</div><div><br></div><div>Elias</div></div>