add explicit public key naming for IdentitiesOnly usage #55
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add optional section of guide in case user has
IdentitiesOnly yes
turned on inssh
client configurations (common if other privacy/security-focused ssh guides were followed), since keys loaded ingpg-agent
will then not auto-enumerate.In such a case, it is not necessarily obvious that
ssh -i [identity_file]
orIdentityFile
configurations can be pointed at a saved copy of the public key instead (since there should be no access to the private key).