Difference between revisions of "Secure Communications Week"

Jump to navigation Jump to search
Line 10: Line 10:

* [http://www.adiumx.com/ Adium] 1.2.7
* [http://www.adiumx.com/ Adium] 1.2.7
* [http://code.google.com/p/exodus/ Exodus] 0.10
* Gaim is now [http://www.pidgin.im/ Pidgin] -- time to upgrade!
* Gaim is now [http://www.pidgin.im/ Pidgin] -- time to upgrade!
* [http://www.gajim.org/] 0.12
* [http://www.gajim.org/] 0.12

Revision as of 21:36, 14 August 2008

Security matters! But it doesn't happen unless we make it happen. Some large Jabber services on the Internet are working to require encrypted communications in time for the 10th anniversary of Jabber technologies on January 4, 1999. In preparation, we're planning to hold a Secure Communications Week, October 4 - October 11, 2008. Read on for details.

Which Services are Participating?

  • jabber.org

How Can End Users Prepare?

Upgrade your client to the most recent version. In general, the most recent versions of all major Jabber clients support encryption. That includes:

How Can Services Prepare?

Simply require SSL or TLS connections for client-to-server connections and install a digital security certificate. You can obtain a FREE domain certificate from the XMPP Intermediate Certificate Authority.

How Can Client Developers Prepare?

Build support for TLS (SSL) and SASL into your client as defined in RFC 3920 and rfc3920bis. Support for certificates issued by the XMPP Intermediate Certificate Authority is also very helpful, because many Jabber services on the Internet use the free certificates issued by the XMPP ICA.