[standards-jig] s2s

Thomas Muldowney temas at box5.net
Tue Nov 5 19:47:51 UTC 2002


Easy to request, not easy to implement.  Because s2s can have many hops
before a msg is delivered, you can't guarantee that a msg won't suddenly
run into an unencrypted hop.  Now, like I've said before, in a
controlled environemnt (such as internal corporate IM servers) it could
potentially be beneficial to enable SSL or some such for s2s.  This
should be fairly easy to hack in right now.  Really though, you're
better to encrypt from end point to end point (note, endpoint, not
user), so that the middle doesn't even have to worry about it.

--temas


On Mon, Nov 04, 2002 at 11:29:32AM +0200, Adrian Rapa wrote:
> hi (again)
> i think that a good ideea is to provide a method to encrypt the s2s
> comunication too.
> 
> Adrian
> 
> _______________________________________________
> Standards-JIG mailing list
> Standards-JIG at jabber.org
> http://mailman.jabber.org/listinfo/standards-jig
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.jabber.org/pipermail/standards/attachments/20021105/f6d905c0/attachment.sig>


More information about the Standards mailing list