From your blog: If you have a passphrase encrypted key, you can see this for yourself: $ eval `ssh-agent` # make sure an empty agent is running $ ssh us

From your blog: If you have a passphrase encrypted key, you can see this for yourself: $ eval `ssh-agent` # make sure an empty agent is running $ ssh user@server # enter passphrase on first login $ ssh user@server # passphrase no longer needed This is wrong. Keys not added explicitly with `ssh-add` to ssh-agent will not be available unless you explicitly enabled AddKeysToAgent in ssh_config. [0] Forgetting something like enabled config options is nothing uncommon for a user, but it doesn't exactly speak well for a company making an ssh-agent alternative as a product. Also I tend to agree with the poster adjacent to me which emphasized the inadequate threat model analysis in your blog post, including entirely ignoring or failing to address critical points. [0] https://www.freebsd.org/cgi/man.cgi?query=ssh_config&sektion=5 https://www.freebsd.org/cgi/man.cgi?query=ssh_config&sektion...