Thanks. Will go into the next release.

I just fixed that in master. The limit is now 255 also for the loopback.

See also T2038 where the limit was raised from 100 to 255. It has not been raised for the loopback mode though.

A better way to to this is my modifying yat2m. I just did this.

FWIW, OpenPGP's S2K and PKCS's PBKDF2 are very similar and don't make a difference except that we have calibration code for S2K in gpg-agent.

I am not sure I understand your question. In any case you need to tell us whcih pinentry flavour you ar using (gpt, qt, curses, gnome, etc...

We have fixed a couple of bugs related to keyservers between 2.1.17 and the current .21.

What version of GnuPG are you using? Standard upstream or from a distribution?

We need to find out when this regression happened. Back when David implemented trust signatures he ran tests with the PGP folks to make sure our implementation are compatible. This is why I call this a regression.

That's fine. The 2.0 branch will reach EOL in 6 months and we will
probably only do a last maintenance release. No need to backport this
fix, though.

On Wed, 28 Jun 2017 15:47, noreply@dev.gnupg.org said:

What tests do you want to be done?

Given that we have no TESTING status, the only way I can handle this is by keeping the ticket open and add the TESTING flag. Closing a bug which has not been tested is a bad idea.

Please be so kind and explain in more detail what you did.

Fixed. Thanks.

https://files.gpg4win.org/Beta/current/

Here is the code:

I can't remember either. We should swicth back to mailing lists for such things.

Anyway we should not allow empty user ids.

ping

Well, can you then please fix it?

Any update on this?

FWIW, I ran a make check today and got several failed tests when using the extended key format. Checking out master to see whether this was caused by another patch I am working on, showed that it worked on master. Checking out my local branch again, then passed the test.

gpg-agent waits for a QUALITY inquiry via Assuan from the pjnentry and replies with an integer giving the percent value. A negative percent value requests "red" indication. The argument for the quality inquirement is the passphrase as already entered. The idea is that this inquiry is send after each keystroke.

1.4 has build fixes for NetBSD. Thus I _assume_ this bug has been fixed.

Justus, please apply the patches.

Unlikely

GpgOL has even been revamped 2 times since then.

According to my checkout this is at

werner@trithemius.gnupg.org:/cvs/gph

But that has long gone. I need to see where to find a backup of that repo.

No way to test on El Capitain anymore. It works on Sierra.

We now have a GPGME feature to list packets:

Libgcrypt 1.6 reaches EOL in 7 days, so we won't fix it.

With the new rndjent as used with libgcrypt 1.8 under Windows rhis can be claimed as finished.

Solution has been given: Use "gpg.conf-1" for gpg 1.4

I commited a change which should fix this on Linux

Thanks for testing.

Well, this is a regression due to us creating creating /run/user/gnupg/ socket directories now on the fly. Thus there is no more need to create non-default home directories via gpgconf. Now, gpg-agent watches the socket file and terminates itself as soon as the socket file vanishes. Before that change the socket for a non-default home directory was created in the homedir itself and thus removing the homedir also removed the socket file and in turn gpg-agent terminated itself.

Thanks for the reminder. Fixed.
Note that LIBASSUAN_LIBS is not needed because it is already part of t_common_ldadd.

This is such a large change that I feel uneasy to close the bug before we know that there are no regressions. This Means we need to wait whether the next release will break.

I used this workaround for the years I accessed my mail over ssh and emacsclient.

(ask Marcus or me for the last 4 digits).

Note that it depends on a gpg-agent configure option. Thus Neal and you may see a different thing.

No, the quality bar is required for pinentries which want to get in wide use. Even if the quality algorithm seems to be too trivial, it is required for external checks like gpg-check-pattern.

On Wed, 21 Jun 2017 12:02, noreply@dev.gnupg.org said:

On Tue, 20 Jun 2017 10:20, noreply@dev.gnupg.org said:

Contract will be signed next Thursday at noon

I can't find the string ' Generating a basic OpenPGP key for our unit test' in the GnuPG 2.1 source nor in the the 2.0 source. Thus it seems to be a modified version of GnuPG. I guess that is the 2.0.30 you mentioned. Please run

What is your operating system?