Skip to content

Commit 4a608a2

Browse files
Update Commit Signing with SSH in Gitkraken Client
Updates Commit Signing with SSH in Gitkraken Client through the Git Executable feature. The preferences have been updated to include the option to select SSH as the GPG format for signing.
1 parent e3bdeef commit 4a608a2

File tree

2 files changed

+23
-10
lines changed

2 files changed

+23
-10
lines changed

_images/gkc-gpg-ssh-preferences.png

266 KB
Loading

gitkraken-client/commit-signing-with-gpg.md

Lines changed: 23 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -144,7 +144,10 @@ There will be several prompts to make sure that you *really* want to delete your
144144

145145
###Commit Signing with SSH
146146

147-
SSH signature verification is available in Gitkraken 9.6.0 as Experimental feature
147+
Commit Signing with SSH is available in Gitkraken Client through Git Executable feature.
148+
149+
<img src="/wp-content/uploads/gkc-gpg-ssh-preferences.png" class="img-bordered img-responsive center">
150+
148151

149152
####Requirements
150153

@@ -161,25 +164,35 @@ Open a Terminal and run this command:
161164

162165
<img src="/wp-content/uploads/gkc-ssh-keygen.png" srcset="/wp-content/uploads/[email protected] 2x" class="img-bordered img-responsive center">
163166

164-
####Configure git to sign commits with SSH
165167

166-
Run this command to use SSH for signing commits and pointing to the key previously created:
167-
`git config --global gpg.format sshgit config --global user.signingkey /PATH/TO/.SSH/KEY.PUB`
168+
####Enable Git Executable feature
168169

169-
####Create allowed_signers file
170+
Go to <kbd>Preferences > Experimental > Git Executable</kbd> and enable it.
171+
172+
<img src="/wp-content/uploads/gkc-git-executable.png" srcset="/wp-content/uploads/[email protected] 2x" class="img-bordered img-responsive center">
173+
174+
####Select SSH as your GPG format for signing
175+
176+
At <kbd>Preferences > GPG > GPG Format</kbd>, select <kbd>SSH</kbd>.
170177

178+
Automatically Gitkraken client will change your preferences in `.gitconfig` and populate GPG SSH Program with ssh-keygen
179+
180+
####Select the signing key
181+
182+
On <kbd>Signing key</kbd>, click on <kbd>Browse</kbd> and select the `.pub` key file previously generated.
183+
184+
####Create allowed_signers file
171185
This file is needed to verify the key used to sign the commits is valid and known by git
186+
187+
On your terminal, run:
172188
```
173189
touch ~/.ssh/allowed_signers
174-
git config gpg.ssh.allowedSignersFile ~/.ssh/allowed_signers
175-
echo "$(git config --get user.email) namespaces=\"git\" $(cat ~/.ssh/<MY_KEY>.pub)" >> ~/.ssh/allowed_signers
176190
```
191+
And select the file in Gitkraken client.
177192

178193
####Enable Commit Signing by Default in Gitkraken:
179194

180-
Preferences > GPG > Sign Commits/Tags By defaultPreferences > Experimental > Use Git Executable and select a git executable 2.34 or later
181-
182-
<img src="/wp-content/uploads/gkc-git-executable.png" srcset="/wp-content/uploads/[email protected] 2x" class="img-bordered img-responsive center">
195+
Preferences > GPG > Sign Commits/Tags By default
183196

184197
####Add the SSH key to your remote hosting
185198

0 commit comments

Comments
 (0)