<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/" xml:lang="en-US">
  <title>jabber.org</title>
  <link rel="alternate" type="text/html" href="http://www.jabber.org/notices.html"/>
  <author>
    <name>jabber.org</name>
    <url>http://www.jabber.org/</url>
  </author>
  <tagline>jabber.org notices</tagline>
  <id>http://www.jabber.org/notices</id>
  <copyright>http://creativecommons.org/publicdomain/zero/1.0/</copyright>
  <modified>2013-03-05</modified>
  <entry>
    <title>Corrected Security Certificate</title>
    <link type="text/html" rel="alternate" href="http://www.jabber.org/notices.html"/>
    <id>tag:jabber.org,9</id>
    <issued>2012-03-05</issued>
    <modified>2012-03-05</modified>
    <summary>The security certificate that we installed in December used a SHA-256 fingerprint, which theoretically is more secure but which some existing software can't handle yet. Therefore we have installed a corrected certificate using a SHA-1 fingerprint. If you've been receiving a certificate warning for the last few months, you shouldn't receive those anymore.</summary>
  </entry>
  <entry>
    <title>Non-ASCII Characters Disallowed in New Accounts</title>
    <link type="text/html" rel="alternate" href="http://www.jabber.org/notices.html"/>
    <id>tag:jabber.org,8</id>
    <issued>2012-01-15</issued>
    <modified>2012-01-15</modified>
    <summary>In response to several recent instances of abuse, we have disallowed non-ASCII characters in new accounts registered at the jabber.org IM service. This policy does not apply to existing accounts.</summary>
  </entry>
  <entry>
    <title>Registration Re-Opened</title>
    <link type="text/html" rel="alternate" href="http://www.jabber.org/notices.html"/>
    <id>tag:jabber.org,7</id>
    <issued>2012-10-09</issued>
    <modified>2012-10-09</modified>
    <summary>We have re-opened account registration at https://register.jabber.org/</summary>
  </entry>
  <entry>
    <title>Updated Service Policy</title>
    <link type="text/html" rel="alternate" href="http://www.jabber.org/notices.html"/>
    <id>tag:jabber.org,6</id>
    <issued>2012-09-25</issued>
    <modified>2012-09-25</modified>
    <summary>Version 1.1 of the jabber.org service policy is now in effect.</summary>
  </entry>
  <entry>
    <title>Disabled Accounts</title>
    <link type="text/html" rel="alternate" href="http://www.jabber.org/notices.html"/>
    <id>tag:jabber.org,5</id>
    <issued>2012-08-22</issued>
    <modified>2012-08-22</modified>
    <summary>Recently the jabber.org IM service has been the victim of massive and repeated denial of service attacks. The admin team strongly suspects that these attacks are related to the widespread and abusive use of jabber.org accounts by "customers" of KBot, a program for cheating at the DarkOrbit game. Even if the DoS attacks prove to be unrelated to KBot, the admin team has decided that use of jabber.org to communicate with KBot violates the jabber.org service policy. Although we are in the process of updating the service policy to more clearly define how this kind of usage is abusive, the dire nature of the current threat has forced us to take more immediate action. Therefore, we are disabling the accounts of every jabber.org user who communicates with KBot, and we have disabled new account registration to prevent further communication between jabber.org users and KBot. We do not take this step lightly, but given the current circumstances we have no other choice.</summary>
  </entry>
  <entry>
    <title>Account Registration Disabled</title>
    <link type="text/html" rel="alternate" href="http://www.jabber.org/notices.html"/>
    <id>tag:jabber.org,4</id>
    <issued>2012-08-22</issued>
    <modified>2012-08-22</modified>
    <summary>As part of our defensive measures against repeated DoS attacks, we have disabled new account registration until further notice.</summary>
  </entry>
  <entry>
    <title>Another Denial of Service</title>
    <link type="text/html" rel="alternate" href="http://www.jabber.org/notices.html"/>
    <id>tag:jabber.org,3</id>
    <issued>2012-08-21</issued>
    <modified>2012-08-21</modified>
    <summary>The previous DDoS attack has started again. As before, fallback measures are in place, but if your IM client doesn't handle DNS SRV records correctly then you might not be able to connect.</summary>
  </entry>
  <entry>
    <title>Proposed Changes to the Service Policy</title>
    <link type="text/html" rel="alternate" href="http://www.jabber.org/notices.html"/>
    <id>tag:jabber.org,2</id>
    <issued>2012-08-20</issued>
    <modified>2012-08-20</modified>
    <summary>We have posted proposed changes to the policy that governs use of the jabber.org IM service. Details, links, and instructions for providing feedback can be found in our post to the juser@jabber.org email list, see http://mail.jabber.org/pipermail/juser/2012-August/006869.html.</summary>
  </entry>
  <entry>
    <title>Service Restored</title>
    <link type="text/html" rel="alternate" href="http://www.jabber.org/notices.html"/>
    <id>tag:jabber.org,1</id>
    <issued>2012-08-15</issued>
    <modified>2012-08-15</modified>
    <summary>We were able to completely restore service today. However, it is quite possible that the denial of service attack could be launched again at any time. If you were unable to connect during the outage, we recommend that you consider using a different IM client or reporting a bug to the developers of the IM client you use, since standard DNS fallback and XMPP reconnection methods should have been sufficient to keep you online after the first few hours of the attack.</summary>
  </entry>
  <entry>
    <title>Denial of Service</title>
    <link type="text/html" rel="alternate" href="http://www.jabber.org/notices.html"/>
    <id>tag:jabber.org,0</id>
    <issued>2012-08-12</issued>
    <modified>2012-08-12</modified>
    <summary>Today we have experienced a distributed denial of service attack against the jabber.org IM service. Although the web server and email server are running fine, we have been forced to take the IM service offline until your (volunteer!) admin team has time to determine appropriate countermeasures. UPDATE 2012-08-12: We've made some DNS fixes and some clients are now able to connect.</summary>
  </entry>
</feed>
