Creating is not that useful - we prefer modern curves anyway.
I think that retrieving a parameter in compressed format is all what we need as per API.
(3) _gcry_ecc_os2ec in libgcrypt/mpi/ec.c should be modified to support parsing compressed representation.
What kind of API should we offer?
(1) offering something like q@comp name for gcry_mpi_ec_get_mpi
If the intended use case will be in create_request function in gpg/sm/certreqgen.c for subjectKeyIdentifier, the 'q' is already generated in the form of SEXP.
It is up to an application (gpgsm), to convert non-compressed point representation to compressed point representation, here.
Thu, Jul 9
It's in master (to be gnupg 2.3).
Wed, Jul 8
The qualitybar has now been removed from 2.2 and master.
Mon, Jul 6
We will need this for 1.9
Yes, its on my agenda.
Sun, Jul 5
Since this issue is what I came across when googling for gpg inspect revocation certificate, I thought I’d add what I found out:
I'd be interested, is this is still on the agenda?
Thu, Jul 2
I regret to have distracted your attention. All the above applies to a terminal window (KDE's konsole) in my GUI KDE. On the bare FreeBSD console, everything is fine. So this is a bug in some KDE library or konsole. I'm sorry I did not have the idea to test that on the bare console right away. I'll close this bug here.
Hello Mr. Niibe,
It seems that nl_langinfo(CODESET) returns US-ASCII on your system.
Mon, Jun 29
My FreeBSD box is currently not up, so I can't test right now. You may want to look into gnupg/common/utf8conv.c and there set_native_charset(). For historical reasons we start off with latin-1 but then swicth to the selected charset and intialize iconv accordingly. In the case of an error we sometimes fallback to utf-8. You may want to add some debug code (log_debug ("foo bar string=%s\n", some_string);)
in your test, which you did on Linux I guess, 'utf-8' is written downcase, whereas on my system, it is written uppercase 'UTF-8', conforming to what I find elsewhere (e.g. Wikipedia). I do not know though, if there is a recommended way to spell it. 2nd, I know that FreeBSD has some issues with internationalization: it does not support charsets in their POSIX meaning, but emulates them by combining all available locales and CODESETs. Usually, this is not a problem, and most translations and handling of UTF-8 works as expected. Maybe this has some subtle effect causing this issue.
Sun, Jun 28
OpenPGP specifies the use of UTF-8 for all meta data (ie. everything except for the signed/encrypted data). GnuPG has always supported this. I don't known on which OS you are but some don't have UTF-8 support on the command line or tty so you need to tweak your environment first.
Fri, Jun 26
Jun 9 2020
Shall we backport this to 2.2 which is our LTS release?
Jun 8 2020
With the recent change the --sender option has an effect on the selection of the User ID used for the key validity check and the TRUST_ status lines:
Jun 5 2020
MAPI Namespace has a pickFolder method which can be used here.
Jun 4 2020
Jun 3 2020
We already have the option --sender which does what @mgorny requests but only in the TOFU case. I need to revisit the system to see whether we can extend it to WoT and direct key signatures.
Jun 2 2020
Uh, I just noticed that this issue is from dec. 2019 I am unsure why I overlooked this and only noticed it in my regular tracker check today.
@JJworx Thanks for the suggestion / feature request.
May 29 2020
The required libgpg-error 1.38 has now been released.
FYIL This is delayed because there are some dependencies to internals of gnupg.
May 28 2020
Is there a blogpost or similar where the use of several smartcards following this improvement is explained to n00bs like me? :) For now all I find is this thread and some SE answers saying it does not work yet (https://security.stackexchange.com/questions/154702/gpg-encryption-subkey-on-multiple-smart-cards-issue) . If somebody could post a new answer on SE / write a small blog post or similar that would be great. Useful would be to have 1) from which versions and over is that available 2) how this works / how to use.
May 27 2020
GnuTLS seems to have some CMS support; see https://gitlab.com/gnutls/gnutls/-/issues/227 .
May 22 2020
May 21 2020
libgpg-error used to be blamed because of this kind of architectural support in earlier stage of building operating system.
T4774 is my try to fix the problem.
Thank you for your work. Please go ahead.
May 20 2020
If there's no objection to this in a few days, i'll go ahead and merge it to master.
I had assumed that GnuPG prioritized the safety of its users over strict adherence to a particular view of a cryptographic protocol