CINXE.COM

<!DOCTYPE html> <html> <head> <meta http-equiv="Content-Type" content="text/html;charset=utf-8"> <meta name="robots" content="index,follow"> <title>OFTC - Home</title> <meta name="viewport" content="width=device-width, initial-scale=1.0"> <link href="/img/oftc-16.png" rel="shortcut icon" type="image/png" /> <link href="/css/bootstrap.min.css" rel="stylesheet" media="screen"> <link href="/css/main.css" rel="stylesheet"> <script src="/js/jquery.min.js"></script> <script src="/js/bootstrap.min.js"></script> <script src="/js/main.js"></script> </head> <body> <div class="navbar navbar-fixed-top"> <div class="navbar-inner"> <div class="container"> <form class="navbar-form pull-right" action="//webchat.oftc.net" method="get" target="_blank"> <input name="nick" type="text" data-toggle="tooltip" title="Enter your IRC nickname" class="span2" placeholder="Nickname"> <input name="channels" type="text" data-toggle="tooltip" title="Enter comma seperated list of channels to join" class="span2" placeholder="#oftc, #moocows"> <input type="hidden" name="uio" value="d4"> <button type="submit" class="btn">Chat!</button> </form> <button type="button" class="btn btn-navbar" data-toggle="collapse" data-target=".nav-collapse"> <span class="icon-bar"></span> <span class="icon-bar"></span> <span class="icon-bar"></span> </button> <a class="brand" href="/">OFTC</a> <div class="nav-collapse collapse"> <ul class="nav"> <li class="active"><a href="/">Home</a></li> <li><a href="/staff/">Staff</a></li> <li><a href="/documentation/">Documentation</a></li> <li><a href="/FAQ/">FAQ</a></li> </ul> </div> </div> </div> </div> <article> <div class="container"> <div class="row-fluid"> <div class="span12"> <h1 id="centerimg-srcimgoftc-80png-welcome-to-oftccenter"><center><img src="img/oftc-80.png" /> Welcome to OFTC!</center></h1> <p>The Open and Free Technology Community aims to provide stable and effective collaboration services to members of the community in any part of the world, while closely listening to their needs and desires.</p> <p>OFTC was founded at the end of 2001 by a group of experienced members of the Open Source and Free Software communities aiming to provide these communities with better communication, development, and support infrastructure.</p> <p>OFTC is a member project of <a href="http://www.spi-inc.org/">Software in the Public Interest</a>, a non-profit organization which was founded to help organizations develop and distribute open hardware and software.</p> <p>You can reach the OFTC IRC network by using a traditional <a href="https://en.wikipedia.org/wiki/Comparison_of_Internet_Relay_Chat_clients">IRC Client</a> of choice, or by the <a href="WebChat">WebChat</a> that we provide. The webchat enables you to connect to the network and chat directly from within your browser.</p> <p><strong>Connection Details:</strong></p> <ul> <li><a href="ircs://irc.oftc.net:6697"><strong>ircs://irc.oftc.net:6697</strong></a> for SSL (alternative port: 9999), IPv4 and IPv6.</li> <li><a href="irc://irc.oftc.net:6667"><strong>irc://irc.oftc.net:6667</strong></a> for non-SSL (alternative ports: 6668-6670, 7000), IPv4 and IPv6.</li> <li>SSL is supported on all of our servers. The server certificates are signed by the <a href="https://letsencrypt.org/"><strong>Let’s Encrypt</strong></a> certification authority. We also publish DNSSEC-signed <strong>TLSA records</strong> for irc.oftc.net:6697/tcp (see <code class="highlighter-rouge">dig _6697._tcp.irc.oftc.net tlsa</code>).</li> <li>See <a href="NickServ/CertFP/"><strong>CertFP</strong></a> for how to configure client certificate-based NickServ identification.</li> <li>If you need to force IPv4, connect to <a href="ircs://irc4.oftc.net:6697">ircs://irc4.oftc.net:6697</a>.</li> <li>We offer a <a href="WebChat"><strong>WebChat</strong></a> service (also via the boxes at the top of this page).</li> <li>Use of <a href="/Tor">Tor</a> is permitted to irc.oftc.net or our onion service on <a href="ircs://oftcnet6xg6roj6d7id4y4cu6dchysacqj2ldgea73qzdagufflqxrid.onion:6697">ircs://oftcnet6xg6roj6d7id4y4cu6dchysacqj2ldgea73qzdagufflqxrid.onion</a>.</li> </ul> <p>We offer IRC services (NickServ, ChanServ) for nick and channel registration.</p> <p>If you have support requests regarding the operation of the network please stop by <code class="highlighter-rouge">#oftc</code> or email <code class="highlighter-rouge">support@oftc.net</code>. We welcome issues and pull requests on our <a href="https://github.com/oftc">GitHub projects</a>, especially on the <a href="https://github.com/oftc/oftc">issue tracking repository</a>.</p> <div class="body"> <h1>News</h1> <h2>November 2024 </h2> <ul> <li><a href="/ElectionResults/2024">2024 staff election results</a> - thanks to Steve McIntyre (Sledge) and Pierre-Elliott Bécue (peb) for running the elections as counters this year.</li> </ul> <h2>March 2024 </h2> <ul> <li><a href="/ElectionResults/2023">2023 staff election results</a> - thanks to Steve McIntyre (Sledge), Alexander Færøy (ahf), and Pierre-Elliott Bécue (peb) for running the elections as counters this year.</li> </ul> <h2>October 2023 </h2> <ul> <li><a href="/ElectionResults/2022">2022 staff election results</a> - They’re a year late, but 2022 election results have been posted. Thanks to Steve McIntyre (Sledge), Alexander Færøy (ahf), and Pierre-Elliott Bécue (peb) for running the elections as counters this year.</li> </ul> <h2>October 2022 </h2> <ul> <li> <p>OFTC wants to upgrade the services in use to the Atheme variant. One user visible change will be the uniqueness of SSL cert fingerprints for accounts. If you are using SSL CertFP to identify to your accounts, please review the fingerprints associated with your account(s) and ensure that they are not duplicated between your accounts. This only applies if you have multiple separate accounts using the same fingerprint. Linked/grouped nicks are only a single account.</p> <p>We intend to remove any remaining duplicate fingerprint entries on 2022-11-22. The removal algorithm will delete duplicates from all but the most recently used account.</p> </li> </ul> <h2>January 2022 </h2> <ul> <li>We now offer a <a href="/Tor">Tor</a> hidden service: <a href="ircs://oftcnet6xg6roj6d7id4y4cu6dchysacqj2ldgea73qzdagufflqxrid.onion:6697">ircs://oftcnet6xg6roj6d7id4y4cu6dchysacqj2ldgea73qzdagufflqxrid.onion</a>.</li> </ul> <h2>November 2021 </h2> <ul> <li><a href="/ElectionResults/2021">2021 staff election results</a> - thanks to Steve McIntyre (Sledge) and Alexander Færøy (ahf) for running the elections as counters this year.</li> </ul> <h2>October 2021 </h2> <ul> <li>We’ve reconfigured our <a href="https://letsencrypt.org/2021/10/01/cert-chaining-help.html">Let’s Encrypt TLS certificates to not use the expired DST Root CA X3</a>, which should resolve issues with some clients and older TLS implementations. Note that if you’re using Android older than 7.1.1, you will no longer be able to connect without manually trusting the Let’s Encrypt CA.</li> </ul> <h2>September 2021 </h2> <ul> <li> <p>We have now deployed the <a href="https://github.com/oftc/oftc-webverify">new verification flow</a> that utilizes hCaptcha instead of Google ReCaptcha. Upon registration, the user receives a link which they can visit in their browser and solve a captcha. Upon successful completion, they will be marked as verified.</p> <p>Together with this, we have also made the system automatically mark the user as verified on the IRC side, making the old <code class="highlighter-rouge">checkverify</code> NickServ command no longer necessary.</p> <p>Should the user need a new link, as they expire after one hour, the new <code class="highlighter-rouge">reverify</code> NickServ command can come in handy.</p> </li> <li> <p>The primary purpose of the old ServicesWeb web application was to facilitate verification. With today’s changes, we have decided to discontinue it.</p> </li> </ul> <h2>June 2021 </h2> <ul> <li><a href="/AntiSpamBot">New Anti-Spam Bot</a> - We have deployed a new anti-spam bot. With your channel op’s permission, it joins your channel, blocks spam messages before the channel sees them, and K-lines the spamming host. Read <a href="/AntiSpamBot">this page</a> to see if our bot is a good fit for your channel.</li> </ul> <h2>May 2021 </h2> <ul> <li> <p><a href="/Privacy_Policy">Privacy Policy updates</a> - New accounts now have the flag <strong>PRIVATE</strong> turned on by default, all old accounts have this flag turned on forcefully <strong>ONCE</strong> as of now. This means that the mail address used for registration is no longer visible by default to other users, only <a href="/staff">IRCOps</a>.</p> <p>We have also updated our privacy policy to include more details on which data is visible to who (including other users).</p> </li> </ul> <h2>October 2020 </h2> <ul> <li><a href="/ElectionResults/2020">2020 staff election results</a> - thanks to Steve McIntyre (Sledge), Matt Trout (mst), and Alexander Færøy (ahf) for running the elections as counters this year.</li> </ul> <h2>November 2019 </h2> <ul> <li> <p><a href="/ElectionResults/2019">2019 staff election results</a> - thanks to Dan Christensen (opello) and Steve McIntyre (Sledge) for once again running the elections as counters this year.</p> <p>OFTC chair is now Tom Wesley (tomaw).</p> </li> </ul> <h2>March 2019 </h2> <ul> <li>We have updated our <a href="/Privacy_Policy/">Privacy Policy</a> to mention that we scan connecting hosts for known vulnerabilities and open proxies, and that we use the EFnet RBL. This was erroneously omitted previously.</li> </ul> <h2>November 2018 </h2> <ul> <li><a href="/ElectionResults/2018">2018 staff election results</a> - thanks to Alexander Færøy (ahf), Dan Christensen (opello), and Steve McIntyre (Sledge) for once again running the elections as counters this year.</li> </ul> <h2>June 2018 </h2> <ul> <li> <p>Late yesterday evening (Thursday 28 June 2018) OFTC staff became aware of successful unauthorized access to a number of OFTC user accounts. All evidence points to the unauthorized access being the result of a combination of weak account passwords and an attacker potentially using credential dumps from other online services.</p> <p>The impact appears to have been limited to channels under the control of the compromised user accounts. OFTC and its services have not been compromised.</p> <p>Known affected users have had their passwords reset and we will be working with those users to help them regain access. As soon as our review is complete, services will return to normal. If your account was not impacted, please ensure that you are using a <a href="https://xkcd.com/792/">strong, unique password</a> for your OFTC account.</p> </li> </ul> <ul> <li>We welcome new <a href="/staff">staff</a> member <em>Unit193</em> on board!</li> </ul> <h2>May 2018 </h2> <ul> <li>OFTC has a <a href="/Privacy_Policy/">Privacy Policy</a> now. Please review it for anything that you might not like. Feedback is welcome on #oftc and via support@oftc.net.</li> </ul> <h2>April 2018 </h2> <ul> <li>We welcome new <a href="/staff">staff</a> member <em>pastly</em> on board!</li> </ul> <ul> <li>On May 7th, irc6.oftc.net will no longer include A records. If you are using this DNS name to connect to OFTC from an IPv4-only host, you will want to update your client to use irc.oftc.net.</li> </ul> <h2>November 2017 </h2> <ul> <li>tjfontaine is stepping down from NOC and is now an OFTC advisor. rnowak is taking over the role as OFTC ombudsman.</li> </ul> <ul> <li><a href="/ElectionResults/2017">2017 staff election results</a> - thanks to Alexander Færøy (ahf), Dan Christensen (opello), and Steve McIntyre (Sledge) for running the elections as counters this year.</li> </ul> <h2>July 2017 </h2> <ul> <li>A new <a href="/UserModes">user mode</a> (+j) has been added which prevents private messages unless the sender is registered with services or whitelisted by the receiver. If a user has +Gj set, they can only receive messages from registered users who also share a channel. The functionality of +G has not been changed.</li> </ul> <h2>June 2017 </h2> <ul> <li>AS6453 is sponsoring a server in Montréal, Quebec, Canada. Thanks!</li> </ul> <h2>May 2017 </h2> <ul> <li>We welcome new <a href="/staff">staff</a> member <em>mcintosh</em> on board!</li> </ul> <h2>March 2017 </h2> <ul> <li> <p>As of 2017-03-26, NickServ will require <strong>nick verification via <a href="https://services.oftc.net/">services.oftc.net</a></strong> for the <em>+R</em> user mode. This affects channels using the <em>+M</em> and <em>+R</em> channel modes.</p> <p>In other words, make sure to verify your newly registered nickname using the web interface.</p> </li> </ul> <h2>January 2017 </h2> <ul> <li> <p>On January 8th, the EFnet RBL domain had expired, and the domain was subsequently taken over by a domain spam^Wparker. They went on to return <em>A</em> responses for all blacklist queries, which made our IRC services cloak all incoming connections as coming in over Tor. While investigating the cause of the problem, services were restarted, which suddenly made (almost) all existing connections to be cloaked as Tor connections as well, and as an unfortunate side effect, also akilled a 3-digit number of connections.</p> <p>We have disabled the use of EFnet RBL for now, and will work on putting sanity checks in place in services which should reject the non-RBL responses so this incident should not repeat itself. Sorry for the trouble.</p> <p>There are still users connected who are wrongly cloaked as being on Tor. Symptoms are being unable to join (or talk in) channels that have banned Tor users. To fix, reconnect, or “/msg nickserv set cloak on/off” to toggle the personalized cloaks which will override the Tor cloaks.</p> </li> </ul> <h2>December 2016 </h2> <ul> <li> <p>OFTC is using <a href="https://dronebl.org/"><strong>DroneBL</strong></a> (and EFnet RBL) to automatically block incoming IRC connections from hosts known to be compromised. Starting last week, DroneBL is now enforced in the firewalls. Previously affected connections were rejected on the IRC level with a “This host is infected” akill message; these connections will now receive a TCP RST.</p> <p>If you have trouble connecting, check DroneBL’s <a href="https://dronebl.org/lookup">IP lookup form</a>. Once the DroneBL listing is removed, you should be able to connect again. If you keep receiving an akill message, contact <a href="mailto:support@oftc.net">support@oftc.net</a> to get that removed as well.</p> </li> </ul> <h2>November 2016 </h2> <ul> <li>OFTC’s ircservices have a web interface at <a href="https://services.oftc.net/"><strong>services.oftc.net</strong></a>.</li> <li>New NickServ accounts now require verification through the services web interface to use the generic <a href="/UserCloaks">user cloaks</a>.</li> </ul> <h2>October 2016 </h2> <ul> <li><a href="/ElectionResults/2016">2016 staff election results</a></li> </ul> <h2>September 2016 </h2> <ul> <li>We have completed the upgrade to oftc-hybrid 1.7.</li> <li>OFTC now supports modern DHE and ECDHE cipher suites to offer <a href="https://en.wikipedia.org/wiki/Forward_secrecy">perfect forward secrecy</a> for SSL/TLS connections. Thanks to Alexander Færøy for the patches!</li> <li>NickServ’s AJOIN feature is now fully available again.</li> </ul> <ul> <li>We welcome new <a href="/staff">staff</a> member <em>dwfreed</em> on board!</li> <li>The minimum length of acceptable nicknames for registration in NickServ has been lowered to 2 characters. Previously the minimum length was 3 characters.</li> <li>In self-referential news, news items are now also available as <a href="https://www.oftc.net/feed.xml">Atom/RSS feed</a> .</li> </ul> <h2>July 2016 </h2> <ul> <li> <p>OFTC is now featuring full <strong>DNSSEC support</strong>. Both the <em>oftc.net</em> and <em>geo.oftc.net</em> zones are signed and verifiable from the DNS root. Additionally, TLSA (aka <a href="https://en.wikipedia.org/wiki/DNS-based_Authentication_of_Named_Entities">DANE</a>) records allow verification of the individual SSL certificate fingerprints of our IRC servers.</p> <p>On related news, our old <em>oftcdns</em> load-balancing for IRC servers based on Python Twisted has been replaced by a <a href="https://github.com/oftc/oftc-tools/tree/master/infrastructure/geodns">newer implemetation based on <em>bind9</em></a> and dynamic DNS updates.</p> </li> </ul> <ul> <li>Adding new <em>AJOIN</em> channels via NickServ is currently disabled. The current implementation allows to circumvent channel bans. AJOIN will be reenabled once this is fixed.</li> </ul> <h2>April 2016 </h2> <ul> <li> <p>We have completed the move to SSL certificates issued by the <a href="https://letsencrypt.org/">Let’s Encrypt</a> project. These certificates should remove the need for users to manually install any CA certificate files. Please drop by on #oftc or mail support@oftc.net if you have any troubles with the new certificates.</p> <p>OFTC would like to thank <a href="http://spi-inc.org/">Software in the Public Interest</a> for providing us with certificate services over the last years, when non-commercial SSL certificates were a scarce resource.</p> <p><em>Update 2016-04-19:</em> Users who have hard-coded paths to CA files in their client config will need to update or remove that config. Especially irssi users are hit by this problem. Removing ssl_cafile from ~/.irssi/config (but leaving ssl_verify in place) should fix it. (Note that /reconnect does not use the new config, use /reload /disconnect /connect instead.)</p> </li> </ul> <h2>March 2016 </h2> <ul> <li> <p>The CA used to sign our IRC server certificates, SPI, has been removed from Debian’s (and other’s) ca-certificates package. This means users will now be seeing “self-signed certificate in certificate chain” errors or experiencing similar problems with SSL connections.</p> <p>We are moving to <a href="https://letsencrypt.org/">Let’s Encrypt</a> certificates, but have yet to complete testing our processes.</p> <p>To work around the problem until we have new certificates, manually import the <a href="http://www.spi-inc.org/ca/spi-cacert.crt">spi-cacert.crt</a> certificate into your system’s or IRC client’s trust store.</p> </li> </ul> <h2>February 2016 </h2> <ul> <li>The OFTC website <a href="https://www.oftc.net/">www.oftc.net</a> finally supports SSL, a long-requested feature.</li> </ul> <h2>November 2015 </h2> <ul> <li>OFTC congratulates our founding member and advisor <a href="https://en.wikipedia.org/wiki/David_de_Burgh_Graham">cdlu</a> on winning a seat in the Canadian Parliament!</li> </ul> <ul> <li><a href="ElectionResults/2015">2015 staff election results</a></li> </ul> <h2>October 2014 </h2> <ul> <li><a href="ElectionResults/2014">2014 staff election results</a></li> </ul> <h2>May 2014 </h2> <ul> <li>OFTC has a <a href="https://github.com/oftc/oftc-tools/tree/master/logo">new logo</a>!</li> </ul> <h2>April 2014 </h2> <ul> <li>The OFTC IRC servers were not affected by the OpenSSL heartbleed bug.</li> </ul> <h2>October 2013 </h2> <ul> <li>The <a href="ElectionResults/2013">2013 staff election</a> is now over and counted.</li> </ul> <h2>March 2013 </h2> <ul> <li>A webchat has been lurking in the shadows for some time, and is now being announced to the world at large. Visit <a href="WebChat">WebChat</a> for more information.</li> </ul> <h2>November 2012 </h2> <ul> <li>On November 26th, <a href="/">OFTC</a> enabled automatic cloaking for those who wish to use it, please see <a href="/UserCloaks">UserCloaks</a> for more information and caveats.</li> <li>The <a href="/ElectionResults/2012">2012 staff election</a> is now over and counted. You can review the staff changes on the <a href="staff">Staff</a> page.</li> </ul> <h2>January 2012 </h2> <ul> <li>On January 18th, a bug in anti-spambot software we are using mistakenly kicked a large number of legitimate users from the network. The bug has been fixed, and we apologize for the inconvenience caused.</li> </ul> <h2>November 2011 </h2> <ul> <li>The <a href="/ElectionResults/2011">2011 staff election</a> is now over and counted. You can review the staff changes on the <a href="staff">Staff</a> page.</li> </ul> <h2>October 2010 </h2> <ul> <li>The <a href="/ElectionResults/2010">2010 staff election</a> is now over and counted. You can review the staff changes on the <a href="staff">Staff</a> page.</li> </ul> <h2>May 2010 </h2> <ul> <li>oftc-ircservices-1.4.0 has been released, this includes the much anticipated <a href="GroupServ">GroupServ</a> module to make it easy for groups to manage multiple channel access lists with centralized group management</li> </ul> <h2>April 2010 </h2> <ul> <li>We have two new staff members, welcome aboard mwalling and youam!</li> </ul> <h2>October 2009 </h2> <ul> <li>The 2009 staff election is now over and counted. You can review the staff changes on the <a href="staff">Staff</a> page.</li> </ul> <div><em><a href="feed.xml">Atom/RSS news feed</a></em></div> </div> </div> </div> </div>  </article> </body> </html>