You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Instantly share code, notes, and snippets.
Andrew Ayer
AGWA
Bootstrapped founder @SSLMate, where I make SSL certificates easier and do WebPKI and Certificate Transparency stuff.
WebPKI and Digital Signature related M&A + Investment + Public Offerings
This was inspired by Matt Suiche's great post on cyber security M&A related activity; there is some overlap but not much.
This is all public data.
I have also intentionally excluded sales of WebPKI key material, not only are these prices not public but they are usually very special cases that are in-essence impossible to compare effectively.
I have also included HSMs, Smart card, Digital signatures and CA related software companies in this list as it seems relevant.
On Twitter the other day,
I was lamenting the state of OCSP stapling support on Linux servers, and got
asked by several people to write-up what I think the requirements are for OCSP
stapling support.
Support for keeping a long-lived (disk) cache of OCSP responses.
This should be fairly simple. Any restarting of the service shouldn't
blow away previous responses that were obtained. This doesn't need to be
disk, just stable - and disk is an easy stable storage for most server
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Similar to my advice regarding OCSP Stapling
for servers/server developers, based on questions I've received about "CT best practices," I wanted to
write something similar for those writing server software. That is, this isn't targeted at server
operators, but for those writing software like Apache, nginx, Caddy, etc.
At the most basic level, the deployment of Certificate Transparency to date has largely tried to
focus the burden on CAs, rather than on server developers. If the CA is doing everything right,