Changes

Jump to navigation Jump to search
no edit summary
Line 38: Line 38:  
* [[sslonly_jabberd2 | Jabberd2]]
 
* [[sslonly_jabberd2 | Jabberd2]]
 
* [[sslonly_jabberd14 | Jabberd14]]
 
* [[sslonly_jabberd14 | Jabberd14]]
 +
* [[sslonly_openfire | Openfire]]
 
* [[sslonly_tigase | Tigase]]
 
* [[sslonly_tigase | Tigase]]
* [[sslonly_openfire | Openfire]]
      
== How Can Client Developers Prepare? ==
 
== How Can Client Developers Prepare? ==
   −
Build support for TLS (SSL) and SASL into your client as defined in [http://www.xmpp.org/rfcs/rfc3920.html RFC 3920] and [http://www.xmpp.org/internet-drafts/draft-saintandre-rfc3920bis-06.html rfc3920bis]. Support for certificates issued by the [https://www.xmpp.net/ XMPP Intermediate Certificate Authority] is also very helpful, because many Jabber services on the Internet use the free certificates issued by the XMPP ICA.
+
Build support for TLS (SSL) and SASL into your client as defined in [http://www.xmpp.org/rfcs/rfc3920.html RFC 3920] and [http://www.xmpp.org/internet-drafts/draft-saintandre-rfc3920bis-06.html rfc3920bis]. Support for certificates issued by the [http://xmpp.org/ca/ XMPP Intermediate Certificate Authority] is also very helpful, because many Jabber services on the Internet use the free certificates issued by the XMPP ICA.
10

edits

Navigation menu