I was a researcher, I believed that we were independent, un-biased, the true source of knowledge (and I still do). What I didn’t appreciate at the time was that researchers were terrible in defining borders of their expertise and saying “I don’t know”.
We introduce an integration plugin for Let’s Encrypt. It provides integration for a variety of mechanisms that enable and simplify verification of domain control and certificate installation. We already tested it with Dehydrated (former letsencrypt.py) . It supports all existing verification methods: DNS, HTTP and TLS-SNI, in their current versions “01”.
We have extended the original research and can now use information from public keys (HTTPS, TLS, SSH, SSL) to audit cyber security management and compliance with internal standards.
The growth of Let’s Encrypt is phenomenal – 7 million certificates in last four months. The remaining hurdle for automation is verification of domain ownership. Well, actually it is NOT true. We were doing syntax testing – hoping to get the right kind of verification error … only to discover we have been successfully verified without providing any information.
The main reason we want to use cloud technologies is because they simplify cost management and allow us spend only as much as we need at any given time. The question is how secure it is and what risks are acceptable.
This post is about a research done by one of our co-founders. Petr showed that it is possible to find which tool or hardware device generated RSA keys from just a few public keys. I’m thinking it’s an attack, unexpected data leakage channel, but also an excellent source for audit-related analytics.
“Encryption is a key technology that underpins trustworthy computing. As digital technologies become ever more central to our lives, encryption becomes more important, and any weaknesses in its implementation become greater risks. Governments must commit to preserving the robustness of end- to-end encryption, and promoting its widespread use.”
A month ago, we decided to launch EnigmaLink – our file-sharing application on ProductHunt. Neither of us used ProductHunt before, but I found a friend who could do the submission. I thought it would be straightforward.
Dusan, one of us @EnigmaBridge was curious about how are default WiFi router passwords generated and very quickly came up with an algorithm producing right passwords. And this “bootstrapping” problem is much bigger …
I have mentioned EnigmaLink in my previous blog as our first application built on our cloud encryption platform (an easy to use alternative to CloudHSM from Amazon). Today, we posted it to the ProductHunt website.