Debian also has the not undeserved reputation of being difficult for those new to Linux to install and manage.
The Debian maintainers apparently created the vulnerability by deleting code that seeded the random number generation used to calculate encryption keys.
The result was that the random number generator used in Debian's OpenSSL package was predictable, leading to cryptographic keys that might guessable.
Debian Security Advisory DSA-1571-1 states: "Affected keys include SSH keys, OpenVPN keys, DNSSEC keys, and key material for use in X.509 certificates and session keys used in SSL/TLS connections. Keys generated with GnuPG or GNUTLS are not affected, though."
The advisory also publishes the URLs for a detector of weak encryption keys, as well as the location of instructions about how to implement key rollover.
The vulnerability only exists in Debian and Debian derived Linux systems, but those also include the Ubuntu versions of Linux that have lately become quite popular among casual desktop Linux users.
The problematic OpenSSL code appeared in the Debian unstable distribution on September 17, 2006 and has since been propagated into the current stable and testing distributions named Etch. The previous stable Debian distribution named Sarge is not affected.
Many Debian Linux desktop users shouldn't be affected by this Secure Sockets Layer (SSL) bug unless they've generated cryptographic keys for Secure Shell (SSH) access between systems or digital signing or authentication certificates.
However, techies who administrate Debian based Linux systems that traffic in certificates might be scurrying about somewhat in coming days as they apt-get the upgraded OpenSSL package and regenerate and roll over cryptographic keys and certificates.