Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Remove symlink_secretive_ssh_public_keys
- Originally added based on maxgoedjen/secretive#117 - This was addressed in maxgoedjen/secretive#288 - Per the FAQ (https://github.com/maxgoedjen/secretive/blob/52cc08424ecb03552b0939ab03a68b941c249fa7/FAQ.md#how-do-i-tell-ssh-to-use-a-specific-key) “Beginning with Secretive 2.2, every secret has an automatically generated public key file representation on disk, and the path to it is listed under "Public Key Path" in Secretive. ” - There are 2 options - Add the Public Key path generated by Secretive (e.g. $HOME/Library/Containers/com.maxgoedjen.Secretive.SecretAgent/Data/PublicKeys/xxxxx.pub) to SSH config - Create a friendly name file in $HOME/.ssh/ (e.g. $HOME/.ssh/github.pub) and symlink that to the Public Key generated by Secretive - We can use ssh-add -l and -L to see which keys Secretive has added to ssh-agent. However this doesn’t give us the path to the public key files which live in `/Users/mikey/Library/Containers/com.maxgoedjen.Secretive.SecretAgent/Data/PublicKeys/`. - The public keys are named MD5-fingerprint.pub - I think, ideally, Secretive could give us a way to list the currently generated keys and the path to their public keys
- Loading branch information