Integration with Git
Keeper SSH Agent integration for Git Authentication and Commit Signing
Last updated
Was this helpful?
Keeper SSH Agent integration for Git Authentication and Commit Signing
Last updated
Was this helpful?
Keeper's SSH Agent integrates seamlessly with Git for authentication and commit signing, ensuring private keys are securely stored in the Keeper Vault instead of being saved locally on the device. This approach enhances security by protecting sensitive keys from local exposure.
In this guide, we'll create and configure separate authentication and signing keys for use with GitHub, all managed securely by Keeper. Using distinct keys for authentication and signing helps maintain a clear separation of roles, further strengthening your security posture.
Ensure that SSH Agent is active on the Keeper Desktop
Environment variables are set
To authenticate with GitHub using Keeper, follow the below steps.
This immediately will trigger a Keeper dialog to authorize the Github Authentication key.
Clicking "Authorize" will use the key stored in Keeper to authenticate with Github.
Your setup is complete.
To sign GitHub commits with Keeper, we will create a separate key that is specifically used for the signing process. Follow the steps below.
We will only delete the local private key, since it is now stored and managed by Keeper. The public key (xxx.pub) needs to stay, as it will be used for identifying which key to use for signing.
Let's also rename the public key to something more specific:
Place the username and the contents of the public key into a file called ~/.ssh/allowed_signers
. For example:
In this example, the file looks like this: