Subscribe: news
Added By: Feedage Forager Feedage Grade B rated
Language: English
account  authenticator  code  factor auth  factor  google authenticator  google  icculus org  icculus  ipv  org  password  shell account 
Rate this Feed
Rate this feedRate this feedRate this feedRate this feedRate this feed
Rate this feed 1 starRate this feed 2 starRate this feed 3 starRate this feed 4 starRate this feed 5 star

Comments (0)

Feed Details and Statistics Feed Statistics
Preview: news news

news from the open source incubator

Published: Tue, 12 Dec 2017 01:17:04 -0500


IPv6 support!

Fri, 30 Oct 2015 03:42:19 -0400

If your connection has IPv6 support, you are likely talking to over the new protocol instead of old, crusty IPv4.

If you aren't sure, one can always force the issue with ... if the page loads at all, congrats, you've got IPv6.

We're still migrating bits and pieces of the system over, so please let me know if something is broken.

Two-factor auth

Wed, 17 Sep 2014 11:30:24 -0400

(image) now supports two-factor authentication via Google Authenticator. Both ssh logins and webmail can be protected by this extra layer of security.

The system is opt-in. By default, nothing changes for you, but we encourage you to enable two-factor auth wherever you are able. To set it up:

  1. Install Google Authenticator on your trusted device (namely: your smart phone). You can get it for lots of platforms (and the source code if you get desperate). The Wikipedia page has links to all that and more technical details, too.
  2. ssh to your account, and run "google-authenticator". It will ask you something about time-based authentication tokens. Say "y" here. It will spit out a big ASCII QR code on your terminal. Scan this on your phone with the Google Authenticator app. There are a few more questions from google-authenticator, answer them however you feel is reasonable.
  3. That's all.

Now when you ssh to your shell account, you will be prompted for your password _and_ the current code from your Google Authenticator app, which changes every 30 seconds. Please note that if you have a valid private key configured, you will not be prompted for either a password or two-factor code, so that route will continue to work as expected, for automated logins, etc.

Webmail can also be protected:

  1. Login to your account.
  2. Click the settings button in the top right, where you'll see a "2steps Google verification"
  3. Click the "Activate" checkbox.
  4. Either fill in your secret key from the ssh account, or make a new one and get your QR code.
  5. Optionally fill in recovery keys (or use the same ones from your shell account).
  6. Click "save"
  7. Fill in your current code from your phone and click "Check code" to make sure it's working.
  8. That's all.

Next time you log into webmail with a valid password, you'll also be prompted for the current code from your smart phone before you can log in. Please note that IMAP and SMTP are not protected by 2-factor auth at this time, nor do we offer "app-specific passwords" at the moment.

Also, a gentle reminder: two-factor auth is powerful stuff, but you should also use strong, unique passwords everywhere. Using a password manager like 1Password or KeePass or LastPass (etc!) is important in modern times.

Heartbleed status

Tue, 15 Apr 2014 13:34:22 -0400

(image) uses OpenSSL, and was vulnerable to the Heartbleed exploit since we migrated to Ubuntu 12.10 on January 20th, 2013.

In the past few days, we have patched the security hole, revoked our existing SSL certificate, and installed a new certificate.

We don't have reason to believe Heartbleed was ever exploited on our servers, but the problem with Heartbleed is that there's never any indication that it was, either. If you have a shell account on, or any personal/sensitive data on any service of, like revision control or Bugzilla, you should consider changing your password.

If you have any problems or questions, or see anything that looks suspicious, please email Ryan ASAP.


PhysicsFS 2.0.3 released!

Tue, 23 Oct 2012 00:21:41 -0400

The details are here.

iodoom3 and GtkRadiant

Sun, 27 Nov 2011 19:47:16 -0500

This has been a very idTech week around here.

First up: GtkRadiant has moved to! You can find its Subversion repository here, and the mailing list here.

You can pull from the Subversion repository with the svn:// protocol:

svn co svn:// GtkRadiant

We're still restoring some bits of functionality, such as the Trac website from the old server. This will be up and running soon.

Also this week: Doom 3 (aka "idTech 4") is now licensed under the GPL3. To match our work on Quake 3, which we affectionately refer to as "ioquake3", we've now set up iodoom3. You can see the start of our efforts over at

Thanks to everyone at id Software for their continued support of Free Software. We all look forward to a great holiday season, full of hacking on idTech!