From supercomputers to IoT – processors (or chips) are everywhere. Computer chips protecting our privacy and security would first travel the world to get designed, fabricated, and personalized. Even if we had an unbreakable encryption algorithm, it may be defeated by its manufacturing. Let’s exploit superpowers and their influence to create a practical unbreakable encryption.
We decided for OpenVPN to build secure connections to our Private Spaces. We braced for difficulties, but that was only the beginning. The point of this post is that integration testing does make a difference. And that OpenVPN is a very nice tool!
The Gateway is our first Private Space – like a VPN (if you know it), but for sharing and co-operation. We have been building Private Spaces for the last three months – a one-click secure cloud space for companies, teams, or home users.
I have come across Troy Hunt’s article yesterday about getting an EV certificate. His initial assumption is that EV certificate actually proves something, unlike many other seals of “security”. But is it really worth spending $80+/year?
I love cryptography. It’s an abstract science, where I can define a problem, come up with a solution and prove it (eventually). I also like applying cryptography as it involves real world (users, limitations of computers, …), which messes everything up and turns pure mathematics into a fun game. Continue reading Transaction Security with Slow Clock and Counter – How to Conjure Up Entropy→
Many companies drive their computer systems without wearing seatbelts, even though they know and constantly witness they risk being injured by cyber crashes. There are simple economic reasons for this. It is not the unavailability of cyber “seat belts”, but the difficulty of putting them in. Enigma Bridge technology gives customers self-driving cyber-security for safe navigation through the cyberspace and protection of its payload.
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.