SSH Signing

Comments: 13

• 09 Sep, '22
  Mattia

  This would be really helpful. Our org requires commit signing, and creating GPG key is way complex than creating SSH keys. Also because some password manager, like 1Password, now allow an easy SSH sign configuration.

• 09 Sep, '22
  Mike Valstar

  I too would like to see this as it's now supported by 1password as well

• 23 Sep, '22
  ShadowLoop

  I bought myself a license for GitKraken Pro over 4 or 5 years ago for use personally and for work (work wouldn't get me a license), and have been using GPG signing the entire time. My company has made the decision to force all employers to use SSH signing and as such is a deal breaker for me, as GitKraken changes repo config for GPG every time you switch profiles etc.
  
  It would be great to be able to have a new option under GPG settings to ask what format to use (defaulted as gpg but allows ssh as a option), then ssh is selected the other options are still relevant (there is still a signing key needed, whether to sign commits and tags).
  
  Don't mean to "solutionise", as a software engineer I can't help it when looking at something to imaging what is needed under the hood! 🤣
  At the very least, perhaps a option in gitgraken to disable gpg altogether and leave it to what is configured in the git repo config and globally; does mean it wouldn't change per profile though.

• 05 Nov, '22
  Ilkka

  1Password makes this amazingly easy to set up and it's been working brilliantly for me with CLI git, magit, lazygit etc. Would love to see this supported -- hopefully in a way that just leverages my existing `~/.gitconfig` settings for it.

• 16 Nov, '22
  Kyle

  GitHub Enterprise Server just launched with support for SSH Key commit signing, would be great to be able to use this in our org.
  GPG is a bit of a pain point due to support on Windows being a bit lackluster and annoying to setup.

• 28 Dec, '22
  Dan

  GitLab also added support for SSH key commit signing https://docs.gitlab.com/ee/user/project/repository/ssh_signed_commits/

• 23 Jan
  Dirk Bester

  If you cannot sign my commits using my Github signing key then using GitKraken is a nonstarter.

• 23 Jan
  Adam

  Bump as request for this feature. Just started using 1password and would greatly prefer to not deal with GPG keys anymore and use SSH key signing instead.

• 27 Jan
  Sam

  Is this seriously still not implemented? After switching my whole workflow over to SSH key signing, GitKraken is the only tool that doesn't support it. So guess what tool will be tossed aside until they can get with the times.

• 27 Jan
  Sam

  Ooof, it's even worse. Every time I try to open a repo, it overwrites my SSH signing key in ~/.gitconfig . Now GK is really unusable.

• 08 Feb
  Dave

  Same here
  I've been a long time user of gitkraken - since version 2, but now I've had to shift my workflow over to "other" tooling due to the fact that they are so far behind on this one.
  
  While the client has gotten slightly bloated over the years with features such as timeline (which was retired) - rather than adding new things like WSLg support - how about we get this one done first then work on other things?
  
  Most git hosts are moving this way. Github and Gitlab both have it now and they are prob the biggest (outside of Azure DevOps / TFS) providers.
  
  It's a real shame as I do love the client - it has the nicest interface to work with compared with "other" tooling that hides things behind extra clicks or menus for no apparent reason.

• 21 Feb
  Stefan

  +1 from me too on this issue, would really love to see this in an upcoming update.

• 13 Mar
  Dana Mison

  This has become a problem for me at work too.