<feed xmlns='http://www.w3.org/2005/Atom'>
<title>git/gpg-interface.h, branch v2.6.2</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/git/git.git/
</subtitle>
<id>https://git.shady.money/git/atom?h=v2.6.2</id>
<link rel='self' href='https://git.shady.money/git/atom?h=v2.6.2'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/'/>
<updated>2015-06-22T21:20:47Z</updated>
<entry>
<title>verify-commit: add option to print raw gpg status information</title>
<updated>2015-06-22T21:20:47Z</updated>
<author>
<name>brian m. carlson</name>
<email>sandals@crustytoothpaste.net</email>
</author>
<published>2015-06-21T23:14:42Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=aeff29dd4dab01b497b2a2cf73e982e846a5fe4c'/>
<id>urn:sha1:aeff29dd4dab01b497b2a2cf73e982e846a5fe4c</id>
<content type='text'>
verify-commit by default displays human-readable output on standard
error.  However, it can also be useful to get access to the raw gpg
status information, which is machine-readable, allowing automated
implementation of signing policy.  Add a --raw option to make
verify-commit produce the gpg status information on standard error
instead of the human-readable format.

Signed-off-by: brian m. carlson &lt;sandals@crustytoothpaste.net&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>gpg: centralize printing signature buffers</title>
<updated>2015-06-22T21:20:47Z</updated>
<author>
<name>brian m. carlson</name>
<email>sandals@crustytoothpaste.net</email>
</author>
<published>2015-06-21T23:14:41Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=ca194d50b84b53a0b711fef46d1a47657ec5da41'/>
<id>urn:sha1:ca194d50b84b53a0b711fef46d1a47657ec5da41</id>
<content type='text'>
The code to handle printing of signature data from a struct
signature_check is very similar between verify-commit and verify-tag.
Place this in a single function.  verify-tag retains its special case
behavior of printing the tag even when no valid signature is found.

Signed-off-by: brian m. carlson &lt;sandals@crustytoothpaste.net&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>gpg: centralize signature check</title>
<updated>2015-06-22T21:20:46Z</updated>
<author>
<name>brian m. carlson</name>
<email>sandals@crustytoothpaste.net</email>
</author>
<published>2015-06-21T23:14:40Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=434060ec6d9bf50f095db901da3fb9b557e11df1'/>
<id>urn:sha1:434060ec6d9bf50f095db901da3fb9b557e11df1</id>
<content type='text'>
verify-commit and verify-tag both share a central codepath for verifying
commits: check_signature.  However, verify-tag exited successfully for
untrusted signature, while verify-commit exited unsuccessfully.
Centralize this signature check and make verify-commit adopt the older
verify-tag behavior.  This behavior is more logical anyway, as the
signature is in fact valid, whether or not there's a path of trust to
the author.

Signed-off-by: brian m. carlson &lt;sandals@crustytoothpaste.net&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>verify-tag: share code with verify-commit</title>
<updated>2015-06-22T21:20:45Z</updated>
<author>
<name>brian m. carlson</name>
<email>sandals@crustytoothpaste.net</email>
</author>
<published>2015-06-21T23:14:38Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=a4cc18f2934b8d2f00c7c3e11107acb6bfafe2c6'/>
<id>urn:sha1:a4cc18f2934b8d2f00c7c3e11107acb6bfafe2c6</id>
<content type='text'>
verify-tag was executing an entirely different codepath than
verify-commit, except for the underlying verify_signed_buffer.  Move
much of the code from check_commit_signature to a generic
check_signature function and adjust both codepaths to call it.

Update verify-tag to explicitly output the signature text, as we now
call verify_signed_buffer with strbufs to catch the output, which
prevents it from being printed automatically.

Signed-off-by: brian m. carlson &lt;sandals@crustytoothpaste.net&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>gpg-interface: move parse_signature() to where it should be</title>
<updated>2014-09-15T20:23:20Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2014-08-19T20:18:07Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=d7c67668fe10184736bdfe953ed8dcbfdb57e0c2'/>
<id>urn:sha1:d7c67668fe10184736bdfe953ed8dcbfdb57e0c2</id>
<content type='text'>
Our signed-tag objects set the standard format used by Git to store
GPG-signed payload (i.e. the payload followed by its detached
signature) [*1*], and it made sense to have a helper to find the
boundary between the payload and its signature in tag.c back then.

Newer code added later to parse other kinds of objects that learned
to use the same format to store GPG-signed payload (e.g. signed
commits), however, kept using the helper from the same location.

Move it to gpg-interface; the helper is no longer about signed tag,
but it is how our code and data interact with GPG.

[Reference]
*1* http://thread.gmane.org/gmane.linux.kernel/297998/focus=1383

Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>gpg-interface: move parse_gpg_output() to where it should be</title>
<updated>2014-09-15T20:23:20Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2014-08-14T22:31:13Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=a50e7ca3215492b16d96221cf762dbe71ed99722'/>
<id>urn:sha1:a50e7ca3215492b16d96221cf762dbe71ed99722</id>
<content type='text'>
Earlier, ffb6d7d5 (Move commit GPG signature verification to
commit.c, 2013-03-31) moved this helper that used to be in pretty.c
(i.e. the output code path) to commit.c for better reusability.

It was a good first step in the right direction, but still suffers
from a myopic view that commits will be the only thing we would ever
want to sign---we would actually want to be able to reuse it even
wider.

The function interprets what GPG said; gpg-interface is obviously a
better place.  Move it there.

Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>gpg-interface: provide access to the payload</title>
<updated>2014-06-23T22:50:30Z</updated>
<author>
<name>Michael J Gruber</name>
<email>git@drmicha.warpmail.net</email>
</author>
<published>2014-06-23T07:05:48Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=71c214c840782a67801fc8dbf5fe8a4f4fc62d01'/>
<id>urn:sha1:71c214c840782a67801fc8dbf5fe8a4f4fc62d01</id>
<content type='text'>
In contrast to tag signatures, commit signatures are put into the
header, that is between the other header parts and commit messages.

Provide access to the commit content sans the signature, which is the
payload that is actually signed. Commit signature verification does the
parsing anyways, and callers may wish to act on or display the commit
object sans the signature.

Signed-off-by: Michael J Gruber &lt;git@drmicha.warpmail.net&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>gpg-interface: provide clear helper for struct signature_check</title>
<updated>2014-06-23T22:50:29Z</updated>
<author>
<name>Michael J Gruber</name>
<email>git@drmicha.warpmail.net</email>
</author>
<published>2014-06-23T07:05:47Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=01e57b5d91b0c9f2ac93708c5c2cbcd4731ddd34'/>
<id>urn:sha1:01e57b5d91b0c9f2ac93708c5c2cbcd4731ddd34</id>
<content type='text'>
The struct has been growing members whose malloced memory needs to be
freed. Do this with one helper function so that no malloced memory shall
be left unfreed.

Signed-off-by: Michael J Gruber &lt;git@drmicha.warpmail.net&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>merge/pull Check for untrusted good GPG signatures</title>
<updated>2013-04-01T05:38:49Z</updated>
<author>
<name>Sebastian Götte</name>
<email>jaseg@physik.tu-berlin.de</email>
</author>
<published>2013-03-31T16:02:46Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=eb307ae7bb78ccde4e2ac69f302ccf8834883628'/>
<id>urn:sha1:eb307ae7bb78ccde4e2ac69f302ccf8834883628</id>
<content type='text'>
When --verify-signatures is specified, abort the merge in case a good
GPG signature from an untrusted key is encountered.

Signed-off-by: Sebastian Götte &lt;jaseg@physik-pool.tu-berlin.de&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Move commit GPG signature verification to commit.c</title>
<updated>2013-04-01T02:15:11Z</updated>
<author>
<name>Sebastian Götte</name>
<email>jaseg@physik.tu-berlin.de</email>
</author>
<published>2013-03-31T16:00:14Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=ffb6d7d5c99e4097e512def20b0133b7ee900953'/>
<id>urn:sha1:ffb6d7d5c99e4097e512def20b0133b7ee900953</id>
<content type='text'>
Signed-off-by: Sebastian Götte &lt;jaseg@physik-pool.tu-berlin.de&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
</feed>
