OpenPGPProject
ActivePublic

Members

  • This project does not have any members.

Recent Activity

Nov 8 2018

Valodim added a comment to T4235: GnuPG doesn't respect key flags when decrypting.

Fair enough. Let's wait and see what others think.

Nov 8 2018, 1:24 PM · Not A Bug, OpenPGP, gnupg
werner closed T4235: GnuPG doesn't respect key flags when decrypting as Resolved.

Also consider that it is possible to change the key usage flags. Thus it will never be clear whether one has a fixed or unfixed public key. I'd like to close this bug because it is currently also discussed in the IETF WG.

Nov 8 2018, 1:10 PM · Not A Bug, OpenPGP, gnupg

Nov 5 2018

werner closed T3773: private subkeys are never deleted on non-master instances as Invalid.

No info received.

Nov 5 2018, 10:12 AM · Info Needed, OpenPGP, gnupg (gpg22), Bug Report

Oct 30 2018

stm added a comment to T4235: GnuPG doesn't respect key flags when decrypting.

There is another argument for respecting the usage flags: it trims the admissible key space, if key ID in the PKESK packet is zero ('wild card') and thus all private keys have to be considered for decryption.

Oct 30 2018, 9:48 PM · Not A Bug, OpenPGP, gnupg

Oct 29 2018

aheinecke added a comment to T4235: GnuPG doesn't respect key flags when decrypting.

I disagree, and you don't have to try to convince me, the decision is with werner. I just want to give my opinion:
Bug compatibility is nothing esoteric or bad especially for a general purpose backend tool like gnupg. Being open to accepting broken input is a good thing because it will mean that we can get people out of a "broken tool vendor lock in".

Oct 29 2018, 8:29 PM · Not A Bug, OpenPGP, gnupg
dkg added a comment to T4235: GnuPG doesn't respect key flags when decrypting.

i agree with @Valodim that it would be better to not have a warning at all for an attempt to decrypt from secret key whose public key has never been marked as valid for encryption. A strict failure there (as with a strict failure for lack of mdc) is a better scenario than a warning. If the user controls the secret key and they decide they want to be able to decrypt with it, they should be able to mark it as decryption-capable (if that's really what they want) and retry. But this is an action only for experts.

Oct 29 2018, 8:04 PM · Not A Bug, OpenPGP, gnupg
Valodim added a comment to T4235: GnuPG doesn't respect key flags when decrypting.

The same *cannot* be said for a subkey that is marked specifically for certification or signing, and not for decryption.

Oct 29 2018, 7:57 PM · Not A Bug, OpenPGP, gnupg
dkg added a comment to T4235: GnuPG doesn't respect key flags when decrypting.

I understand the real world requirement for decrypting messages that have been encrypted to a revoked or expired key.

Oct 29 2018, 7:43 PM · Not A Bug, OpenPGP, gnupg
werner triaged T4235: GnuPG doesn't respect key flags when decrypting as Low priority.

I don't see a problem. If you have the private key you can and will use it. I guess your concern is an oracle?

Oct 29 2018, 8:47 AM · Not A Bug, OpenPGP, gnupg

Oct 18 2018

adam added a comment to T4189: GngOL cannot decrypt title nor sender; How to disable certificate selection dialog?.

Dear aheinecke,

Oct 18 2018, 1:04 PM · kleopatra, gnupg, Enigmail, OpenPGP, gpgol
aheinecke closed T4189: GngOL cannot decrypt title nor sender; How to disable certificate selection dialog? as Invalid.

Hi Adam,

Oct 18 2018, 12:26 PM · kleopatra, gnupg, Enigmail, OpenPGP, gpgol

Oct 17 2018

adam created T4189: GngOL cannot decrypt title nor sender; How to disable certificate selection dialog? in the S1 Public space.
Oct 17 2018, 11:49 AM · kleopatra, gnupg, Enigmail, OpenPGP, gpgol

Jun 24 2018

werner triaged T4042: RFC 4880 compliance as Normal priority.
Jun 24 2018, 9:50 PM · OpenPGP, gnupg

Feb 22 2018

werner triaged T3773: private subkeys are never deleted on non-master instances as Low priority.
Feb 22 2018, 10:33 AM · Info Needed, OpenPGP, gnupg (gpg22), Bug Report

Feb 6 2018

werner added projects to T3773: private subkeys are never deleted on non-master instances: gnupg (gpg22), OpenPGP.
Feb 6 2018, 6:30 PM · Info Needed, OpenPGP, gnupg (gpg22), Bug Report

Nov 20 2017

werner triaged T3513: Change of trust of new uid not immediately reflected in user interface as Normal priority.

To compute the key validity (trust) more information may be needed and we can only do that after the changes have been saved. Further, no-auto-chec-trustdb will anyway delay that computation until "gpg --check-trustdb" is run (e.g. by a cron job).

Nov 20 2017, 8:44 AM · OpenPGP, gnupg (gpg23), Feature Request

Sep 8 2017

attila.lendvai added a comment to T3391: cannot import subkey that was once marked to be on a card.

success, thank you for the help!

Sep 8 2017, 1:06 PM · gnupg, OpenPGP, Bug Report
gniibe claimed T3391: cannot import subkey that was once marked to be on a card.
Sep 8 2017, 12:48 PM · gnupg, OpenPGP, Bug Report
gniibe added a comment to T3391: cannot import subkey that was once marked to be on a card.

In GnuPG 2.1, secret keys are under control of gpg-agent. Currently, it is not deleted by gpg frontend.
Please run:

$ gpg -K --with-keygrip
Sep 8 2017, 12:48 PM · gnupg, OpenPGP, Bug Report
attila.lendvai updated the task description for T3391: cannot import subkey that was once marked to be on a card.
Sep 8 2017, 12:12 PM · gnupg, OpenPGP, Bug Report

Sep 7 2017

attila.lendvai created T3391: cannot import subkey that was once marked to be on a card.
Sep 7 2017, 4:00 PM · gnupg, OpenPGP, Bug Report

Aug 27 2017

werner triaged T3373: Unusual incompatibility with PGP6 PhotoID's as Low priority.

IIRC, rfc2440 did not forbid partial length encoding for key-material so gpg could use that. rfc4880 limits partial length encoding to non-key-material which causes this error message.

Aug 27 2017, 9:04 PM · OpenPGP, gnupg, Bug Report

Aug 26 2017

Kelbom68 added a comment to T3372: Long preference lists resetting each other.

Well, I'd expect gpg not to alter my digest/compression preferences when changing my cipher preferences and vice versa. So if a user's going to have to lose his previously set preferences for a key in this manner because that's the only reasonably viable way of maintaining backwards compatibility, I think it would be appropriate to let him know beforehand and also suggest that he set it all up at once (as I've so described above) so that nothing is lost in the process.

Aug 26 2017, 7:39 PM · OpenPGP, gnupg, Bug Report
werner triaged T3372: Long preference lists resetting each other as Normal priority.

The way the setpref command works is implementation specific and thus the OpenPGP standard is irrelevant here
.
Are you requesting a change in the behaviour of the setpref command? That would not be easy to implement for backward compatibility.

Aug 26 2017, 6:22 PM · OpenPGP, gnupg, Bug Report

Jul 27 2017

werner added a project to T2313: gpg --import of secret keys prompts for passwords in 2.1: S/MIME.

Well, iff we implement that for gpg we also need to implement it for gpgsm.

Jul 27 2017, 9:41 AM · S/MIME, Feature Request, Stalled, gnupg, OpenPGP
werner edited projects for T2313: gpg --import of secret keys prompts for passwords in 2.1, added: Feature Request; removed Bug Report.
Jul 27 2017, 9:40 AM · S/MIME, Feature Request, Stalled, gnupg, OpenPGP

Jul 24 2017

marcus added a project to T2313: gpg --import of secret keys prompts for passwords in 2.1: Stalled.

A decision must be made what the desired behaviour should be.

Jul 24 2017, 5:25 PM · S/MIME, Feature Request, Stalled, gnupg, OpenPGP

Jun 22 2017

thomas added a comment to T1291: signatures to OpenPGP keys no longer expire by default if the signed key expires.
  • marcus (Marcus Brinkmann) <noreply@dev.gnupg.org> [20170622 16:41]:
So, the default change 7y ago and the world didn't end. Closing this.
Jun 22 2017, 4:52 PM · gnupg, OpenPGP, Feature Request
marcus closed T1291: signatures to OpenPGP keys no longer expire by default if the signed key expires as Wontfix.

So, the default change 7y ago and the world didn't end. Closing this.

Jun 22 2017, 4:41 PM · gnupg, OpenPGP, Feature Request

May 17 2017

srgblnchtrn added a watcher for OpenPGP: srgblnchtrn.
May 17 2017, 9:20 AM

Apr 7 2017

gp_ast added a watcher for OpenPGP: gp_ast.
Apr 7 2017, 2:35 PM

Mar 30 2017

admin created OpenPGP.
Mar 30 2017, 6:42 PM

Feb 14 2017

aheinecke closed T2324: gpg --batch --export-secret-key fails (requires user interaction) if key has no passphrase as Resolved.
Feb 14 2017, 1:43 PM · gnupg, OpenPGP, Bug Report
aheinecke added a comment to T2324: gpg --batch --export-secret-key fails (requires user interaction) if key has no passphrase.

Tested this again with 2.1.18 and it works now as expected. Export secret key
just exports a key if it has no passphrase. So I think this issue can be marked
as resolved.

Feb 14 2017, 1:43 PM · gnupg, OpenPGP, Bug Report

Sep 7 2016

werner added a comment to T2241: Encrypt to all encryption subkeys.

It is a hack in OpenKeychain to allow the use of several devices. Frankly, I am
not sure whether this is really a good idea: The security is limited by the key
for the least secure device.

Sep 7 2016, 11:20 AM · gnupg, OpenPGP, Feature Request

Sep 6 2016

dkg added a comment to T2324: gpg --batch --export-secret-key fails (requires user interaction) if key has no passphrase.

So i've tested this locally with:

    export GNUPGHOME=$(mktemp -d)
    gpg --quick-gen-key 'test user <test@example.org>'
    gpg --armor --export-secret-key 'test user <test@example.org>'

(choosing no passphrase during the prompts that come up during the quick-gen-key
step). The final export step works fine.

Can you show what steps you're taking that fail for you, Andre?

Sep 6 2016, 5:08 AM · gnupg, OpenPGP, Bug Report

Sep 5 2016

aheinecke changed Version from 2.1.11 to 2.1.15 on T2324: gpg --batch --export-secret-key fails (requires user interaction) if key has no passphrase.
Sep 5 2016, 2:40 PM · gnupg, OpenPGP, Bug Report
aheinecke added a comment to T2324: gpg --batch --export-secret-key fails (requires user interaction) if key has no passphrase.

I'm using latest master and I still can't export a secret key without passphrase.

And Justus also has not closed this bug or wrote that he commited something
more. So I think the 2.1.13 announcement was mistaken and this problem still
exists. (Or am I missing some option / need a different pinentry mode?)

Sep 5 2016, 2:40 PM · gnupg, OpenPGP, Bug Report

Jul 14 2016

werner removed a project from T2402: New option to encrypt with a key taken from a file: Unreleased.
Jul 14 2016, 7:13 PM · gnupg, OpenPGP, Feature Request

Jul 6 2016

werner added a project to T2402: New option to encrypt with a key taken from a file: Unreleased.
Jul 6 2016, 4:10 PM · gnupg, OpenPGP, Feature Request
werner added a comment to T2402: New option to encrypt with a key taken from a file.

We got it for 2.1: -f or --recipient-file

Jul 6 2016, 4:10 PM · gnupg, OpenPGP, Feature Request
werner closed T2402: New option to encrypt with a key taken from a file as Resolved.
Jul 6 2016, 4:10 PM · gnupg, OpenPGP, Feature Request

Jun 29 2016

werner added projects to T2402: New option to encrypt with a key taken from a file: Feature Request, OpenPGP, gnupg.
Jun 29 2016, 12:40 PM · gnupg, OpenPGP, Feature Request

Jun 27 2016

bernhard added a comment to T2324: gpg --batch --export-secret-key fails (requires user interaction) if key has no passphrase.

Hi,
the 2.1.13 announcement has
"""

  • gpg: Allow export of non-passphrase protected secret keys.

"""
(from https://lists.gnupg.org/pipermail/gnupg-announce/2016q2/000390.html)
so this defect may be fixed with 2.1.13 I guess, cool!
Probably only need a test to confirm?

Jun 27 2016, 5:37 PM · gnupg, OpenPGP, Bug Report

Jun 6 2016

aheinecke added a comment to T2380: Auto-refresh key if it is close to its expiration date..

Replacing revoked keys made me wonder if we actually need an auto-refresh key.
If we try to return one valid key with --locate-keys wouldn't it make more sense
semantically if we use the auto-key-locate mechanisms with locate-keys when a
key is expired in the local store?

This would also work better for revoked keys where a Parcimonie style auto
refresh would pick up the revocation and locate-keys would then look for a new key.

Jun 6 2016, 3:56 PM · gnupg, OpenPGP, Feature Request
werner added projects to T2380: Auto-refresh key if it is close to its expiration date.: Feature Request, OpenPGP, gnupg.
Jun 6 2016, 11:40 AM · gnupg, OpenPGP, Feature Request

Jun 1 2016

bernhard added a comment to T2324: gpg --batch --export-secret-key fails (requires user interaction) if key has no passphrase.

I can confirm one defect with 2.1.11:
The ability to export a secret key without passphrase available in gnupg2.0
is gone. My use case is to write a testcase that automatically imports the key.

Jun 1 2016, 3:27 PM · gnupg, OpenPGP, Bug Report

May 27 2016

justus added a comment to T2324: gpg --batch --export-secret-key fails (requires user interaction) if key has no passphrase.

I did not work on this other than what I merged. What I did is to enhance our
fake pinentry program to allow it to supply different passphrases, make it write
a log so that we can quantify the pinentry interaction in test cases, and to add
an export test documenting the status quo.

May 27 2016, 6:02 PM · gnupg, OpenPGP, Bug Report
werner added a comment to T2324: gpg --batch --export-secret-key fails (requires user interaction) if key has no passphrase.

The question at hand is whether dkg's patch or Justus work is the way to go. I
have not yet reviewed dkg's patch, though.

May 27 2016, 11:42 AM · gnupg, OpenPGP, Bug Report
werner added a comment to T2324: gpg --batch --export-secret-key fails (requires user interaction) if key has no passphrase.

dgk: You are right that Pinentry may be used even with --batch. In fact gpgme
uses --batch and a Pinentry is used nevertheless.

Right, there are no technical means right now to inhibit the export of private
keys. However, it would be easy to add this by not allowing gpg-agent to tell
the client the key used to encrypt the import/export command of keys.

A user migyt have used no passphrase for a key in the believe that an
unprotected key can't be exported.

May 27 2016, 11:41 AM · gnupg, OpenPGP, Bug Report