This data is aggregated from our automated service monitoring system as well as the outage and maintenance notices posted below.
Recent versions of OpenSSL were found to be affected by an information disclosure vulnerability related to TLS heartbeats, nicknamed Heartbleed. It allows attackers to read up to 64kb of random server memory, possibly including passwords, session IDs or even private keys.
Gentoo users should consult the related GLSA for more information on how to address the issue on their machines.
After the public disclosure on April 7, we have confirmed that several services provided by Gentoo Infrastructure were vulnerable as well. We have immediately updated the affected software, recreated private keys, reissued certificates, and invalidated all running user sessions. Despite these measures, we cannot exclude the possibility of attackers exploiting the issue during the time it was not publicly known to gain access to credentials or session IDs of our users. There are currently no indications this has happened.
However, to be safe, we are asking you to reset your passwords used for Gentoo services within the next 7 days.
You need to take action if you have an account on one or more of these sites:
Log in using your current credentials and use the reset password functionality:
You need to change your LDAP password (used for
perl_ldap and the SMTP/IMAP/POP services).
To do that, log in to dev.gentoo.org via ssh and invoke
If you don't update your credentials until April 19, 23:59 UTC, we will be removing your current password to avoid abuse.
For our web services, you will then need to request a reset via email. We can not recover your account in case your email address on file is not current.
For LDAP accounts, developers will need to be in possession of their SSH or GPG keys and contact infra for a normal password reset.
Contact firstname.lastname@example.org for assistance or further information.
Users using a Bugzilla password that uses character beyond the ASCII character range are currently unable to log in to the site.
This was caused by a recent Software update. We are coordinating with the upstream Bugzilla developers on how to resolve this issue.
For the time being, please reset your password to a string containing only ASCII characters if you cannot log in.