<feed xmlns='http://www.w3.org/2005/Atom'>
<title>gnupg, branch debian-unstable-patch-queue</title>
<subtitle>The GNU Privacy Guard.</subtitle>
<id>http://git.bktus.com/gpgfrontend/gnupg/atom?h=debian-unstable-patch-queue</id>
<link rel='self' href='http://git.bktus.com/gpgfrontend/gnupg/atom?h=debian-unstable-patch-queue'/>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gnupg/'/>
<updated>2019-07-20T18:16:21Z</updated>
<entry>
<title>dirmngr: Don't add system CAs for SKS HKPS pool.</title>
<updated>2019-07-20T18:16:21Z</updated>
<author>
<name>NIIBE Yutaka</name>
<email>gniibe@fsij.org</email>
</author>
<published>2019-07-16T01:10:52Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gnupg/commit/?id=6ca2289a9d9cab80748877fc171fe679630e2082'/>
<id>urn:sha1:6ca2289a9d9cab80748877fc171fe679630e2082</id>
<content type='text'>
* dirmngr/http.c [HTTP_USE_GNUTLS] (http_session_new): Clear
add_system_cas.

--

Cherry-picking the master commit of:
	75e0ec65170b7053743406e3f3b605febcf7312a

GnuPG-bug-id: 4594
Signed-off-by: NIIBE Yutaka &lt;gniibe@fsij.org&gt;
(cherry picked from commit 58e234fbeb6cc5908b69a73e50428f02e584e504)

Gbp-Pq: Name dirmngr-Don-t-add-system-CAs-for-SKS-HKPS-pool.patch</content>
</entry>
<entry>
<title>gpg: Improve import slowness.</title>
<updated>2019-07-20T18:16:21Z</updated>
<author>
<name>NIIBE Yutaka</name>
<email>gniibe@fsij.org</email>
</author>
<published>2019-07-10T06:42:07Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gnupg/commit/?id=f56d60f43bccebf7aebfb3fee9ea6d4b0e98c03a'/>
<id>urn:sha1:f56d60f43bccebf7aebfb3fee9ea6d4b0e98c03a</id>
<content type='text'>
* g10/import.c (read_block): Avoid O(N^2) append.
(sec_to_pub_keyblock): Likewise.

Signed-off-by: NIIBE Yutaka &lt;gniibe@fsij.org&gt;
(cherry picked from commit 33c17a8008c3ba3bb740069f9f97c7467f156b54)

Gbp-Pq: Topic from-master
Gbp-Pq: Name gpg-Improve-import-slowness.patch</content>
</entry>
<entry>
<title>gpg: Fix keyring retrieval.</title>
<updated>2019-07-20T18:16:21Z</updated>
<author>
<name>NIIBE Yutaka</name>
<email>gniibe@fsij.org</email>
</author>
<published>2019-07-10T06:06:54Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gnupg/commit/?id=9e12829299c777d1d869e0d8e584f46d391fd931'/>
<id>urn:sha1:9e12829299c777d1d869e0d8e584f46d391fd931</id>
<content type='text'>
* g10/keyring.c (keyring_get_keyblock): Avoid O(N^2) append.

GnuPG-bug-id: 4592
Signed-off-by: NIIBE Yutaka &lt;gniibe@fsij.org&gt;
(cherry picked from commit a7a043e82555a9da984c6fb01bfec4990d904690)

Gbp-Pq: Topic from-master
Gbp-Pq: Name gpg-Fix-keyring-retrieval.patch</content>
</entry>
<entry>
<title>gpg: drop import-clean from default keyserver import options</title>
<updated>2019-07-20T18:16:21Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2019-07-15T20:24:35Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gnupg/commit/?id=ab76d6483741ba15c1ad1233470604153528fba0'/>
<id>urn:sha1:ab76d6483741ba15c1ad1233470604153528fba0</id>
<content type='text'>
* g10/gpg.c (main): drop IMPORT_CLEAN from the
default opt.keyserver_options.import_options
* doc/gpg.texi: reflect this change in the documentation

Given that SELF_SIGS_ONLY is already set, it's not clear what
additional benefit IMPORT_CLEAN provides.  Furthermore, IMPORT_CLEAN
means that receiving an OpenPGP certificate from a keyserver will
potentially delete data that is otherwise held in the local keyring,
which is surprising to users who expect retrieval from the keyservers
to be purely additive.

GnuPG-Bug-Id: 4628
Signed-off-by: Daniel Kahn Gillmor &lt;dkg@fifthhorseman.net&gt;

Gbp-Pq: Name gpg-drop-import-clean-from-default-keyserver-import-optio.patch</content>
</entry>
<entry>
<title>fix spelling</title>
<updated>2019-07-20T18:16:21Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2018-11-18T22:33:55Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gnupg/commit/?id=ca820eda3248d06090cd9d568619f3ec3f003b3b'/>
<id>urn:sha1:ca820eda3248d06090cd9d568619f3ec3f003b3b</id>
<content type='text'>
Gbp-Pq: Name fix-spelling.patch</content>
</entry>
<entry>
<title>Make gpg-zip use tar from $PATH</title>
<updated>2019-07-20T18:16:20Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2018-11-18T22:29:52Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gnupg/commit/?id=4c9bfbe23877abe21588527185a15b2dfb769fd1'/>
<id>urn:sha1:4c9bfbe23877abe21588527185a15b2dfb769fd1</id>
<content type='text'>
Apparently there is no clean way to configure this from ./configure,
and upstream is deprecating gpg-zip anyway.  So just force-set tar to
be manually "tar" (meaning, that we should look in the $PATH at
runtime).

See also https://dev.gnupg.org/T4251 and https://bugs.debian.org/913582

Gbp-Pq: Name Make-gpg-zip-use-tar-from-PATH.patch</content>
</entry>
<entry>
<title>Use hkps://keys.openpgp.org as the default keyserver</title>
<updated>2019-07-20T18:16:20Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2019-07-12T01:52:11Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gnupg/commit/?id=253024a536a3e859d043ff2d8a36c2f4c32ce3e9'/>
<id>urn:sha1:253024a536a3e859d043ff2d8a36c2f4c32ce3e9</id>
<content type='text'>
As of 2.2.17, GnuPG will refuse to accept any third-party
certifications from OpenPGP certificates pulled from the keyserver
network.

The SKS keyserver network currently has at least a dozen popular
certificates which are flooded with enough unusable third-party
certifications that they cannot be retrieved in any reasonable amount
of time.

The hkps://keys.openpgp.org keyserver installation offers HKPS,
performs cryptographic validation, and by policy does not distribute
third-party certifications anyway.

It is not distributed or federated yet, unfortunately, but it is
functional, which is more than can be said for the dying SKS pool.
And given that GnuPG is going to reject all the third-party
certifications anyway, there is no clear "web of trust" rationale for
relying on the SKS pool.

One sticking point is that keys.openpgp.org does not distribute user
IDs unless the user has proven control of the associated e-mail
address.  This means that on standard upstream GnuPG, retrieving
revocations or subkey updates of those certificates will fail, because
upstream GnuPG ignores any incoming certificate without a user ID,
even if it knows a user ID in the local copy of the certificate (see
https://dev.gnupg.org/T4393).

However, we have three patches in
debian/patches/import-merge-without-userid/ that together fix that
bug.

Signed-off-by: Daniel Kahn Gillmor &lt;dkg@fifthhorseman.net&gt;

Gbp-Pq: Name Use-hkps-keys.openpgp.org-as-the-default-keyserver.patch</content>
</entry>
<entry>
<title>dirmngr: Only use SKS pool CA for SKS pool</title>
<updated>2019-07-20T18:16:20Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2019-06-30T15:54:35Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gnupg/commit/?id=263a07f04d138d9c1398568642f3a8e9e3d8fea0'/>
<id>urn:sha1:263a07f04d138d9c1398568642f3a8e9e3d8fea0</id>
<content type='text'>
* dirmngr/http.c (http_session_new): when checking whether the
keyserver is the HKPS pool, check specifically against the pool name,
as ./configure might have been used to select a different default
keyserver.  It makes no sense to apply Kristian's certificate
authority to anything other than the literal host
hkps.pool.sks-keyservers.net.

Signed-off-by: Daniel Kahn Gillmor &lt;dkg@fifthhorseman.net&gt;

Gbp-Pq: Name dirmngr-Only-use-SKS-pool-CA-for-SKS-pool.patch</content>
</entry>
<entry>
<title>gpg: accept subkeys with a good revocation but no self-sig during import</title>
<updated>2019-07-20T18:16:20Z</updated>
<author>
<name>Vincent Breitmoser</name>
<email>look@my.amazin.horse</email>
</author>
<published>2019-06-13T19:27:43Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gnupg/commit/?id=b2605ad61451796db371590b33f207da3553c676'/>
<id>urn:sha1:b2605ad61451796db371590b33f207da3553c676</id>
<content type='text'>
* g10/import.c (chk_self_sigs): Set the NODE_GOOD_SELFSIG flag when we
encounter a valid revocation signature. This allows import of subkey
revocation signatures, even in the absence of a corresponding subkey
binding signature.

--

This fixes the remaining test in import-incomplete.scm.

GnuPG-Bug-id: 4393
Signed-off-by: Daniel Kahn Gillmor &lt;dkg@fifthhorseman.net&gt;

Gbp-Pq: Topic import-merge-without-userid
Gbp-Pq: Name gpg-accept-subkeys-with-a-good-revocation-but-no-self-sig.patch</content>
</entry>
<entry>
<title>gpg: allow import of previously known keys, even without UIDs</title>
<updated>2019-07-20T18:16:20Z</updated>
<author>
<name>Vincent Breitmoser</name>
<email>look@my.amazin.horse</email>
</author>
<published>2019-06-13T19:27:42Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gnupg/commit/?id=e70841404d72f36f0eae3dbde7d311da4e86f1a8'/>
<id>urn:sha1:e70841404d72f36f0eae3dbde7d311da4e86f1a8</id>
<content type='text'>
* g10/import.c (import_one): Accept an incoming OpenPGP certificate that
has no user id, as long as we already have a local variant of the cert
that matches the primary key.

--

This fixes two of the three broken tests in import-incomplete.scm.

GnuPG-Bug-id: 4393
Signed-off-by: Daniel Kahn Gillmor &lt;dkg@fifthhorseman.net&gt;

Gbp-Pq: Topic import-merge-without-userid
Gbp-Pq: Name gpg-allow-import-of-previously-known-keys-even-without-UI.patch</content>
</entry>
</feed>
