Query: All Stories

Disable the hidden Close button to prevent problem with screen reader

	Include stories about projects I am a member of.

Closing, as downstream ticket has been closed.

Fixed in libgcrypt 1.9.4.

It must be fixed in 2.3.2. If not, please report.

Line 1454 : if (!opt.pcsc_shared || app->card->cardtype != CARDTYPE_YUBIKEY)
need to remove || app->card->cardtype != CARDTYPE_YUBIKEY

po: Auto update translations

Post release updates

dirmngr: Change the default keyserver.

po: In German always use "Passwort" instead of "Passphrase".

po: Update German translation

t-fam.c: In function 'main':
t-fam.c:34:14: warning: array subscript 'struct arg_and_data_s[0]' is partly outside array bounds of 'unsigned char[22]' [-Warray-bounds]
   34 |   aad0->next = NULL;
      |              ^
t-fam.c:30:10: note: referencing an object of size 22 allocated by 'malloc'
   30 |   aad0 = malloc (offsetof (struct arg_and_data_s, arg) + 2);
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
t-fam.c:35:13: warning: array subscript 'struct arg_and_data_s[0]' is partly outside array bounds of 'unsigned char[22]' [-Warray-bounds]
   35 |   aad0->len = 2;
      |   ~~~~~~~~~~^~~
t-fam.c:30:10: note: referencing an object of size 22 allocated by 'malloc'
   30 |   aad0 = malloc (offsetof (struct arg_and_data_s, arg) + 2);
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
t-fam.c:36:15: warning: array subscript 'struct arg_and_data_s[0]' is partly outside array bounds of 'unsigned char[22]' [-Warray-bounds]
   36 |   aad0->flags = 0;
      |   ~~~~~~~~~~~~^~~
t-fam.c:30:10: note: referencing an object of size 22 allocated by 'malloc'
   30 |   aad0 = malloc (offsetof (struct arg_and_data_s, arg) + 2);
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
t-fam.c:37:18: warning: array subscript 'struct arg_and_data_s[0]' is partly outside array bounds of 'unsigned char[22]' [-Warray-bounds]
   37 |   aad0->print_fd = fd;
      |   ~~~~~~~~~~~~~~~^~~~
t-fam.c:30:10: note: referencing an object of size 22 allocated by 'malloc'
   30 |   aad0 = malloc (offsetof (struct arg_and_data_s, arg) + 2);
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

For GCC 11, modified version of struct arg_and_data_s has an issue for x86_64.

gpg: Report the status of NO_SECKEY for decryption.

Actually, I think there's a way to make gpg_strerror_r more usable on its own. I previously said

I find it quite difficult to use strerror_r and gpg_strerror_r. With having to guess and retry to get an appropriate buffer length, a wrapper which dynamically allocates the string seems to be needed.

Do not show "opaque signature" warning if just one file is to be signed

Update the commit button only if the corresponding wizard page is shown

Ensure correct tab order in VS-NfD compliant mode

Set VS-NfD compliance hint also as tooltip of the commit button

We should update jitterentropy to 3.0.2 or newer, which should be easier to get through certification, if we will go this way. From FIPS perspective, we should be fine with either going through getrandom only or with jitter entropy, but the bottom-line was that we should probably keep both as we do now.

From Stephan I got the following response to the allocation handler use case

I think the last user of random-fips was removed with rCed57fed6de1465e02ec5e3bc0affeabdd35e2eb7

Yes, it makes sense to remove it.

Disable sign option and encrypt options if needed keys are not available

Oh yes, I was blind.

A cursory look doesn't show me where list->result is set to something else than -1. Can you give me a hint?

In GnuPG 2.3, the procedure of decryption has been changed;
It now collects all ENC_TO packet, keeping it to ->PKENC_LIST field, and then process ENCRYPTED packet with the list.

So it is related to code page. Screenshots may be more informative:

After several days of observation, after modifying the configuration file options , the problem has indeed been greatly alleviated.

For the use case of struct arg_and_data_s in gpgme, which may allocate zero-sized ARG[], it seems that GCC 11 interprets it as an invalid use.

cipher: Use offsetof for allocation of gcry_md_context.

swdb: Libgcrypt 1.9.4

Post release updates

Fallout from the fact that the @cbiedl left us and had an internal non-tagged ticket left open (T5456)

I see whats going on. The GitHub gpgme mirror (https://github.com/gpg/gpgme) is no longer updated. The last commit is from June 22, 2021. Changing the source link to the official (https://dev.gnupg.org/source/gpgme) URL gets the latest updates, and now builds successfully.

mpi/longlong.h: fix missing macro parameter parentheses

tests/t-mpi-point: add NIST curve multiplication test vectors

ecc: Fix bug in gcry_pk_get_param for Curve25519.

build: Fix broken mlock detection

random: Silence a warning for building rndjent by Clang.

Minor tweak to gcry_free.

cipher: Extend convenience OID mapping table for AES.

cipher: Fix memory leaks for EdDSA.

ecc: Check the input length for the point.

hwf-x86: fix use of wrong operand type

doc: Clarify gcry_md_setkey for keyed BLAKE hashes.

This has already been fixed with rM4b64774b6d13ffa4f59dddf947a97d61bcfa2f2e

Frankly, I don fully understand your report. Can you please clarify?
Note that with 2.2.8 we introduced full Unicode support on the command line. If you see scrambled output you may want to "chcp 65001" to get the output correctly rendered.

I have recently been busy with the new features and mechanisms of the GpgFrontend project.

wkd: Properly unescape the user-id from a key listing.

All Stories
Use Results
Edit Query
Hide Query

Aug 25 2021

Aug 24 2021

Aug 23 2021

Aug 22 2021

Aug 21 2021

Aug 20 2021