[JDEV] s2s SSL

[David Waite]

I assume you trust both server operators not to look at the sensitive 
data, and that you can ensure that the other client is only connecfting 
to the remote server via ssl. I'm also assuming all of these servers 
have trusted certificates (at least to the local clients and between 
servers). Is it acceptable to only have s2s connections allowed to and 
from machines that run a ssl-enabled s2s component? If you allow a mixed 
environment, you may find that users cannot tell if their conversations 
with another user are encrypted or not - either the connection between 
servers or the connection from the other server to the remote client 
could be unprotected, and the local user would not know.

This kinda ruins the point of having data encrypted at all - who cares 
if the conversation _could_ be safe :-) Thats why most of the proposals 
for encryption in Jabber are endpoint-to-endpoint encryption - the two 
endpoints do not have a dependancy on the support of an encryption 
standard on the servers between them.

-David Waite

Bray, Dan wrote:

>
>I'm building a specialized Jabber client to enable various entities to
>exchange data. The data needs to remain private.  I can encrypt the payload
>but there is also a desire to keep the routing secret so I need to transport
>over an SSL socket.  I've got this working fine on the client side but am
>now concerned about deliveries that need to go ourside my server.  I need
>server to server SSL.  
>
>I'd like to work on this and would appreciate some help narrowing down the
>code I need to look at. Whre do I start to look?  mio? dialback?  At what
>level are the s2s connections managed?
>
>Thanks
>
>Dan Bray
>
>
>_______________________________________________
>jdev mailing list
>jdev at jabber.org
>http://mailman.jabber.org/listinfo/jdev
>