On Mon, Aug 06, 2018 at 08:24:25PM +, Tacitus Aedifex wrote:
> the older patch set suggested the idea of using PEM strings to match up the
> signature payload with a certain signing tool. i can't tell if they mean
> the 'pre-ecapsulation boundary' (e.g. '-BEGIN FOO-') or if they mean
On Fri, Aug 03, 2018 at 06:07:46PM -0400, Jeff King wrote:
There's been some work on this lately. See this patch and the response
thread:
https://public-inbox.org/git/20180409204129.43537-9-mastahy...@gmail.com/
The more recent work focused on just doing the minimum to provide
gpg/gpgsm
On August 3, 2018 5:39 PM, Tacitus Aedifex wrote:
> I'm looking at the existing commit signing and verification integration and
> it is
> all GPG specific. I'm interested in refactoring the code to have a generic
> signing/verifying interface so that "drivers"
> for other signing tools can be
On Fri, Aug 03, 2018 at 09:38:34PM +, Tacitus Aedifex wrote:
> I'm looking at the existing commit signing and verification
> integration and it is all GPG specific. I'm interested in refactoring
> the code to have a generic signing/verifying interface so that "drivers"
> for other signing
I'm looking at the existing commit signing and verification
integration and it is all GPG specific. I'm interested in refactoring
the code to have a generic signing/verifying interface so that "drivers"
for other signing tools can be created and other signing tools can be
used (e.g. OpenBSD
5 matches
Mail list logo
