The first secure, decentralized, human-meaningful naming system.
https://forum.namecoin.org/
Namecoin uses crypto++.Explained Garzik:
“The gnuTLS bug is pretty bad, but very few use gnuTLS in the bitcoin community. OpenSSL is standard.”
Garzik indicated that the use of OpenSSL mitigates a fork risk that is present when using other competing libraries for key software, such as gnuTLS.
He also stated that projects using OpenSSL, Mozilla NSS, Crypto++ or another crypto library are not impacted by the bug.
Yeah.khal wrote:From http://www.coindesk.com/serious-linux-f ... sdropping/ :Namecoin uses crypto++.Explained Garzik:
“The gnuTLS bug is pretty bad, but very few use gnuTLS in the bitcoin community. OpenSSL is standard.”
Garzik indicated that the use of OpenSSL mitigates a fork risk that is present when using other competing libraries for key software, such as gnuTLS.
He also stated that projects using OpenSSL, Mozilla NSS, Crypto++ or another crypto library are not impacted by the bug.
Convergence/FreeSpeechMe uses firefox' libs (NSS).
Other than that, we are affected the same way with server daemons using gnuTLS (apache, php, etc).
=> Namecoin servers have been updated.
Ankur Nandwani, a developer at Bitmonet, suggested hosted wallet users and the users of bitcoin exchanges would be most affected, but stated that there are easy protections to prevent issues.
“In both cases, an attacker can sniff users credentials, when users are trying to log-in to their account. To reduce the probability of online wallets and exchange credentials from being compromised, it is really important that everyone use two-factor authentication.”
Nandwani said that the bug is evidence that bitcoin users should reduce their reliance on online wallets and exchanges.