A bug in the Debian-modified version of OpenSSL (also used by Ubuntu) means that cryptographic keys generated on Debian systems for the last couple of years may be insecure. Instead of being well randomized, they are easily guessable.<\/p>\n
More information about the vulnerability is here<\/a>; how to fix it here<\/a>.<\/p>\n How much does this matter? The full scope has not emerged yet; but as I understand it, it affects self-generated keys. This means that a large number of supposedly secure SSH connections or SSL connections to web sites and servers over the last couple of years were actually not very secure at all.<\/p>\n If nothing else, it shows how easy it is to be falsely reassured, to think you are secure when you are not.<\/p>\n It also shows the risks of modifying security code. The problem is not with OpenSSL, but with changes made by a Debian coder who thought he was fixing something when in fact he was breaking it.<\/p>\n This site runs on Debian and I’ve spent some time today checking it for vulnerability and regenerating keys.<\/p>\n A bug in the Debian-modified version of OpenSSL (also used by Ubuntu) means that cryptographic keys generated on Debian systems for the last couple of years may be insecure. Instead of being well randomized, they are easily guessable. More information about the vulnerability is here; how to fix it here. How much does this matter? … Continue reading Painful Debian \/ Ubuntu SSL bug<\/span> Those who purchased certificates from a third-party certificate authority are not affected, unless one of those authorities turns out to have been using the broken version which is unlikely.<\/strike> Even if you purchased certificates from a third-party certificate authority, you would still be affected if you generated the certificate request on a system with the broken OpenSSL library (thanks to Nico for the correction below).<\/p>\n