Page MenuHome GnuPG

Bug Report
ActivePublic

Members

  • This project does not have any members.
  • View All

Recent Activity

Yesterday

gniibe closed T5433: libgcrypt: Do not use SHA1 by default as Wontfix.

The change for pubkey-util.c is not needed any more, because

  • T5665 handles new functions rejects use of SHA-1 as approved signature.
  • pubkey-util.c is used by gcry_pk_sign and gcry_pk_verify.
Tue, Nov 30, 10:48 AM · FIPS, libgcrypt, Bug Report
gniibe added a comment to T5693: GPG sign in corrupts larger terminal sizing.

Thank you for the info.

Tue, Nov 30, 10:35 AM · MacOS, pinentry, Bug Report
pzich added a comment to T5693: GPG sign in corrupts larger terminal sizing.

I ran DYLD_PRINT_LIBRARIES=1 DYLD_PRINT_LIBRARIES_POST_LAUNCH=1 DYLD_PRINT_RPATHS=1 pinentry-curses and see libncurses.5.4 (full output below).

Tue, Nov 30, 8:45 AM · MacOS, pinentry, Bug Report
gniibe added a comment to T5693: GPG sign in corrupts larger terminal sizing.

Is there some other command I should run to check which curses it's using? I see there's a --debug flag but I'm not sure how to use it.

Tue, Nov 30, 3:57 AM · MacOS, pinentry, Bug Report
gniibe added a comment to T5693: GPG sign in corrupts larger terminal sizing.

I think that either of following might be true:
(1) macOS has older ncurses (which doesn't support ioctl well, to get columns/lines info) in system
(2) macOS has BSD curses (with no suport for ioctl)

Tue, Nov 30, 3:53 AM · MacOS, pinentry, Bug Report
pzich added a comment to T5693: GPG sign in corrupts larger terminal sizing.

I installed it with brew and didn't provide any special options. This is one of the new M1 macs though, so perhaps there is some platform check deep in the install that is getting confused?

Tue, Nov 30, 3:40 AM · MacOS, pinentry, Bug Report
gniibe added a comment to T5693: GPG sign in corrupts larger terminal sizing.

Thank you for the information. So, you don't have these environment variables set.

Tue, Nov 30, 2:36 AM · MacOS, pinentry, Bug Report
pzich added a comment to T5693: GPG sign in corrupts larger terminal sizing.

printenv COLUMNS LINES shows no output, however if I echo $COLUMNS $LINES I see 160 48 both before and after the password prompt.

Tue, Nov 30, 2:29 AM · MacOS, pinentry, Bug Report
gniibe added a project to T5693: GPG sign in corrupts larger terminal sizing: MacOS.

Curses application (of pinentry) get information of screen size by:

  • environment variables (COLUMNS, LINES)
  • operating system using TIOCGSIZE or TIOCGWINSZ ioctl
  • tinfo data base
Tue, Nov 30, 2:21 AM · MacOS, pinentry, Bug Report

Sat, Nov 27

swimmerm added a comment to T5593: Gpg4Win displayed 'PATH env variable too big' error during setup.

Caveat, Caveat (Warning, Warning) I know I've been quite busy with other activities, and ITMT my client status went really bad and even worse reached its final point and self-rebooted while I was trying to suspend it, but anyway this update is needed because I just discovered that my last choice to prepend %ProgramFiles(x86)%\Gpg4win\bin;%ProgramFiles(x86)%\GnuPG\bin;%PATH% was not very good. Why ? Simple, as I discovered today (few hours ago) using this syntax, will only be valid&useful only if you really want to restrict Gpg4win v3.1.16 usage only to accounts in Administrators group.
Ok, so now you're wondering: How I discovered this effect ? Again simple, desktop shortcut that I have for starting new 'Command Prompt' was modified to always run as Admin, so I have to specifically choose when I want to run it without Admin privileges, and so today, after I didn't notice I had launched Kleopatra before, right after closing it, I launched a new Command Prompt and so when I tried to run 'gpgconf --kill gpg-agent' I only received this answer :

**'gpgconf' is not recognized as an internal or external command,**
**operable program or batch file.**

So then I obviously opened another 'Command Prompt' as an Admin and correctly killed gpg-agent so ensuring that everything was indeed still working as expected.
So now you're asking, why in the past I had confirmed that prepending those paths I was expecting to work, really worked ?
If you remember well how I reported Iìve done my past installations and tests, I also made those changes in OS System Environment Variables really on the fly and then just re-confirmed they were valid via GUI by simply pressing [ OK ].
And so this is the test I just repeated again and so I can re-confirm you that only after by doing so, every new 'Command Prompt' started as non Admin user will have proper access to those newly prepended paths.
Otherwise, those paths will work only for any new 'Command Prompt' if run with an account in Administrators group.
So while this can still be temporarily fine for me, I'm unsure it might have been a real standard choice for Gpg4win v3.1.16 setup run without experiencing the error I'm reporting in this bug, so please just ensure to avoid using %ProgramFiles(x86)%\Gpg4win\bin;%ProgramFiles(x86)%\GnuPG\bin; syntax when changing your paths on the fly by prepending it or appending to %PATH% even if you should try to definitely solve same error I found and reported with this bug. OK ?
Thanks for your attention (for now).

Sat, Nov 27, 3:27 PM · Bug Report, gpg4win

Fri, Nov 26

outer added a comment to T5699: libgpg-error 1.43 fails t-lock-single-thread test on x86_64 with musl.

Thanks for the help. After running make clean / aclocal / autoconf / autoupdate … &etc, the patch worked & make check passed all eleven 11 tests, ie the new 12th test was not performed.

Fri, Nov 26, 9:46 AM · gpgrt, Bug Report
gniibe added a comment to T5699: libgpg-error 1.43 fails t-lock-single-thread test on x86_64 with musl.

Thank you for your log.

Fri, Nov 26, 6:31 AM · gpgrt, Bug Report
outer added a comment to T5699: libgpg-error 1.43 fails t-lock-single-thread test on x86_64 with musl.

Here is ”config.log", or did you want just the screen output?

Fri, Nov 26, 5:37 AM · gpgrt, Bug Report
gniibe added a comment to T5699: libgpg-error 1.43 fails t-lock-single-thread test on x86_64 with musl.

Please show us the log of configure, not just the result of the failure.

Fri, Nov 26, 3:32 AM · gpgrt, Bug Report
outer added a comment to T5699: libgpg-error 1.43 fails t-lock-single-thread test on x86_64 with musl.

I’m not that geeky anymore.

Fri, Nov 26, 2:35 AM · gpgrt, Bug Report
gniibe added a comment to T5699: libgpg-error 1.43 fails t-lock-single-thread test on x86_64 with musl.

If you see wrong result for the decision of the HAVE_LOCK_OPTIMIZATION (for running the test), it's better to contribute to gnulib (https://www.gnu.org/software/gnulib/) for the detection of thread features.

Fri, Nov 26, 2:01 AM · gpgrt, Bug Report
gniibe added a comment to T5699: libgpg-error 1.43 fails t-lock-single-thread test on x86_64 with musl.
Fri, Nov 26, 1:25 AM · gpgrt, Bug Report

Thu, Nov 25

outer added a comment to T5699: libgpg-error 1.43 fails t-lock-single-thread test on x86_64 with musl.

I've just confirmed that the fixes in the commit "rE50e0f32b1935" above to configure.ca & tests/makefile.am do NOT fix the problem under MacOSX Catalina 10.15.7 using Xcode 12.4, gcc Apple clang-1200.0.32.28.

Thu, Nov 25, 11:31 PM · gpgrt, Bug Report
outer added a comment to T5699: libgpg-error 1.43 fails t-lock-single-thread test on x86_64 with musl.

I'm getting the same error even when compiling with x86_64/glibc (from Apple clang-1200.0.32.28) :(

Thu, Nov 25, 6:59 PM · gpgrt, Bug Report
gniibe added a comment to T5331: Possibly incompatible Ed25519 signature between other implementations and 2.3-bata.

To be conservative, it's better to output non-zero-removed signature.

Thu, Nov 25, 6:29 AM · gnupg (gpg23), Bug Report
gniibe added a comment to T5120: Incompatible Ed25519 secret key (no-encryption).

My proposal is applying SOS (MPI with leading zero octets) patches, for 2.2, because there may be existing keys with SOS already.

Thu, Nov 25, 6:17 AM · gnupg (gpg22), Bug Report
gniibe reopened T5120: Incompatible Ed25519 secret key (no-encryption), a subtask of T5114: GnuPG fails to import back generated and exported EdDSA secret key., as Open.
Thu, Nov 25, 6:14 AM · gnupg, Testing, gpgagent, Bug Report
gniibe reopened T5120: Incompatible Ed25519 secret key (no-encryption) as "Open".

It's not yet solved.

Thu, Nov 25, 6:14 AM · gnupg (gpg22), Bug Report
gniibe updated the task description for T5331: Possibly incompatible Ed25519 signature between other implementations and 2.3-bata.
Thu, Nov 25, 5:52 AM · gnupg (gpg23), Bug Report
gniibe changed the status of T5699: libgpg-error 1.43 fails t-lock-single-thread test on x86_64 with musl from Open to Testing.

Reading the documentation of musl, it seems that there are no equivalent to detect if an application is single-threaded or not.

Thu, Nov 25, 4:11 AM · gpgrt, Bug Report

Wed, Nov 24

gniibe triaged T5699: libgpg-error 1.43 fails t-lock-single-thread test on x86_64 with musl as Normal priority.
Wed, Nov 24, 3:20 AM · gpgrt, Bug Report
gniibe added a comment to T5699: libgpg-error 1.43 fails t-lock-single-thread test on x86_64 with musl.

In the libgpg-error implementation, it may skip synchronization when it can detect an application is single threaded. The t-lock-single-thread test checks if it really skips as intended.

Wed, Nov 24, 3:20 AM · gpgrt, Bug Report
gniibe claimed T5699: libgpg-error 1.43 fails t-lock-single-thread test on x86_64 with musl.
Wed, Nov 24, 2:55 AM · gpgrt, Bug Report
gniibe added a comment to T5393: gnupg coverity static analysis reports.

Thank you.

Wed, Nov 24, 2:52 AM · gnupg (gpg23), Bug Report

Tue, Nov 23

Jakuje added a comment to T5393: gnupg coverity static analysis reports.

(forgot to upload the patch to the last comment)

Tue, Nov 23, 3:59 PM · gnupg (gpg23), Bug Report
Jakuje added a comment to T5393: gnupg coverity static analysis reports.

I am fine with either way. The memcmp variant is probably cleaner to make sure all works as expected in all cases.

Tue, Nov 23, 3:59 PM · gnupg (gpg23), Bug Report
werner triaged T5701: Mismatch between enums and config table as High priority.

Thanks for the well written bug report and the fix.

Tue, Nov 23, 1:29 PM · gnupg (gpg23), Bug Report
werner closed T5682: ed25519 internal authenticate with openpgpcard may send long data over short apdu as Resolved.
Tue, Nov 23, 1:26 PM · Testing, scd, ssh, Bug Report
adriaandegroot added a comment to T5701: Mismatch between enums and config table.

So that you don't need to chase the downstream bug report, the problem from a user's perspective looks like this:

Tue, Nov 23, 12:21 PM · gnupg (gpg23), Bug Report
Jakuje added a comment to T5636: Run integrity checks + selftests from library constructor in FIPS.

Thank you. Extending the semantics of GCRYCTL_CLOSE_RANDOM_DEVICE sounds good to me. I think the deinit functions were created initially especially not to change the semantics of existing code using GCRYCTL_CLOSE_RANDOM_DEVICE, but I agree that it will probably not be an issue.

Tue, Nov 23, 9:59 AM · FIPS, libgcrypt, Bug Report
werner closed T5076: [solved] gpg-agent respawn another process randomly and causes cached passphrase check failed / expired as Resolved.
Tue, Nov 23, 9:18 AM · gnupg (gpg22), Bug Report
werner closed T5120: Incompatible Ed25519 secret key (no-encryption), a subtask of T5114: GnuPG fails to import back generated and exported EdDSA secret key., as Resolved.
Tue, Nov 23, 9:15 AM · gnupg, Testing, gpgagent, Bug Report
werner closed T5120: Incompatible Ed25519 secret key (no-encryption) as Resolved.

I guess this is solved. Feel free to re-open and schedule for 2.2.34

Tue, Nov 23, 9:15 AM · gnupg (gpg22), Bug Report
werner closed T5656: Error emitted: gpg: error reading symlink '/proc/curproc/file': No such file or directory as Resolved.
Tue, Nov 23, 9:07 AM · gnupg (gpg23), MacOS, Bug Report
werner added a project to T5701: Mismatch between enums and config table: gnupg (gpg23).
Tue, Nov 23, 9:04 AM · gnupg (gpg23), Bug Report

Mon, Nov 22

ikloecker changed the status of T5697: Kleopatra: Crashes or hangs on circular certificate chains from Open to Testing.
Mon, Nov 22, 10:51 AM · Restricted Project, kleopatra, Bug Report
ikloecker added a comment to T5697: Kleopatra: Crashes or hangs on circular certificate chains.

Second issue is also fixed.

Mon, Nov 22, 10:50 AM · Restricted Project, kleopatra, Bug Report
adriaandegroot updated the task description for T5701: Mismatch between enums and config table.
Mon, Nov 22, 10:27 AM · gnupg (gpg23), Bug Report
adriaandegroot added a comment to T5701: Mismatch between enums and config table.

Here's a patch against b091a250d1411f9962385d1338c13481da2e0f9e.

Mon, Nov 22, 10:25 AM · gnupg (gpg23), Bug Report
adriaandegroot created T5701: Mismatch between enums and config table.
Mon, Nov 22, 10:22 AM · gnupg (gpg23), Bug Report

Fri, Nov 19

marv created T5699: libgpg-error 1.43 fails t-lock-single-thread test on x86_64 with musl.
Fri, Nov 19, 2:06 PM · gpgrt, Bug Report
hydra3333 added a comment to T5695: libgcrypt cross-compilation error.

PS, knowing little about it, I tend to look at builds scripts here https://github.com/msys2/MINGW-packages on how to do things.
eg https://github.com/msys2/MINGW-packages/tree/master/mingw-w64-libgcrypt

Fri, Nov 19, 9:12 AM · Bug Report
hydra3333 added a comment to T5695: libgcrypt cross-compilation error.

Thank you, it successfully cross-compiles from latest git commit (not sure if it "runs", not tested it).

Fri, Nov 19, 9:09 AM · Bug Report
gniibe added a comment to T5636: Run integrity checks + selftests from library constructor in FIPS.

Part 1 was applied. Part 3, Part 4, and Part 7 are irrelevant now, because we now have rndgetentropy which doesn't use device.

Fri, Nov 19, 8:50 AM · FIPS, libgcrypt, Bug Report
gniibe added a comment to T5695: libgcrypt cross-compilation error.

It was in the middle of merging jitterentropy. Please see T5692 (newer jitterentropy uses pthread by default, which was disabled now).

Fri, Nov 19, 12:52 AM · Bug Report