gnupg (gpg23)Milestone
ActivePublic

Members

  • This project does not have any members.

Watchers

  • This project does not have any watchers.

Recent Activity

Fri, Jan 11

beckda created T4320: tar archive encryption failed with japanese characters.
Fri, Jan 11, 9:00 AM · gpg4win, kleopatra, Bug Report

Dec 12 2018

gniibe merged task T3529: Connection limit for gpg-agent into T4255: gpg-agent: "<gcrypt> Cannot allocate memory" with 10 threads decrypting OpenPGP.
Dec 12 2018, 7:16 AM · Feature Request, gnupg (gpg23), gpgagent

Nov 9 2018

jukivili added a commit to T3786: Unexpectedly slow decryption for AEAD (and CFB): rG5d6c080522e1: g10/decrypt-data: use iobuf_read for higher performance.
Nov 9 2018, 5:07 PM · gnupg (gpg23), Bug Report

Nov 8 2018

werner created T4246: GnuPG master does not allow decryption with bad usage flags (regression).
Nov 8 2018, 1:27 PM · Bug Report, gnupg (gpg23)

Nov 5 2018

werner edited projects for T3730: Add support to HTTP Basic Auth for Keyservers, added: gnupg (gpg23); removed gnupg (gpg22).
Nov 5 2018, 10:17 AM · gnupg (gpg23), Feature Request
werner edited projects for T3753: Bad self-signatures and missing subkey usage flags when creating ECDSA/Ed25519 keys in batch mode, added: gnupg (gpg23); removed gnupg (gpg22).
Nov 5 2018, 10:16 AM · gnupg (gpg23), Bug Report
werner edited projects for T3108: gpgconf lists the wrong extra socket path when a path is explicitly configured in gpg-agent.conf, added: gnupg (gpg23); removed gnupg (gpg22).
Nov 5 2018, 9:38 AM · gnupg (gpg23), gpgagent
werner edited projects for T3101: GnuPG 2.2 cannot import secret keys from 1.4/2.0's secring.gpg directly (if it is expired by original expiration date), added: gnupg (gpg23); removed gnupg (gpg22).
Nov 5 2018, 9:37 AM · gnupg (gpg23), Bug Report
werner edited projects for T3278: explicit key expiration date/time is interpreted as UTC, is echoed back using local time, confusion ensues, added: gnupg (gpg23); removed gnupg (gpg22).
Nov 5 2018, 9:36 AM · gnupg (gpg23), Documentation, Bug Report
werner edited projects for T3237: gnupg complies to CO_DE_VS when generating keys non-interactively only by accident, added: gnupg (gpg23); removed gnupg (gpg22).
Nov 5 2018, 9:34 AM · gnupg (gpg23)

Oct 29 2018

werner triaged T4154: allow setting passphrase from an environment variable as Low priority.
Oct 29 2018, 9:42 AM · Feature Request, gnupg (gpg23)

Oct 7 2018

dkg added a comment to T4154: allow setting passphrase from an environment variable.

ok, feel free to close this ticket then. It's disappointing that there
seems to be no sane, simple, private multi-channel communication
mechanism avaiable cross-platform that GnuPG can rely on.

Oct 7 2018, 6:45 AM · Feature Request, gnupg (gpg23)

Oct 1 2018

werner added a comment to T3398: fingerprint-based import screener is no defense against malice.

I have this use case: A card based encryption key is used as a subkey on one of my keys but also on another key of mine. The reason for this can be that I want to have separate keys (with different fingerprints) for two user ids but still use the same card for decryption. Sure it is possible to figure out that the user ids belong together but it is not obvious on first sight. Another use case is a role account with a shared subkey with only one administering the primary key.

Oct 1 2018, 8:39 AM · gnupg (gpg23), Feature Request

Sep 28 2018

dkg added a comment to T3398: fingerprint-based import screener is no defense against malice.

This was additionally reported as https://bugs.debian.org/909755 -- it would be great to get a clear statement from the GnuPG project about handling the curated keyring use case.

Sep 28 2018, 5:45 PM · gnupg (gpg23), Feature Request

Sep 24 2018

werner added a comment to T4154: allow setting passphrase from an environment variable.

Maybe not on Linux but the environment is visible from other processes in the same way as the command line. So I don't see why we should add yet more clumsy passphrase workarounds to gpg. We already have PINENTRY_USER_DATA which can fulfill the same task.

Sep 24 2018, 9:06 AM · Feature Request, gnupg (gpg23)

Sep 23 2018

dkg added a comment to T4154: allow setting passphrase from an environment variable.

i note that my patch doesn't include an addition to the test suite, which it probably should, though i'm not fluent in gpgscm. if someone could update it to include a test, i'd appreciate that, and would probably learn from the commit. I imagine the test would do something like:

Sep 23 2018, 9:31 PM · Feature Request, gnupg (gpg23)
dkg added a comment to T4154: allow setting passphrase from an environment variable.

I tried to push commit 07c19981da0607dc442fadc4079b1d71fbef8f83 to branch dkg/passphrase-env on playfair, but i got this complaint:

Sep 23 2018, 8:36 PM · Feature Request, gnupg (gpg23)
dkg created T4154: allow setting passphrase from an environment variable in the S1 Public space.
Sep 23 2018, 8:32 PM · Feature Request, gnupg (gpg23)

Sep 7 2018

gniibe added a comment to T2836: dirmngr: wakes up periodically.

Patch 0001 applied to master.

Sep 7 2018, 7:30 AM · gnupg, gnupg (gpg23), Bug Report, dirmngr
gniibe added a commit to T2836: dirmngr: wakes up periodically: rG04b56eff118e: dirmngr: hkp: Avoid potential race condition when some hosts die..
Sep 7 2018, 7:30 AM · gnupg, gnupg (gpg23), Bug Report, dirmngr

Aug 30 2018

stm added a comment to T4108: Support for verifying OpenPGP standalone and timestamp signatures.

BTW: For TSA keys an additional key (usage) flag ("This key may be used for time-stamping") in RFC 4880bis would be nice. What do you think?

Aug 30 2018, 8:44 PM · gnupg (gpg23), Feature Request
stm added a comment to T4108: Support for verifying OpenPGP standalone and timestamp signatures.

According to RFC 3628 there are two additional conditions to consider:

A timestamp or a time mark (which is an audit record kept in a secure
audit trail from a trusted third party) applied to a digital
signature value proves that the digital signature was created before
the date included in the time-stamp or time mark.
Aug 30 2018, 6:55 AM · gnupg (gpg23), Feature Request

Aug 28 2018

werner added a comment to T4108: Support for verifying OpenPGP standalone and timestamp signatures.

The question is now to model the API for this. For 0x02 it seems to be pretty clear: We assume it is a detached signature on a zero length file and make sure that no signed file is given.

Aug 28 2018, 5:16 PM · gnupg (gpg23), Feature Request
gniibe closed T3056: gpgme-1.8.0: test failures on NetBSD as Resolved.
Aug 28 2018, 4:20 AM · gpgagent, gnupg (gpg23), gpgme

Aug 27 2018

stm added a comment to T4108: Support for verifying OpenPGP standalone and timestamp signatures.

Attached is a timestamp signature created with the test key (alfa, alpha, alice) from tests/openpgp.

Aug 27 2018, 9:30 PM · gnupg (gpg23), Feature Request
gniibe changed the status of T3119: gpg: Improve public key decryption from Open to Testing.
Aug 27 2018, 9:32 AM · gnupg (gpg23)
gniibe added a comment to T3119: gpg: Improve public key decryption.

In master, commit from rGce2f71760155: g10: Change decryption key selection for public key encryption. until rG84cc55880a58: g10: Prefer to available card keys for decryption. fixed this.

Aug 27 2018, 9:32 AM · gnupg (gpg23)
gniibe added a comment to T3056: gpgme-1.8.0: test failures on NetBSD.

I think it's good to close this as "resolved", since many fixes have been done, and I don't have remaining issue.
@wiz Please open another ticket for your next try.

Aug 27 2018, 6:53 AM · gpgagent, gnupg (gpg23), gpgme

Aug 26 2018

werner added a comment to T4108: Support for verifying OpenPGP standalone and timestamp signatures.

Okay, can you please provide sample data for the test suite? Best using one of the existing keys but adding another one won't harm either.

Aug 26 2018, 8:29 AM · gnupg (gpg23), Feature Request

Aug 25 2018

stm added a comment to T4108: Support for verifying OpenPGP standalone and timestamp signatures.

DKGPG will contain programs to generate such signatures in its next release. Thus it would be nice, if those signatures can be verified by GnuPG as one of the most widespread OpenPGP implementations.

Aug 25 2018, 9:42 AM · gnupg (gpg23), Feature Request

Aug 24 2018

werner moved T3056: gpgme-1.8.0: test failures on NetBSD from Backlog to For next release on the gpgme board.
Aug 24 2018, 5:57 PM · gpgagent, gnupg (gpg23), gpgme
werner added a comment to T3056: gpgme-1.8.0: test failures on NetBSD.

What are we going to do with this report? The last comment is 6 months old; can we change from testing to resolved or do we need to wait for a gpgme release?

Aug 24 2018, 5:56 PM · gpgagent, gnupg (gpg23), gpgme
werner added a project to T4108: Support for verifying OpenPGP standalone and timestamp signatures: gnupg (gpg23).

What are your use cases?

Aug 24 2018, 5:31 PM · gnupg (gpg23), Feature Request

Apr 19 2018

werner triaged T3921: Make adding an arbitrary (sub)key easier as Low priority.
Apr 19 2018, 5:24 PM · gnupg (gpg23), Feature Request
werner created T3921: Make adding an arbitrary (sub)key easier.
Apr 19 2018, 5:24 PM · gnupg (gpg23), Feature Request

Apr 17 2018

werner triaged T3786: Unexpectedly slow decryption for AEAD (and CFB) as High priority.
Apr 17 2018, 8:40 PM · gnupg (gpg23), Bug Report
werner triaged T3801: gpg --import cannot display user ID as High priority.
Apr 17 2018, 8:26 PM · gnupg (gpg23)

Apr 13 2018

aheinecke created T3903: Kleopatra: Use the term password instead of passphrase.
Apr 13 2018, 1:58 PM · FAQ, Documentation, gnupg (gpg23)
werner created T3902: Use the term password instead of passphrase.
Apr 13 2018, 1:55 PM · FAQ, Documentation, gnupg (gpg23)

Apr 9 2018

gniibe closed T3299: scd: support key algorithm attribute change UI as Resolved.
Apr 9 2018, 7:27 AM · gnupg (gpg23)
gniibe added a comment to T3299: scd: support key algorithm attribute change UI.

Fixed for forthcoming 2.2.6. Because of T3781: ECC encryption key on-card generation broken.
rG820380335a20: g10: Add "key-attr" command for --card-edit.

Apr 9 2018, 7:27 AM · gnupg (gpg23)

Feb 26 2018

gniibe closed T3757: Problem building latest master on macOS: unknown identifier LOCAL_PEERUID in command-ssh.c as Resolved.
Feb 26 2018, 7:59 AM · gpgagent, gnupg (gpg23), MacOS, Bug Report

Feb 20 2018

werner claimed T3801: gpg --import cannot display user ID.

Thanks for tracking this down. I'll fix.

Feb 20 2018, 5:04 PM · gnupg (gpg23)
gouttegd added a comment to T3801: gpg --import cannot display user ID.

Bissecting between gnupg-2.3-base and master pinpointed commit ecbbafb88d920e713439b6b1b8e1b41a6f8d0e38 as the origin of the bug. This commit changed MAX_FINGERPRINT_LEN from 20 to 32, but the get_user_id_byfpr function in g10/getkey.c still assumes the old value.

Feb 20 2018, 4:43 PM · gnupg (gpg23)
werner edited projects for T3801: gpg --import cannot display user ID, added: gnupg (gpg23); removed gnupg.
Feb 20 2018, 4:22 PM · gnupg (gpg23)

Feb 16 2018

gniibe added a comment to T3056: gpgme-1.8.0: test failures on NetBSD.

The error of testQuickUID is strange. In the test, it adds a UID and checks number of UIDs (3 + 1 = 4).
It is not reproducible for me (Debian with Qt 5.9.2, NetBSD 7.0.2 with Qt 5.5.1), gnupg 2.2.x from the repo.

Feb 16 2018, 12:45 AM · gpgagent, gnupg (gpg23), gpgme

Feb 15 2018

werner added a comment to T3056: gpgme-1.8.0: test failures on NetBSD.

(automake should flag non-portable Makefile features - after all it is there to avoid gmake features)

Feb 15 2018, 11:52 AM · gpgagent, gnupg (gpg23), gpgme
wiz added a comment to T3056: gpgme-1.8.0: test failures on NetBSD.

Thank you very much! This is working quite well now.

Feb 15 2018, 10:57 AM · gpgagent, gnupg (gpg23), gpgme
gniibe added a comment to T3056: gpgme-1.8.0: test failures on NetBSD.

I believe that all BSD Makefile issues has been fixed (except python-tar-gz distribution thing for maintainer).
Please test again.

Feb 15 2018, 5:07 AM · gpgagent, gnupg (gpg23), gpgme
gniibe added a comment to T3056: gpgme-1.8.0: test failures on NetBSD.

I located the problem. It's Makefile portability issue and it is fixed in: rMb5ec21b9baf0: tests: Makefile portability., rMba6e610baa13: tests: More Makefile portability., and rM3224d7f0ea83: tests: Fix previous commit
It was not your final invocation of "make check" (GNU or BSD), but the one before ("make all" by BSD make) which imported keys for tests.
The "export" directive doesn't work on BSD.

Feb 15 2018, 3:40 AM · gpgagent, gnupg (gpg23), gpgme