Hi. Thanks to both of you for your helpful comments.
Jonathan Nieder writes ("Re: git signed push server-side"):
> Ian Jackson wrote[1]:
> > 2. git-receive-pack calls gpg (Debian #852684)
> >
> > It would be better if it called gpgv.
...
> think respecting gpg.p
Jonathan Nieder writes:
> I think respecting gpg.program would be nicer. Is there a reason not
> to do that?
>
> I suspect receive-pack just forgot to call git_gpg_config.
That would be a good change.
> How is the keyring configured for other commands that use GPG, like
> "git tag -v"? (Forgi
Jonathan Nieder writes:
> +Dave Borowitz, who implemented push cert handling in JGit and Gerrit
> Hi Ian,
>
> Ian Jackson wrote[1]:
>
>> I have been investigating git signed pushes. I found a number of
>> infelicities in the server side implementation which make using this
>> in practice rather
+Dave Borowitz, who implemented push cert handling in JGit and Gerrit
Hi Ian,
Ian Jackson wrote[1]:
> I have been investigating git signed pushes. I found a number of
> infelicities in the server side implementation which make using this
> in practice rather difficult. I'm emailing here (before
Ian Jackson writes:
> I have been investigating git signed pushes. I found a number of
> infelicities in the server side implementation which make using this
> in practice rather difficult. I'm emailing here (before writing
> patches) to see what people think of my proposed changes.
> ...
> If
I have been investigating git signed pushes. I found a number of
infelicities in the server side implementation which make using this
in practice rather difficult. I'm emailing here (before writing
patches) to see what people think of my proposed changes.
1. PUSH_CERT_KEY has truncated keyid (D
6 matches
Mail list logo
