![\"Debian\"](\"http:\/\/upload.wikimedia.org\/wikipedia\/en\/e\/e8\/Debian-logo.svg\"){kind=logo}
<\/p>\n<\/p>\n
Well, seeing as lately my blog is geeking-out over Ubuntu, I may as well add this posting to the list, and it’s a doozy.
\n<\/p>\n
If you happen to be a Linux Geek running Ubuntu<\/a>, Debian<\/a>, or any of the 40+ related distributions<\/a>, AND you’ve been hiding under a rock for the past 24 hours, then you should know that there’s a HUGE security vulnerability<\/strong><\/a> involving OpenSSL<\/a> and everything related to it, including SSH<\/a>. For the non-geekified: this is the stuff required for “secure” web sites to stay secure, and what people typically use to log into systems remotely without their passwords being freely scattered for any hacker to see and exploit.<\/p>\n The problem? The encryption keys used to keep your logins safe and private hinge around seemingly-random numbers<\/a> that the system must generate. However, sometime in September 2006, a developer got a bit careless and made a revision to the software that suddenly made the random number generator, well, not-so-random. The result? The encryption keys are theoretically easy to guess and decrypt, leaving those once-believed-private transactions very vulnerable and exposed. <\/p>\n Here are the security notices from Debian (here<\/a> and here<\/a>), and Ubuntu (here<\/a>, here<\/a> and here<\/a>), the two biggest Linux flavors affected by this security hole. The notices include fixes, and updates are available, but sysadmins need<\/strong> to follow the instructions to make the fix effective.<\/p>\n