g10code (gnupg-2.2)Milestone
ArchivedPublic

Watchers

  • This project does not have any watchers.

Details

Description

Required for the GnuPG 2.2.0 release

Recent Activity

Mar 15 2018

aheinecke archived g10code (gnupg-2.2).
Mar 15 2018, 6:45 PM

Oct 22 2017

jcross updated the task description for T3463: UI says “Secret key is available.” in gpg when it is not.
Oct 22 2017, 3:54 PM · Bug Report, gnupg (gpg22)
jcross created T3463: UI says “Secret key is available.” in gpg when it is not in the S1 Public space.
Oct 22 2017, 3:45 PM · Bug Report, gnupg (gpg22)

Sep 1 2017

t8m created T3380: Use exponential backoff when spawning agent and dirmngr in the S1 Public space.
Sep 1 2017, 9:51 AM · Feature Request, gnupg

Aug 23 2017

aheinecke added a commit to T3364: Pinentry strings no longer translated on windows: rG615881130493: agent: Fix string translation for Windows.
Aug 23 2017, 11:15 AM · g10code (gnupg-2.2), gpg4win
aheinecke closed T3364: Pinentry strings no longer translated on windows as Resolved.

ENABLE_NLS is not defined as it should be but we still have to define L_ in that case if simple_gettext is used to have some gettext. This was fixed by 6158811304937b592601ef30c29c5a5cdbaa88ea

Aug 23 2017, 11:14 AM · g10code (gnupg-2.2), gpg4win
aheinecke created T3364: Pinentry strings no longer translated on windows.
Aug 23 2017, 10:48 AM · g10code (gnupg-2.2), gpg4win

Aug 7 2017

werner closed T3324: Activate Web Key Discovery by default as Resolved.
Aug 7 2017, 1:16 PM · g10code (gnupg-2.2)

Aug 4 2017

werner added a comment to T3324: Activate Web Key Discovery by default.

auto-key-locate now defaults to "local,wkd" and --auto-key-retrieve is also the default.

Aug 4 2017, 10:16 PM · g10code (gnupg-2.2)
werner added a commit to T3324: Activate Web Key Discovery by default: rG7e1fe791d188: gpg: Default to --auto-key-locate "local,wkd" and --auto-key-retrieve..
Aug 4 2017, 10:14 PM · g10code (gnupg-2.2)

Aug 3 2017

werner added a comment to T3324: Activate Web Key Discovery by default.

Yes, any auto-key-locate entry should disable the defaults.

Aug 3 2017, 7:54 PM · g10code (gnupg-2.2)

Aug 2 2017

aheinecke added a comment to T3324: Activate Web Key Discovery by default.

IMO for now we should not add DANE as this has been published for a while and we don't see widespread adoption. To avoid additional delays I would keep it disabled by default for now. But you know the pros / cons there better then me.

Aug 2 2017, 1:51 PM · g10code (gnupg-2.2)
werner raised the priority of T3324: Activate Web Key Discovery by default from Normal to High.

So your suggestion is that

auto-key-retrieve
auto-key-locate local
auto-key-locate wkd
auto-key-locate dane

shall be the new default unless --disable-dirmngr is also used?

Aug 2 2017, 12:37 PM · g10code (gnupg-2.2)
aheinecke created T3324: Activate Web Key Discovery by default.
Aug 2 2017, 11:34 AM · g10code (gnupg-2.2)

Jul 31 2017

werner removed a project from T3318: Keyserver access on Windows broken (Resource Temporary Unavailable): In Progress.
Jul 31 2017, 5:12 PM · g10code (gnupg-2.2), gpg4win
werner closed T3318: Keyserver access on Windows broken (Resource Temporary Unavailable) as Resolved.

A new installer is now available:

Jul 31 2017, 5:10 PM · g10code (gnupg-2.2), gpg4win
werner added a project to T3318: Keyserver access on Windows broken (Resource Temporary Unavailable): In Progress.
Jul 31 2017, 4:26 PM · g10code (gnupg-2.2), gpg4win
werner added a comment to T3318: Keyserver access on Windows broken (Resource Temporary Unavailable).

Patched installer is better. This is also a good test on whether the build works with custom patches.

Jul 31 2017, 2:10 PM · g10code (gnupg-2.2), gpg4win
aheinecke added a comment to T3318: Keyserver access on Windows broken (Resource Temporary Unavailable).

Or you publish some gnupg-2.1.23-beta3 or so. Would also be ok imo.

Jul 31 2017, 2:02 PM · g10code (gnupg-2.2), gpg4win
aheinecke added a comment to T3318: Keyserver access on Windows broken (Resource Temporary Unavailable).

I'd say a patched installer with a different date. This is how I would have handled this in the Gpg4win 2.x times.

Jul 31 2017, 1:58 PM · g10code (gnupg-2.2), gpg4win
werner added a comment to T3318: Keyserver access on Windows broken (Resource Temporary Unavailable).

How, shall we build just a new patched installer or do a full new release?

Jul 31 2017, 1:19 PM · g10code (gnupg-2.2), gpg4win
werner closed T3319: Fix connect with timeout on Windows, a subtask of T3318: Keyserver access on Windows broken (Resource Temporary Unavailable), as Resolved.
Jul 31 2017, 1:18 PM · g10code (gnupg-2.2), gpg4win
werner closed T3319: Fix connect with timeout on Windows as Resolved.

That was an easy one.

Jul 31 2017, 1:18 PM · g10code (gnupg-2.2), gpg4win
werner added a commit to T3319: Fix connect with timeout on Windows: rG482fd5758c1b: dirmngr,w32: Fix http connection timeout problem..
Jul 31 2017, 1:18 PM · g10code (gnupg-2.2), gpg4win
werner created T3319: Fix connect with timeout on Windows.
Jul 31 2017, 9:58 AM · g10code (gnupg-2.2), gpg4win
werner added a comment to T3318: Keyserver access on Windows broken (Resource Temporary Unavailable).

Workaround is to add

Jul 31 2017, 9:48 AM · g10code (gnupg-2.2), gpg4win
aheinecke added a comment to T3318: Keyserver access on Windows broken (Resource Temporary Unavailable).

Sorry. Git log had some ...skipping which i overlooked instead of 3419a339d9c4e800bf30e9021e05982d8c1021c1 the actual one is 9b43220b8ad1a5c1cd51de3bbfff7ccbcc3fa877

Jul 31 2017, 9:16 AM · g10code (gnupg-2.2), gpg4win
aheinecke reassigned T3318: Keyserver access on Windows broken (Resource Temporary Unavailable) from aheinecke to werner.

It's either rev: 5b9025cfa1f9b1c67ddf2f6bf87d863e780cf157 which does not compile by itself or 3419a339d9c4e800bf30e9021e05982d8c1021c1

Jul 31 2017, 9:11 AM · g10code (gnupg-2.2), gpg4win
aheinecke lowered the priority of T3318: Keyserver access on Windows broken (Resource Temporary Unavailable) from Unbreak Now! to Needs Triage.

Uhm. I can't reproduce this with a dirmngr built on my development system.

Jul 31 2017, 8:41 AM · g10code (gnupg-2.2), gpg4win
aheinecke created T3318: Keyserver access on Windows broken (Resource Temporary Unavailable).
Jul 31 2017, 8:34 AM · g10code (gnupg-2.2), gpg4win

Jul 28 2017

werner closed T3266: Checksum Errors and Assertions when working with a specific homedir as Resolved.

That real bug is not a bug but a wrong error message. Due to the use of OCB we catch passphrase by means of that AEAD mode and not by looking at the cleartext. That resulted in a wrong error message. Fixed to return Bad Passphrase instead.

Jul 28 2017, 12:04 PM · g10code (gnupg-2.2)
werner added a commit to T3266: Checksum Errors and Assertions when working with a specific homedir: rG5cf95157c5db: agent: For OCB key files return Bad Passprase instead of Checksum Error..
Jul 28 2017, 12:01 PM · g10code (gnupg-2.2)
werner added a commit to T3266: Checksum Errors and Assertions when working with a specific homedir: rG6496dc1f9d2a: gpg: Fix segv in get_best_pubkey_byname..
Jul 28 2017, 12:01 PM · g10code (gnupg-2.2)
werner added a comment to T3266: Checksum Errors and Assertions when working with a specific homedir.

Segv/ref-count error found. Now for the real bug ...

Jul 28 2017, 11:04 AM · g10code (gnupg-2.2)
aheinecke added a comment to T3266: Checksum Errors and Assertions when working with a specific homedir.

I tried to reproduce this through various scripts in variations of


but failed. So maybe interactive usage plays a role here or it was fixed.

Jul 28 2017, 9:22 AM · g10code (gnupg-2.2)

Jul 27 2017

werner added a comment to T3266: Checksum Errors and Assertions when working with a specific homedir.

Hmmm.

Jul 27 2017, 2:49 PM · g10code (gnupg-2.2)
werner claimed T3266: Checksum Errors and Assertions when working with a specific homedir.
Jul 27 2017, 2:47 PM · g10code (gnupg-2.2)
aheinecke added a comment to T3266: Checksum Errors and Assertions when working with a specific homedir.

From this I take it that the checksum error comes from gcrypt but is wrongly propagated as Pinentry error.

Jul 27 2017, 1:18 PM · g10code (gnupg-2.2)
aheinecke added a comment to T3266: Checksum Errors and Assertions when working with a specific homedir.

With the vsnfdhome attached to this report:

Jul 27 2017, 1:17 PM · g10code (gnupg-2.2)
werner added a comment to T3266: Checksum Errors and Assertions when working with a specific homedir.

I don't understand the GPG_ERR_CHECKSUM coming according to Justus' log from Pinentry. A likeley reason for that error is an OCB decrypt failure in Libgcrypt (e.g. extended protected key format) - but from Pinentry?

Jul 27 2017, 12:48 PM · g10code (gnupg-2.2)
aheinecke added a comment to T3266: Checksum Errors and Assertions when working with a specific homedir.

Maybe related: T3187

Jul 27 2017, 11:15 AM · g10code (gnupg-2.2)
aheinecke added a comment to T3266: Checksum Errors and Assertions when working with a specific homedir.

I'm in a checksum error scenario again.

Jul 27 2017, 11:14 AM · g10code (gnupg-2.2)
aheinecke added a parent task for T3266: Checksum Errors and Assertions when working with a specific homedir: T3307: de-vs compliance mode problems.
Jul 27 2017, 11:12 AM · g10code (gnupg-2.2)

Jul 11 2017

justus triaged T3266: Checksum Errors and Assertions when working with a specific homedir as Normal priority.

This is very odd indeed. Here is my guru log, it is the same as yours, but except of dying of the assertion, it just continues:

Jul 11 2017, 1:55 PM · g10code (gnupg-2.2)

Jul 10 2017

aheinecke added a comment to T3266: Checksum Errors and Assertions when working with a specific homedir.

Yes, signing failed: Bad Passphrase but that may be later.

Jul 10 2017, 3:10 PM · g10code (gnupg-2.2)
justus added a comment to T3266: Checksum Errors and Assertions when working with a specific homedir.

I only get checksum errors:

Jul 10 2017, 3:06 PM · g10code (gnupg-2.2)
aheinecke created T3266: Checksum Errors and Assertions when working with a specific homedir.
Jul 10 2017, 2:54 PM · g10code (gnupg-2.2)

Apr 7 2017

flokli merged task T2991: dirmngr unable to receive keys if only IPv6 DNS servers are set into T2990: dirmngr fails with IPv6 nameserver in resolv.conf.
Apr 7 2017, 5:59 PM · g10code (gnupg-2.2), Debian, Bug Report, gnupg, gnupg (gpg21), dirmngr

Mar 31 2017

werner edited Description on g10code (gnupg-2.2).
Mar 31 2017, 8:14 PM
werner added a project to T2991: dirmngr unable to receive keys if only IPv6 DNS servers are set: g10code (gnupg-2.2).
Mar 31 2017, 3:12 PM · g10code (gnupg-2.2), Debian, Bug Report, gnupg, gnupg (gpg21), dirmngr