Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign updocument how to set up splitgpg for git #1964
Comments
mfc
added
help wanted
C: doc
labels
May 5, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
May 5, 2016
Member
Besides standard gpg setup in git (setting keyid, automatic signing etc), the only thing required to enable usage of split gpg is:
git config --global gpg.program /usr/bin/qubes-gpg-client-wrapper
And of course set gpg backend domain name in /rw/config/gpg-split-domain, but that's a standard step in split gpg configuration in general.
|
Besides standard gpg setup in git (setting keyid, automatic signing etc), the only thing required to enable usage of split gpg is:
And of course set gpg backend domain name in |
mfc
added this to the
Documentation/website milestone
May 6, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
adrelanos
May 6, 2016
Member
Not sure this will require #474. I am using split gpg, but failed setting up split gpg a while ago for git. Don't remember anymore exactly why. A new try just now revealed, that my config works. If someone has time to test and document this, please do so.
-
Get split gpg to work.
-
~/.gitconfig
[user]
name = Patrick Schleizer
email = adrelanos@riseup.net
signingkey = 0x8D66066A2EEACCDA
[commit]
gpgsign = true
[gpg]
program = qubes-gpg-client-wrapper
## {{ https://forums.whonix.org/t/git-users-enable-fsck-by-default-for-better-security
[transfer]
fsckobjects = true
fsckobjects = true
[fetch]
fsckobjects = true
fsckobjects = true
[receive]
fsckobjects = true
fsckobjects = true
## }}
- usage: theupdateframework/tuf#255
|
Not sure this will require #474. I am using split gpg, but failed setting up split gpg a while ago for git. Don't remember anymore exactly why. A new try just now revealed, that my config works. If someone has time to test and document this, please do so.
|
andrewdavidwong
added
enhancement
P: minor
labels
May 6, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
andrewdavidwong
May 6, 2016
Member
Another helpful thing to add: signing and verifying tags (using conventions specific to the Qubes OS Project). I seem to recall documenting this somewhere. Anyway, here's how I do it:
[alias]
stag = "!id=`git rev-parse --verify HEAD`; git tag -s adw_${id:0:8} -m \"Tag for commit $id\""
vtag = !git tag -v `git describe`
|
Another helpful thing to add: signing and verifying tags (using conventions specific to the Qubes OS Project). I seem to recall documenting this somewhere. Anyway, here's how I do it:
|
kulinacs
referenced this issue
in QubesOS/qubes-doc
May 24, 2016
Merged
Added Split-GPG for Git documentation #145
andrewdavidwong
closed this
in
QubesOS/qubes-doc#145
May 25, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
mfc
May 25, 2016
Member
great! it would be awesome to have the Table of Contents of the page highlight that there is documentation on split-gpg & email and split-gpg & git within, not sure if I should make a separate ticket for that?
|
great! it would be awesome to have the Table of Contents of the page highlight that there is documentation on split-gpg & email and split-gpg & git within, not sure if I should make a separate ticket for that? |
added a commit
to QubesOS/qubes-doc
that referenced
this issue
May 25, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
@mfc: Done. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
awesome! looks great, thanks. |
mfc commentedMay 5, 2016
https://www.qubes-os.org/doc/split-gpg/
I know most Qubes folks have set it up, I imagine it is not too complicated.
https://help.github.com/articles/telling-git-about-your-gpg-key/
https://help.github.com/articles/signing-commits-using-gpg/
this would be really nice to highlight for developers.