<div dir="ltr">Emile,<div><br></div><div>Thank you for your response.</div><div><br></div><div style>Simon,</div><div style><br></div><div style>You are correct - I was primarily interested in securing the "channel" from the producer / consumer to the exchange / queue. Any guidance with that in mind?</div>
<div style><br></div><div style>Regards,</div><div style><br></div><div style>Richard</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jan 16, 2013 at 2:29 AM, Simon MacMullen <span dir="ltr"><<a href="mailto:simon@rabbitmq.com" target="_blank">simon@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 class="im">On 16/01/13 10:24, Emile Joubert wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 15/01/13 23:29, Richard Raseley wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Could anyone provide any guidance on what they use for securing traffic<br>
over the WAN? Is the built in SSL / TLS support in RabbitMQ (as outlined<br>
here <a href="http://www.rabbitmq.com/ssl.html" target="_blank">http://www.rabbitmq.com/ssl.<u></u>html</a>) sufficient for such purposes?<br>
Should I be concerned about the additional overhead in processing<br>
requirements for an estimated 10 million+ messages per day?<br>
</blockquote>
<br>
I assume you want to secure the link between federated exchanges or a<br>
shovel connection, because clustering over a WAN link is not<br>
recommended. SSL will provide confidentiality and if you use certificate<br>
verification then it can provide authentication. SSL also provides<br>
integrity by hashing data.<br>
</blockquote>
<br></div>
I assume the OP was talking about securing standard client -> server connections.<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
If you care about performance then select an appropriate cipher (e.g.<br>
avoid 3DES). If you have crypto hardware support then make sure that is<br>
enabled.<br>
</blockquote>
<br></div>
10m messages per day is only 115 msg/s. Presumably there will be spikes, but at that sort of rate, SSL performance is unlikely to be an issue.<br>
<br>
Cheers, Simon<span class="HOEnZb"><font color="#888888"><br>
<br>
-- <br>
Simon MacMullen<br>
RabbitMQ, VMware<br>
</font></span></blockquote></div><br></div>