World Library  
Flag as Inappropriate
Email this Article

Rsa Bsafe

Article Id: WHEBN0041479526
Reproduction Date:

Title: Rsa Bsafe  
Author: World Heritage Encyclopedia
Language: English
Subject: Cryptographic software, LibreSSL, Dual EC DRBG, BREACH (security exploit), Botan (programming library)
Collection: Cryptographic Software, Transport Layer Security Implementation
Publisher: World Heritage Encyclopedia

Rsa Bsafe

RSA BSAFE is a FIPS 140-2 validated cryptography library offered by RSA Security. From 2004 to 2013 the default random number generator in the library contained an alleged backdoor from the American National Security Agency (NSA), as part of its secret Bullrun program.[1]


  • SSL-C 1
  • Dual_EC_DRBG backdoor 2
  • References 3
  • External links 4


The SSL-C library is an SSL toolkit in the BSAFE suite. It was originally written by Eric A. Young and Tim J. Hudson, as a fork of the open library SSLeay, that they developed prior to joining RSA.[2][3] Like SSLeay, SSL-C supported SSLv2, SSLv3, TLSv1; while it also supports X.509v1 and X.509v3.[4] SSL-C was first released in 1999.[5] The algorithm was one of several available in the libraries that users were able to choose from.[6]

Dual_EC_DRBG backdoor

From 2004 to 2013, the default cryptographically secure pseudorandom number generator (CSPRNG) in BSAFE was Dual_EC_DRBG, which contained an alleged backdoor from NSA, in addition to being a biased and slow CSPRNG.[7] The cryptographic community had been aware that Dual_EC_DRBG was a very poor CSPRNG since shortly after the specification was posted in 2005, and by 2007 it had become apparent that the CSPRNG seemed to be designed to contain a hidden backdoor for NSA, usable only by NSA via a secret key.[8] In 2007, Bruce Schneier described the backdoor as "too obvious to trick anyone to use it."[8] The backdoor was confirmed in the Snowden leaks in 2013, and it was insinuated that NSA had paid RSA Security US$10 million to use Dual_EC_DRBG by default in 2004,[1] though RSA Security denied that they knew about the backdoor in 2004. The Reuters article which revealed the secret $10 million contract to use Dual_EC_DRBG described the deal as "handled by business leaders rather than pure technologists".[1] RSA Security has largely declined to explain their choice to continue using Dual_EC_DRBG even after the defects and potential backdoor were discovered in 2006 and 2007, and has denied knowingly inserting the backdoor.[9]

So why would RSA pick Dual_EC as the default? You got me. Not only is Dual_EC hilariously slow – which has real performance implications – it was shown to be a just plain bad random number generator all the way back in 2006. By 2007, when Shumow and Ferguson raised the possibility of a backdoor in the specification, no sensible cryptographer would go near the thing. And the killer is that RSA employs a number of highly distinguished cryptographers! It's unlikely that they'd all miss the news about Dual_EC.
— Matthew Green, cryptographer and research professor at Johns Hopkins University, A Few Thoughts on Cryptographic Engineering[7] (From after the backdoor was confirmed, but before the $10 million secret deal was revealed by Reuters.)

As a cryptographically secure random number generator is often the basis of cryptography, much data encrypted with BSAFE was not secure against NSA. Specifically it has been shown that the backdoor makes SSL/TLS completely breakable by the party having the private key to the backdoor (i.e. NSA).[8] Since the US government and US companies have also used the vulnerable BSAFE, NSA can potentially have made US data less safe, if NSA's secret key to the backdoor had been stolen. It is also possible to derive the secret key by solving a single instance of the algorithm's elliptic curve problem[8] (breaking an instance of elliptic curve cryptography is considered unlikely with current computers and algorithms, but a breakthrough may occur).


  1. ^ a b c
  2. ^
  3. ^
  4. ^
  5. ^
  6. ^
  7. ^ a b
  8. ^ a b c d
  9. ^

External links

  • RSA BSAFE - RSA Security
This article was sourced from Creative Commons Attribution-ShareAlike License; additional terms may apply. World Heritage Encyclopedia content is assembled from numerous content providers, Open Access Publishing, and in compliance with The Fair Access to Science and Technology Research Act (FASTR), Wikimedia Foundation, Inc., Public Library of Science, The Encyclopedia of Life, Open Book Publishers (OBP), PubMed, U.S. National Library of Medicine, National Center for Biotechnology Information, U.S. National Library of Medicine, National Institutes of Health (NIH), U.S. Department of Health & Human Services, and, which sources content from all federal, state, local, tribal, and territorial government publication portals (.gov, .mil, .edu). Funding for and content contributors is made possible from the U.S. Congress, E-Government Act of 2002.
Crowd sourced content that is contributed to World Heritage Encyclopedia is peer reviewed and edited by our editorial staff to ensure quality scholarly research articles.
By using this site, you agree to the Terms of Use and Privacy Policy. World Heritage Encyclopedia™ is a registered trademark of the World Public Library Association, a non-profit organization.

Copyright © World Library Foundation. All rights reserved. eBooks from Project Gutenberg are sponsored by the World Library Foundation,
a 501c(4) Member's Support Non-Profit Organization, and is NOT affiliated with any governmental agency or department.