Support for S/MIME
Currently only gpg signed commits are supported, but S/MIME is an alternative to this.
Using `gpgsm` and git cli, it is straightforward to sign commits, i.e. simply call `git commit -S`, but gitkraken does not handle it correctly. It appears to not parse the password request correctly.
As for other basic interfaces:
- Toggle between S/MIME and gpg: set git config option `gpg.format=x509`
- Assign S/MIME key: Assign as git config `user.signingkey=0xFFFFFFFF` and can check availability via `gpgsm --list-secret-keys 0xFFFFFFFF`
- [Optional] Import pk12 private keys into gpgsm:
- Calls `gpgsm --import`
- Add root certificate's fingerprint to `~/.gnupg/trustlist.txt`
- Verify that certificates are trusted: `gpgsm --list-secret-keys --with-validation 0xFFFFFFFF`
- [Optional] Display basic info about certificate chain, especially expiration date.
Comments: 3
-
06 Jul, '22
LecrisI should add that currently gitkraken is unusable if you setup a S/MIME signing. Rebasing, cherry-picking, most common operations for which you would use gitkraken over cli require the git signing password, and because the UI is broken, all of these have to be done via cli.
-
10 Nov, '22
Justin OThis is now a requirement at our company, and will prevent us from renewing our enterprise license in the future.
-
22 Jun
LycaKnightIs it possible in any way?
I tried with the Experimental Feature (Git Executable).
Hoping that Gitkraken will take over the global Git settings, but unfortunately that doesn't work either.