Finding the Ultimate Password Manager

In this blog post, I wrote down my considerations & requirements around finding my next password manager. I’ve been a LastPass Family user for several years, but I am going to switch to a new password manager. In 2015, LastPass was sold to LogMeIn. It didn’t feel good, but it wasn’t a deal breaker for me. Recent security issues issues like this one or this one made me freak out a bit. Last but not least, the parent company of LastPass – LogMeIn – sold itself to private equity firms. That was it – I needed a new password manager and while I’m on this journey to find a new password manager, I’m sharing it with the rest of the world. I hope this blog post will help you in finding your ultimate password manager.

Continue reading “Finding the Ultimate Password Manager”

*driver* did not meet the Store signing level requirements – Windows 10 Code Integrity

This error message is related to Device Guard Code Integrity in Windows 10 and shows up in the Event Viewer under the Code Integrity folder. As of writing this article, the error message is not described in online documentation of Microsoft.

Continue reading “*driver* did not meet the Store signing level requirements – Windows 10 Code Integrity”

Let’s Encrypt leaks 3.125 email addresses

First of all, I absolutely love Let’s Encrypt. It’s a very easy way to protect a website. All websites are protected with an SSL certificate from Let’s Encrypt as well. I received an e-mail this morning from Let’s Encrypt about their new Subscriber Agreement. Above the message, there is a big list with 3.125 e-mail addresses including my own e-mail address. Looks like they forgot to put those email addresses in the BCC of the email. The e-mail was sent from the Let’s Encrypt mailservers because the SPF record is valid: Authentication-Results: spf=pass (sender IP is;

Dear Let’s Encrypt Subscriber,

We’re writing to let you know that we are updating the Let’s Encrypt Subscriber Agreement, effective June 30, 2016. You can find the updated agreement (v1.1) as well as the current agreement (v1.0.1) in the “Let’s Encrypt Subscriber Agreement” section of the following page:

Thank you for helping to secure the Web by using Let’s Encrypt.

We’re talking about a Certificate Authority here! Hopefully they’ll protect the SSL certificates in a better way.

UPDATE: Official statement from Let’s Encrypt.