rorycl / sshagentca Goto Github PK

I would like to understand the design rationale behind requiring each public key to be entered twice: one in raw form in authorized_keys, and once as a fingerprint hash in settings.yaml.

The code goes to lengths to ensure that every key in authorized_keys has a corresponding fingerprint in settings.yaml, and vice versa. So why not just put the public key in settings.yaml and remove the need for authorized_keys altogether? This would be much easier to administer.