Are you on Windows or Linux? What version of Kleopatra or Gpg4win are you using?
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Oct 19 2020
See also T5098 - I am sorry for this regression. We are working on a fix.
Which version of Gpg4win did you install, from where, and which OS version are you using? Why did you install gpg4win at a non-default location?
But changing just the displayed S/N should not disturb anything.
No, the above patch makes OpenPGP app stop working.
(I don't know well about Yubikey specific serial number.)
Oct 18 2020
gcc also warns about missing arguments and hopefully also if the arg for %n is not an int*.
You may need to enable these warnings which we do at least in maintainer-mode. On Windows some of the warnings might be wrong because mingw assumes the MS implementation.
Fair enough with regards to portability, and this is not a hill I will die on, but can you comment on the security concerns of using %n?
Nope %n works on all implementations I am aware of. It has to because it is part of even C90.
Oct 17 2020
Hi Werner,
Oct 16 2020
@werner , if you would like some help moderating this bug tracker, I don't mind volunteering to do it.
Sorry, it is entirely non-sense to ban useful printf features. Also note that we use our own printf implementation to avoid portability problems with for example "%zu". If you have a problem with any of the uses of "%n", please explain the problem.
Oct 15 2020
Oct 14 2020
Please understand that this is a bug tracker and not a support line.
The user is asked for a passphrase only if the key has a passphrase. I am still in favor of making a passphrase optional and then we need an extra dialog. Better safe than sorry. Those who have a workflow which includes the export of the secret key can still use the command line.
Oct 13 2020
I suggest to also change the option to "Backup Secret Key..." (i.e. singular instead of plural) because the corresponding action does not support the export of multiple secret keys.
This doesn't help. I think that's because after
flush_cached_data (app, dobj->tag);
do_writecert does
do_readkey (...)
which fills the cache again.
Caching issue. do_writecert in app-piv flushes the cache but may be the wrong DO. Can you try to
Kleopatra does now support using multiple smartcards with multiple apps concurrently (at least as far as the backend scdaemon supports this). Only tested with master of everything so far.
Oct 12 2020
Oct 11 2020
Oct 10 2020
Oct 9 2020
I think you have missed the Key Pair Creation Wizard:
Create a personal X.509 key pair and certification request
kleopatra/src/newcertificatewizard/chooseprotocolpage.ui
Oct 8 2020
I have added a workaround to Kleopatra: rKLEOPATRA57cf71b043d198f85270eb3b8782de6277b8b889
I'm testing:
diff --git a/agent/findkey.c b/agent/findkey.c index fa9e5b548..eec85ba67 100644 --- a/agent/findkey.c +++ b/agent/findkey.c @@ -996,7 +996,10 @@ agent_key_from_file (ctrl_t ctrl, const char *cache_nonce, if (r_passphrase) *r_passphrase = NULL;
I really like that you do stuff like this.
Oct 7 2020
OK, I upgraded the patch, including style adjustments to GNU style despite feeling that not having clang-format support for GNU style leads to it driving away contributors. It also credits Andy, and I have personally e-mailed Andy before.
v2: avoid __int128 which is poorely optimized, and bizarrely not available
in 32-bit addressing mode (our SIMD unit is 128 bits).
v3: properly credit Andy and Cryptograms (there was never mal-intent here, just FUD).
Thanks for the quick analysis.
Oct 6 2020
Please ask your distribution . What I see here is a problem with the packaging of a dedicated build system. This is not the build system which comes with GnuPG. Feel free to reopen if you can show that this is a native gnupg build problem.
We understand the problem, it's a regression from August. For T4083 we changed an internal function to better work with Windows UTF-16 filenames in preperation to at some point fully support UTF-16 and only use the wide character functions as system calls.
But that broke places where internally the local 8 bit encoding was still used.
I can reproduce this.
Observation:
The umlaut is displayed incorrectly on the command line (cmd.app) when the keybox file is created.
(This may or may not be relevant.)
Hi Zetrick,
Hi Zetrick,
Perhaps, don't allow automatic use of available card keys would be better:
diff --git a/agent/command.c b/agent/command.c index 160979dae..b6286becf 100644 --- a/agent/command.c +++ b/agent/command.c @@ -2292,13 +2292,7 @@ cmd_scd (assuan_context_t ctx, char *line) if ((argc == 1 && !strcmp (argv[0], "SERIALNO")) || (argc == 2 && !strcmp (argv[0], "GETINFO") - && !strcmp (argv[1], "version")) - || (argc == 2 - && !strcmp (argv[0], "GETATTR") - && !strcmp (argv[1], "KEY-FPR")) - || (argc == 2 - && !strcmp (argv[0], "KEYINFO") - && !strcmp (argv[1], "--list=encr"))) + && !strcmp (argv[1], "version"))) xfree (l); else {