News for hackers. Stuff that matters.
Re:BoringSSL by mehta on Tuesday October 20, 2015 @02:01PM (#10420714)
OpenSSL as you can guess is also open source. Having boringssl opensourced does not change anything.
Re:BoringSSL by icebraining on Tuesday October 20, 2015 @05:31PM (#10421953)
Google hadn't been using OpenSSL for most of their services; in fact, they discovered Heartbleed when studying the possible transition to OpenSSL from NSS; they ended up transitioning directly to BoringSSL.

This doesn't detract from your point, since NSS is also open source, it's just a factoid.

Re:BoringSSL by Thaxll on Tuesday October 20, 2015 @02:38PM (#10420917)
Who knows that google was using OpenSSL?
Re:BoringSSL by aruss on Tuesday October 20, 2015 @02:52PM (#10421007)
The security of a system should never rely on an attacker not knowing the details of the algorithm or implementation.

https://en.wikipedia.org/wiki/Security_through_obscurity

Re:BoringSSL by wolf550e on Wednesday October 21, 2015 @06:06AM (#10424515)
It is possible to fingerprint a TLS stack using its behaviour that a sysadmin can't change. People knew it was openssl.