3 ms·
Too much fluff, too less technical information :/ Also, do they contribute their improvements to OpenSSL back or at least have a public repository where others
by moepstar 14y ago
Too much fluff, too less technical information :/
Also, do they contribute their improvements to OpenSSL back or at least have a public repository where others could take a look?
- batterseapower 14y agoI think it was pretty interesting, first time I've heard of OCSP stapling. Apparently the AES-NI stuff is actually already part of the public OpenSSL codebase: http://datacenteroverlords.com/2011/09/07/aes-ni-pimp-your-aes/ http://datacenteroverlords.com/2011/09/07/aes-ni-pimp-your-a...
- swordswinger12 14y agoIf they want anyone to use their software they should. Any crypto or security person worth a damn will be extremely skeptical of their changes until he or she verifies they don't affect the security of the implementation. Lots of people have ideas on how to 'speed up' crypto, and most of them are total junk.