|
|
| Subject |
Re: TLS + Jabber
|
| Posted |
3/22/2002; 9:48 PM by Brian Andresen
|
| Last Modified |
3/22/2002; 9:48 PM by Brian Andresen
|
| In Response To |
TLS + Jabber (#9)
|
| Label |
None.
|
Read |
652
|
|
|
|
|
Hi Jeremy,
>I'd be interested in adding the ability to connect to Jabber servers
>securely to my Jabber stuff, but I'd need the ability to read from and
>write to raw sockets. Is that possible with TLS? (I don't know much about
>it.)
The technology definitely makes that possible. The transport-layer part
of the TLS name comes from its integration at the TCP level; essentially
any activity on a TCP socket could be redirected to a "TLS socket,"
meaning a TLS wrapper around a TCP socket. Of course the connection on
the other side needs to be using the same protocol.
However, this level of functionality is not presently exported to
UserTalk. If and when it is, it will have an interface analogous to that
of the tcp.* kernel verbs. Since I'm pretty sure that's what you're
using, you don't need worry about TLS compatibility in your design. You
might want to add some security-specific functions -- client
authentication, or verifying some of the details of the server's
certificate. We don't have an interface for those functions yet, but the
functionality is already in the DLL.
I hope this is answering your question. If not, try me again...
-Brian
|
|
|
None.
|
|
Yes, I expected it would be that easy to use, and I've designed for it; only
|
|
|
|
|