Please ask on a mailing list - this is a bug tracker and somehow expects bug descriptions.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Nov 12 2020
Sorry, I do not understand what kind of bug you are trying to report. it seems that you have a question about some software and you assume this is gpg4win. "invalid pocket" is however not an error any of our software emits.
BTW, the idea is to fade out support for gpg --card-status and --card-edit. Thus no new features there. New features shall only go into gpg-card.
Nov 11 2020
Released with GpgOL 2.4.6 ang gpg4win 3.1.12
This is in 3.1.12
3.1.12 was released on 2020-07-24.
Nov 10 2020
Works for me. Also with a gpg.conf-2 file. Do you use a /etc/gnupg/gpg.conf ?
Nov 9 2020
I reconsidered this. Suppressing such messages with --quiet is oka and will be in 2.2.24.
Nov 6 2020
For portability reasons it would be better to define F_OK if is is not defined.
Nov 4 2020
That is just one bit different - Shouldn't we better have a wrapper as we used to do for other things?
The inotify thing is only used to detect a deleted homedir and stop the agent. AFAIU your problem is that a migration is triggered again. The migration status is a file ~/.gnupg/.gpg-v21-migrated - are you sure that you have extracted it again?
Nov 3 2020
The whole TOFU stuff hash not yet been fully translated because there are conceptional problems with the way the code works.
FWIW, --enforce-passphrase-constraints does already work for symmetric-only encryption since 2.2.21 (rGae8b88c635424ef3). Thus this bug is actually a feature request to have a separate set of passphrase constraints option for symmetric-only mode.
Nov 2 2020
The next version will fix the wrong warning and also allow for an empty value.
No, overlapped I/O is not used. OVL is just a zeroed out memory area and thus hHandle is NULL. Errors are of course checked.
Note: menu_backsign can be enhanced to detect such a case in the same way it detects missing backsigs.
We should find a way to figure out the OpenPGP S/N even if OpenPGP is disabled. I'll ask Yubico.
Oct 29 2020
Indeed we need to fix/enhance this to make testing of --quick-revoke-sig easier. See over at T5093
I recall that I had the same bug during development. Must have slipped in again - Good catch.
I forgot that we have LOCK and UNLOCK commands in scdaemon. This was implemented around 2005 but there are no more users in gpg meanwhile.
On purpose. We actually allow user ids and gpg should somehow reflect this. As requested by you I changed it in the man page to what is suggested.
In short eddsa secret keys generated with current 2.3 can't be imported with 2.2, right? That will lead to a compatibility problem, so we need to fix that in 2.2.
Oct 28 2020
The backend part is ready. Someone(tm) now needs to add it to gpgme. Extending the sign key API might be the best solution.