The Author

Who I am

I’ve written pseudonymously — not out of secrecy, but because the guide should stand on its own merits. If the ideas are sound, they are sound regardless of who wrote them. If they are flawed, they should be challenged on those grounds. Part of my goal in publishing this guide is to collaborate with others to fill any gaps in my understanding.

This guide built first and foremost for me, and then I could not find a good reason to keep private.

I’m a software engineer with about 10 years of industry experience behind me. But I am not a security expert. And I think that is a good thing. I am the “technical person” in my circle.

My credentials that I think is sufficient for writing this guide

• My software engineering background means that I can read and understand the first-principals behind the technical details of cryptography and security tooling.
• I am very practical. I have zero tolerance for over engineered solutions. Good enough is good enough.
• I am curious and open minded. I take any and all feedback onboard.
• I have skin in the game. I’m running this protocol in my own life… and now I’ve published it for all to see. If it has flaws people will mock and exploit it. I vow to publish these incidents to this site and make the appropriate changes.