Hi, my name is Marcus, and I’m writing you about how technology influences your life, work, business, or our society. And something about Open Source and Open Culture. If you like to get in touch with me, just write me an email or leave a comment.
Let‘s Encrypt wants to bring free encryption to your website. Founded as a project by the Linux Foundation and supported by major companies like Automattic, Facebook, Akamai or Mozilla, it has established a complete CA infrastructure for automated certificate issuing. The root certificate has been cross signed by IdentiTrust, so it works already in most major browsers.
As I followed the Processing.js tutorial using Chrome, I ran into unsuspected troubles: Chrome blocks local files from beeing loaded to improve your security. You could run chrome via command line, allowing this explicitly, using chrome.exe --allow-file-access-from-files.
But there’s another way which is clearer and more similar to a production environment: Use a static webserver to serve your files to localhost.
We all share the same problems with passwords: They should not only be secure, but also easy to remember. However, most passwords are either insecure (like Pa$$word oder letmein) or hard to remember (like sk3Oh$d!). For a secure password only the the number of possible combinations matters. What in most cases does not matter is how long a password is. And that’s where the system suggested by Randall Munroe starts: Instead of getting most combinations out of a few characters, he uses some more letters (in his example, four words) one can easily remember (if only because the combination is so weired) to achieve a large number of combinations: