News for hackers. Stuff that matters.
Re:Chrome: From NSS to OpenSSL by thirsteh on Thursday April 10, 2014 @02:59PM (#7568864)
The problem with OpenSSL is that it's really problematic to simply fix and refactor stuff given their FIPS certification.
Re:Chrome: From NSS to OpenSSL by leoc on Thursday April 10, 2014 @03:37PM (#7569137)
Ooh, OpenSSL's FIPS certification. The fellows who've been fighting for years to take it away http://www.itnews.com.au/News/65016,openssl-in-a-fips-flap.a... must be crowing right now. (Regardless of whether their own stuff is any better or no.) Another decertification incoming?
Re:Chrome: From NSS to OpenSSL by crashandburn4 on Friday April 11, 2014 @05:44AM (#7571990)
Hi, can someone help me understand what the significance of FIPS certification is? ( beyond the wikipedia page: http://en.wikipedia.org/wiki/FIPS_140-2 )
Re:Chrome: From NSS to OpenSSL by leoc on Friday April 11, 2014 @07:11AM (#7572207)
AFAIK the US federal government (excluding the military, which obviously has its own hoops to jump through) generally can't use your hardware/software unless it has the appropriate FIPS certification(s). https://en.wikipedia.org/wiki/Federal_Information_Processing...