dkg (Daniel Kahn Gillmor)
User

Projects

Today

  • Clear sailing ahead.

Tomorrow

  • Clear sailing ahead.

Monday

  • Clear sailing ahead.

User Details

User Since
Mar 27 2017, 4:49 PM (147 w, 5 d)
Availability
Available

Recent Activity

Yesterday

dkg added a comment to T4817: dirmgr keys.openpgp.org:443 Address family not supported by protocol.

(if you don't want to publish the full strace output here because you're concerned it might leak some information about your machine or your network, but you're ok sharing it with me personally, you can send it to me privately by e-mail, encrypted to the OpenPGP certificate with fingerprint C4BC2DDB38CCE96485EBE9C2F20691179038E5C6, and sent to one of the e-mail addresses associated with that certificate. please make a note here if you do that)

Fri, Jan 24, 3:20 PM · Bug Report
dkg added a comment to T4817: dirmgr keys.openpgp.org:443 Address family not supported by protocol.

ok, that's deeply weird. i'm assuming that this machine has IPv4 connectivity. I have no idea why dirmngr would be returning EAFNOSUPPORT in that case.

Fri, Jan 24, 3:18 PM · Bug Report
dkg added a task to rM414938cfedbd: m4/python: Scan for python 3.8 as well: T4821: gpgme's m4/python.m4 doesn't search for python 3.8.
Fri, Jan 24, 12:32 AM
dkg added a commit to T4821: gpgme's m4/python.m4 doesn't search for python 3.8: rM414938cfedbd: m4/python: Scan for python 3.8 as well.
Fri, Jan 24, 12:32 AM · gpgme
dkg added commits to T4820: gpgme's json test fails with gpg 2.2.19: rMc4cf527ea227: gpg: Send --with-keygrip when listing keys, rMf2aeb2563ba2: tests/json: Bravo key does not have secret key material.
Fri, Jan 24, 12:31 AM · gpgme, Bug Report
dkg added a task to rMc4cf527ea227: gpg: Send --with-keygrip when listing keys: T4820: gpgme's json test fails with gpg 2.2.19.
Fri, Jan 24, 12:31 AM
dkg added a task to rMf2aeb2563ba2: tests/json: Bravo key does not have secret key material: T4820: gpgme's json test fails with gpg 2.2.19.
Fri, Jan 24, 12:31 AM
dkg added a comment to T4821: gpgme's m4/python.m4 doesn't search for python 3.8.

branch dkg/fix-4821 contains a fix for this, in commit 414938cfedbdb97b83d00e8619dec9502096be22

Fri, Jan 24, 12:31 AM · gpgme
dkg committed rM414938cfedbd: m4/python: Scan for python 3.8 as well (authored by dkg).
m4/python: Scan for python 3.8 as well
Fri, Jan 24, 12:30 AM
dkg created T4821: gpgme's m4/python.m4 doesn't search for python 3.8.
Fri, Jan 24, 12:30 AM · gpgme
dkg committed rMc4cf527ea227: gpg: Send --with-keygrip when listing keys (authored by dkg).
gpg: Send --with-keygrip when listing keys
Fri, Jan 24, 12:26 AM
dkg committed rMf2aeb2563ba2: tests/json: Bravo key does not have secret key material (authored by dkg).
tests/json: Bravo key does not have secret key material
Fri, Jan 24, 12:26 AM
dkg added a comment to T4820: gpgme's json test fails with gpg 2.2.19.

in particular, c4cf527ea227edb468a84bf9b8ce996807bd6992 and f2aeb2563ba2f55eea7f52041e52062fdc839a64

Fri, Jan 24, 12:25 AM · gpgme, Bug Report
dkg added a comment to T4820: gpgme's json test fails with gpg 2.2.19.

The dkg/fix-4820 branch now has these two fixes.

Fri, Jan 24, 12:23 AM · gpgme, Bug Report

Thu, Jan 23

dkg added a comment to T4820: gpgme's json test fails with gpg 2.2.19.

For easier reference or searchability, the test error looks like this:

Thu, Jan 23, 11:57 PM · gpgme, Bug Report
dkg created T4820: gpgme's json test fails with gpg 2.2.19.
Thu, Jan 23, 11:40 PM · gpgme, Bug Report
dkg added a comment to T4817: dirmgr keys.openpgp.org:443 Address family not supported by protocol.

This appears to be a different error than above. here we see:

Thu, Jan 23, 5:50 PM · Bug Report

Wed, Jan 22

dkg added a comment to T4817: dirmgr keys.openpgp.org:443 Address family not supported by protocol.

this looks to me like a problem with the TLS handshake -- it looks like this is a response coming from the TLS stack -- as rfc 8446 says, alert 49 is access_denied:

Wed, Jan 22, 6:47 PM · Bug Report

Fri, Jan 17

dkg added a comment to T1983: gpg2 prefers missing secret key to available key on card.

This is also https://bugs.debian.org/346241

Fri, Jan 17, 7:25 PM · Bug Report, gnupg

Thu, Jan 16

dkg added a comment to T4796: GpgOL should hide "legacy display" parts when it encounters them.

thanks for the fix, @aheinecke ! can you post screenshots of the changes? or do you have a nightly build i could test?

Thu, Jan 16, 10:42 PM · gpgol, Bug Report, gpg4win

Tue, Jan 14

dkg added a comment to T4809: Non-operational functions and missing feature.

In T4809#131931, @werner wrote:

BTW, the qualitybar is not shown by default, only if you configure sme of the extra password checks. We may even remove it completely because it leads to wrong assumption on why a passphrase is required.

Tue, Jan 14, 3:30 PM · Fedora, pinentry, Bug Report
dkg added a comment to T4809: Non-operational functions and missing feature.

@Rycky_Tigg cases 1, 2, and 3 that you document here each show the behavior that i would expect from pinentry-gnome3, given the definition of its Assuan-based API and its use of gcr-prompter. (i'm assuming that in case 3 the user just waited longer than the allowed timeout)

Tue, Jan 14, 3:29 PM · Fedora, pinentry, Bug Report
dkg added a comment to T4809: Non-operational functions and missing feature.

pinentry-gnome uses gcr's gcr_prompt_set_password_new to prompt for a new password, and ignores the SETQUALITYBAR assuan command.

Tue, Jan 14, 12:12 AM · Fedora, pinentry, Bug Report

Dec 24 2019

dkg created T4796: GpgOL should hide "legacy display" parts when it encounters them.
Dec 24 2019, 11:27 PM · gpgol, Bug Report, gpg4win

Dec 20 2019

dkg added a comment to T4393: GnuPG should always accept key updates even if the update does not contain UIDs.

It has now been over 6 months since the patches were available to fix this problem and they have not been adopted upstream.

Dec 20 2019, 6:56 PM · gnupg (gpg23), Feature Request

Dec 9 2019

dkg added a comment to T4393: GnuPG should always accept key updates even if the update does not contain UIDs.

@werner, i don't understand your last remark. what "required computations" do you think the proposed patches are "moving" from the server to the client?

Dec 9 2019, 6:07 PM · gnupg (gpg23), Feature Request

Dec 6 2019

dkg added a comment to T4766: gpgme_signature_t relies on `unsigned long` for signature creation and expiration times.

fwiw, ensuring that overflow for either field results in ULONG_MAX (rather than wrapping around) would go a long way toward this problem being something that we can reasonably put off for another 50 years.

Dec 6 2019, 10:31 PM · gpgme, Bug Report

Dec 4 2019

dkg added a comment to T4766: gpgme_signature_t relies on `unsigned long` for signature creation and expiration times.

The most plausible fix to the Y2K38 problem on 32-bit machines is to simply move to a 64-bit time_t at the same time as any other major system-wide ABI break. However, if that ABI break doesn't also change the size of long to more than 32 bits, GPGME will remain unfixed in spite of any architectural correction.

Dec 4 2019, 4:42 PM · gpgme, Bug Report
dkg added a comment to T4767: gpgme_signature_t exp_timestamp behaves differently for OpenPGP vs. CMS.

Very few OpenPGP data signatures have an expiration time either, fwiw. I have never actually seen one in the wild, and no one that i know uses --ask-sig-expire or --default-sig-expire (it shows up in the cupt test suite and the apt test suite, but doesn't appear to be actually used by anything).

Dec 4 2019, 10:03 AM · OpenPGP, S/MIME, gpgme, Bug Report
dkg created T4767: gpgme_signature_t exp_timestamp behaves differently for OpenPGP vs. CMS.
Dec 4 2019, 8:02 AM · OpenPGP, S/MIME, gpgme, Bug Report
dkg created T4766: gpgme_signature_t relies on `unsigned long` for signature creation and expiration times.
Dec 4 2019, 3:52 AM · gpgme, Bug Report
dkg committed rMc0c97dbbe6e0: gpgme-tool: Fix help text for INCLUDE_CERTS. (authored by dkg).
gpgme-tool: Fix help text for INCLUDE_CERTS.
Dec 4 2019, 12:45 AM

Dec 3 2019

dkg added a comment to T4585: pinentry-tty mishandles ctrl-C.

pinentry-tty is pretty fragile, and designed to be handled in a particular way. I strongly recommend a different workflow if you're using gpg secret key operations in a regular process. either:

Dec 3 2019, 10:46 PM · Bug Report
dkg created T4765: gpgsm --import should not try to invoke dirmngr if it is not necessary.
Dec 3 2019, 10:26 PM · gnupg (gpg23), S/MIME, Bug Report

Nov 25 2019

dkg created T4757: gpgsm --import --quiet is not quiet.
Nov 25 2019, 8:43 PM · S/MIME, Bug Report
dkg created T4756: gpgsm --list-keys behaves differently than gpg when --passphrase is supplied.
Nov 25 2019, 7:06 PM · Feature Request, S/MIME
dkg added a comment to T4735: Please provide an option to make --verify accept only signatures from specific trusted UID.

To be clear, i believe @mgorny means that he wants the User ID containing the e-mail address to be considered *valid* (that is, full or ultimate validity). I don't think this operation should care about ownertrust.

Nov 25 2019, 4:30 PM · Feature Request

Nov 21 2019

dkg created T4751: gpgsm unable to import a PKCS12 file with a NULL password.
Nov 21 2019, 4:22 AM · gnupg, Feature Request, S/MIME

Nov 18 2019

dkg added a comment to T4393: GnuPG should always accept key updates even if the update does not contain UIDs.

it's been almost a quarter year since my last nudge on this supplied patch. It's not clear to me why it hasn't been merged in master. I'm trying to not be a nag, but:

Nov 18 2019, 4:03 AM · gnupg (gpg23), Feature Request

Nov 7 2019

dkg reopened T4741: PLAINTEXT_LENGTH is sometimes incorrect as "Open".

DETAILS says:

*** PLAINTEXT_LENGTH <length>
    This indicates the length of the plaintext that is about to be
    written.  Note that if the plaintext packet has partial length
    encoding it is not possible to know the length ahead of time.  In
    that case, this status tag does not appear.
Nov 7 2019, 3:36 PM · gnupg (gpg22), Bug Report
dkg created T4741: PLAINTEXT_LENGTH is sometimes incorrect.
Nov 7 2019, 6:02 AM · gnupg (gpg22), Bug Report

Oct 28 2019

dkg created T4732: X.509 cert for openpgpkey.gnupg.org is expired.
Oct 28 2019, 11:36 PM · gpgweb, Bug Report

Oct 24 2019

dkg reopened T4725: Dubious filename in literal data packet when encrypting with GPGME/GnuPGv1.4.23 as "Open".

@werner, are you saying that gpgme is not fully supported for use with gpg 1.4?

Oct 24 2019, 9:22 PM · gpgme, Bug Report
dkg added a comment to T4726: auto-key-locate only works with raw e-mail addresses (not angle-brackets).

@werner, you seem to be saying that -r does not imply "key lookups on remote services". Is that correct?

Oct 24 2019, 8:42 PM · gnupg (gpg22), wkd, Bug Report
dkg added a comment to T4513: dirmngr should try the configured keyservers anyway even if they are all dead.

There is a growing bit of popular lore in the GnuPG community that "when keyserver operations fail, you solve that problem with killall dirmngr." I believe this suggestion is potentially damaging (the long-running daemon may be in the middle of operations for a client that you don't know about), but i suspect it is circulating as advice because it resolves the situation outlined in this ticket. For whatever ephemeral reason, dirmngr gets stuck, and fails to notice that this situation has resolved itself.

Oct 24 2019, 5:39 PM · Feature Request, Keyserver, dirmngr

Oct 23 2019

dkg added a comment to T4725: Dubious filename in literal data packet when encrypting with GPGME/GnuPGv1.4.23.

@justus can you provide an example of the gpgme code you're using that generates this weirdness?

Oct 23 2019, 3:43 AM · gpgme, Bug Report
dkg created T4726: auto-key-locate only works with raw e-mail addresses (not angle-brackets).
Oct 23 2019, 3:24 AM · gnupg (gpg22), wkd, Bug Report

Oct 2 2019

dkg reopened T4400: GnuPG fails to parse algorithm preferences (and presumably features) from direct key signatures as "Open".

I agree with @werner that when presented with a User ID with self-sig with preference, the preferences subpackets from the self-sig should take precedence.

Oct 2 2019, 4:33 PM · Bug Report

Sep 10 2019

dkg added a comment to T4704: Wrong error message when key is expired.

yep, the implementation thinks that the default signing key is expired due to metadata contained in the public keyring. The secret key is available to the implementation. So the error mesage No secret key can cause confusion and/or panic if the user thinks they've actually lost their secret key.

Sep 10 2019, 3:15 PM · gnupg (gpg23), UI, Bug Report

Sep 9 2019

dkg added projects to T4704: Wrong error message when key is expired: gnupg (gpg22), UI.

fwiw, i can reproduce this on debian unstable with gpg version 2.2.17, without a redirected agent -- so the agent redirection isn't relevant here.

Sep 9 2019, 5:06 PM · gnupg (gpg23), UI, Bug Report
dkg added a comment to T4698: Results from clang analyzer.

@stm -- thank you for this!

Sep 9 2019, 4:34 PM · gpgrt, Bug Report

Sep 1 2019

dkg created T4694: manage first-party attestations.
Sep 1 2019, 1:45 PM · Feature Request

Aug 27 2019

dkg added a comment to T4276: Context.decrypt() throws an error if *any* signature is bad.

i'm actually running make -j3 check, since make -j3 distcheck has the problems described in T4688.

Aug 27 2019, 4:50 PM · gpgme, Python, Bug Report
dkg created T4688: `make distcheck` fails trying to make `rst/gpgme-python-howto.rst`.
Aug 27 2019, 4:48 PM · gpgme, Bug Report
dkg added a comment to T4276: Context.decrypt() throws an error if *any* signature is bad.

So i've been able to (intermittently) reproduce the failures that i think @werner was alluding to here, but not under any circumstances where i can get them to happen reliably to understand what's going on.

Aug 27 2019, 4:18 PM · gpgme, Python, Bug Report

Aug 24 2019

dkg added a comment to T4393: GnuPG should always accept key updates even if the update does not contain UIDs.

It has now been more than a month since:

Aug 24 2019, 12:55 AM · gnupg (gpg23), Feature Request

Aug 22 2019

dkg added a comment to T2669: gpg --import auto-launches gpg-agent even when no secret keys are imported.

Thanks, @gniibe. From reading this patch (i haven't tested it), it looks like it would avoid most unnecessary agent launches (and agent communication) in the (b) case, which is a win over the status quo.

Aug 22 2019, 8:47 PM · Bug Report, gnupg

Aug 21 2019

dkg added a comment to T4679: WKD spec should document exactly when a client should fall back from "advanced" to "direct" URL.

This was also raised for (hopefully) wider discussion on the IETF mailing list.

Aug 21 2019, 8:32 PM · Documentation, wkd
dkg set External Link to https://en.wikipedia.org/wiki/Ms. on T4682: Salutation "Mrs." implies that the user is married. Use "Ms." instead..
Aug 21 2019, 7:52 PM · gnupg (gpg23), Bug Report
dkg added a task to rGc4b9eba1d6a6: gpg: Adjust female-gendered salutation from Mrs. to Ms.: T4682: Salutation "Mrs." implies that the user is married. Use "Ms." instead..
Aug 21 2019, 7:51 PM
dkg added a commit to T4682: Salutation "Mrs." implies that the user is married. Use "Ms." instead.: rGc4b9eba1d6a6: gpg: Adjust female-gendered salutation from Mrs. to Ms..
Aug 21 2019, 7:51 PM · gnupg (gpg23), Bug Report
dkg added a comment to T4682: Salutation "Mrs." implies that the user is married. Use "Ms." instead..

i've just pushed rGc4b9eba1d6a63b73238dcbb644b365dc53563f3d to the dkg-fix-T4682 branch resolve this.

Aug 21 2019, 7:51 PM · gnupg (gpg23), Bug Report
dkg committed rGc4b9eba1d6a6: gpg: Adjust female-gendered salutation from Mrs. to Ms. (authored by dkg).
gpg: Adjust female-gendered salutation from Mrs. to Ms.
Aug 21 2019, 7:51 PM
dkg created T4682: Salutation "Mrs." implies that the user is married. Use "Ms." instead..
Aug 21 2019, 7:49 PM · gnupg (gpg23), Bug Report

Aug 20 2019

dkg created T4680: dirmngr documentation titles claim X.509 only, but should describe full scope of the daemon.
Aug 20 2019, 11:13 PM · gnupg, Documentation, Bug Report
dkg created T4679: WKD spec should document exactly when a client should fall back from "advanced" to "direct" URL.
Aug 20 2019, 10:59 PM · Documentation, wkd
dkg committed rGb7793c3af32b: doc: fix minor spelling and tense errors (authored by dkg).
doc: fix minor spelling and tense errors
Aug 20 2019, 10:05 PM
dkg committed rGcba6e1bd7242: doc: clarify CARD event counter. (authored by dkg).
doc: clarify CARD event counter.
Aug 20 2019, 10:05 PM
dkg added a comment to T4677: Failure using pinentry-tty or pinentry-curses when GnuPG's standard input is a file.

@skeeto can you edit the summary/title of this ticket to better reflect what you think the underlying issue is?

Aug 20 2019, 2:45 AM · unreproducible, gnupg (gpg22), Bug Report
dkg reopened T2011: gnupg should notify cancellation of its operation to gpg-agent to kill pinentry as "Open".
Aug 20 2019, 2:44 AM · Bug Report, gpgagent
dkg added a comment to T2011: gnupg should notify cancellation of its operation to gpg-agent to kill pinentry.

This appears to be https://bugs.debian.org/850946 and it does not appear to be fixed to me.

Aug 20 2019, 2:43 AM · Bug Report, gpgagent
dkg reopened T2013: pinentry-curses / pinentry-tty should emit a bell when showing a dialog as "Open".

reviewing this, i think the situation is:

Aug 20 2019, 2:36 AM · pinentry, Feature Request

Aug 10 2019

dkg added a comment to T4672: E-mail encryption in Microsoft Outlook Office 365 does not work properly.

Are you seeing mixed-up MIME parts? or a different problem?

Aug 10 2019, 4:26 AM · Bug Report, gpg4win
dkg added a comment to T4618: DANE OpenPGP certificate retrieval does not verify DNSSEC signatures.

WKD and DANE/OPENPGPKEY offer rather distinct properties. I'd be hard-pressed to say that one is "better" than the other without understanding the threat model and concerns of the evaluator:

Aug 10 2019, 4:24 AM · dns, dirmngr

Aug 3 2019

dkg created T4668: `gpgconf --launch gpg-agent` tells me to run `gpgconf --check-options gpg-agent`, but the latter command gives me no information.
Aug 3 2019, 7:30 PM · gnupg (gpg22), Bug Report
dkg created T4667: "gpg: deleting secret key failed: No pinentry" when in --batch mode with --pinentry=loopback.
Aug 3 2019, 7:15 PM · gnupg (gpg22), Bug Report
dkg added a comment to T4666: gpg --delete-secret-keys: excessive and unclear prompting, surprising outcomes.

I also observe that the text in the GUI prompts is remarkably unclear on its own. setting aside the grammar, punctuation, and wording, the prompts don't expose the usage flags set for the secret keys, which is possibly the only detail that a user with a single OpenPGP certificate would care about: "am i deleting my signing-capable subkey or my decryption-capable subkey?"

Aug 3 2019, 7:10 PM · gnupg (gpg23), Bug Report
dkg created T4666: gpg --delete-secret-keys: excessive and unclear prompting, surprising outcomes.
Aug 3 2019, 7:05 PM · gnupg (gpg23), Bug Report
dkg created T4665: gpg --delete-key of subkey leaves dangling subkey binding signature.
Aug 3 2019, 5:12 PM · gnupg (gpg22), Bug Report

Jul 31 2019

dkg created T4662: --locate-external-keys does not interact well with --no-auto-key-locate.
Jul 31 2019, 7:31 PM · gnupg (gpg22), Bug Report
dkg reopened T4661: gpg-agent "getinfo cmd_has_option" is frequently wrong as "Open".

Please update the documentation for the function in that case.

Jul 31 2019, 4:49 PM · Documentation, gpgagent
dkg added a comment to T4652: avoid unnecessary trailing NUL byte in S-expressions.

Please see my explanation on gnupg-devel about why the trailing NUL is a source of pain and difficulty for would-be adopters.

Jul 31 2019, 4:45 PM · gnupg, Bug Report

Jul 29 2019

dkg created T4661: gpg-agent "getinfo cmd_has_option" is frequently wrong.
Jul 29 2019, 8:54 PM · Documentation, gpgagent

Jul 27 2019

dkg added a comment to T4658: Fix a dangling pointer in pinentry's qt/main.cpp.

I've just uploaded pinentry 1.1.0-3 to debian unstable with this fix in it.

Jul 27 2019, 6:07 AM · pinentry, Bug Report
dkg added a comment to T4658: Fix a dangling pointer in pinentry's qt/main.cpp.

@aheinecke thanks for the heads-up. i'll pull this in.

Jul 27 2019, 1:16 AM · pinentry, Bug Report

Jul 25 2019

dkg added a comment to rGfdd1567743cc: gpg,gpgsm: Handle pkdecrypt responses with or without NUL terminators.

@aheinecke

Due to socket forwarding we can have different versions of gpg-agent and gpg / gpgsm because they are on different machines and afaik we try to support it.

Jul 25 2019, 2:54 PM
dkg added a comment to rGfdd1567743cc: gpg,gpgsm: Handle pkdecrypt responses with or without NUL terminators.

fwiw, if the old gcrypt actually returned a radically different API, it should have a larger SONAME across that change, and NEED_LIBGCRYPT_VERSION should reflect a source version that forces it past that SONAME. I don't know what version of libgcrypt behaved differently -- is there a reference for that?

Jul 25 2019, 2:45 PM
dkg added a comment to rGfdd1567743cc: gpg,gpgsm: Handle pkdecrypt responses with or without NUL terminators.

I don't think there's a problem to have a long explanatory message in the main repository, as i think it makes it easier to understand, and space is not an issue.

Jul 25 2019, 2:40 PM
dkg added a task to rGefffd9907b75: agent: Do not place a trailing NUL byte on S-expressions: T4652: avoid unnecessary trailing NUL byte in S-expressions.
Jul 25 2019, 1:59 AM
dkg added commits to T4652: avoid unnecessary trailing NUL byte in S-expressions: rGefffd9907b75: agent: Do not place a trailing NUL byte on S-expressions, rGfdd1567743cc: gpg,gpgsm: Handle pkdecrypt responses with or without NUL terminators.
Jul 25 2019, 1:59 AM · gnupg, Bug Report
dkg added a task to rGfdd1567743cc: gpg,gpgsm: Handle pkdecrypt responses with or without NUL terminators: T4652: avoid unnecessary trailing NUL byte in S-expressions.
Jul 25 2019, 1:59 AM
dkg added a comment to T4652: avoid unnecessary trailing NUL byte in S-expressions.

I've just broken out my changes into two commits, one that makes gpg and gpgsm more robust. That should be applicable without any risk.

Jul 25 2019, 1:59 AM · gnupg, Bug Report
dkg removed a task from rGb84feb0c82eb: agent: Do not place a trailing NUL byte on S-expression: T4652: avoid unnecessary trailing NUL byte in S-expressions.
Jul 25 2019, 1:58 AM
dkg removed a commit from T4652: avoid unnecessary trailing NUL byte in S-expressions: rGb84feb0c82eb: agent: Do not place a trailing NUL byte on S-expression.
Jul 25 2019, 1:58 AM · gnupg, Bug Report
dkg committed rGfdd1567743cc: gpg,gpgsm: Handle pkdecrypt responses with or without NUL terminators (authored by dkg).
gpg,gpgsm: Handle pkdecrypt responses with or without NUL terminators
Jul 25 2019, 1:57 AM
dkg committed rGefffd9907b75: agent: Do not place a trailing NUL byte on S-expressions (authored by dkg).
agent: Do not place a trailing NUL byte on S-expressions
Jul 25 2019, 1:57 AM

Jul 24 2019

dkg removed a task from rG1ae16838660a: agent: Do not place a trailing NUL byte on S-expression: T4652: avoid unnecessary trailing NUL byte in S-expressions.
Jul 24 2019, 6:24 AM
dkg added a task to rGb84feb0c82eb: agent: Do not place a trailing NUL byte on S-expression: T4652: avoid unnecessary trailing NUL byte in S-expressions.
Jul 24 2019, 6:24 AM
dkg edited commits for T4652: avoid unnecessary trailing NUL byte in S-expressions, added: rGb84feb0c82eb: agent: Do not place a trailing NUL byte on S-expression; removed rG1ae16838660a: agent: Do not place a trailing NUL byte on S-expression.
Jul 24 2019, 6:24 AM · gnupg, Bug Report
dkg added a comment to T4652: avoid unnecessary trailing NUL byte in S-expressions.

I've just posted rGb84feb0c82eb to the dkg-fix-T4652 branch, which solves the failure problems by making agent_pkdecrypt and gpgsm_agent_pkdecrypt more robust.

Jul 24 2019, 6:24 AM · gnupg, Bug Report