Messages in this thread | | | Date | Mon, 25 Apr 2005 04:08:39 +0100 (IST) | From | Paul Jakma <> | Subject | Re: Git-commits mailing list feed. |
| |
Ah, to add to below..
If one wished, one could optionally store the actual signature data as a seperate blob object and refer to it in the signing object. Not needed really for a GPG ASCII clear-signed detached signature (tiny and they're ASCII obviously :) ), but who knows.
On Mon, 25 Apr 2005, Paul Jakma wrote:
> - add the 'signature object' to the respository after the signed > object > > So a 'signed commit' turns into the > > - tool preparing the commit object, > - get the user to sign it > - save the detached signature for later > - adding the commit object to the repository
- adding the signature blob, if it is to stored as a blob
> - prepare the signing object and add to repository
> The repository head then refers then to signature object, which could > (handwaving) look something like: > > Object Signature > Signing <object ID, in this case of the commit object> > Sign-type GPG
With either a 'Signature <ID of signature data blob>' or else:
> <signature data>
regards, -- Paul Jakma paul@clubi.ie paul@jakma.org Key ID: 64A2FF6A Fortune: May you have many beautiful and obedient daughters. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |