Page MenuHome GnuPG

MacOSUmbrella
ActivePublic

Members

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

Watchers

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

Recent Activity

Wed, Oct 13

ikloecker added a comment to T5656: Error emitted: gpg: error reading symlink '/proc/curproc/file': No such file or directory.

No, the error is harmless. I guess it shouldn't be printed (except when debugging).

Wed, Oct 13, 5:18 PM · gnupg (gpg23), MacOS, Bug Report
werner added projects to T5656: Error emitted: gpg: error reading symlink '/proc/curproc/file': No such file or directory: MacOS, gnupg (gpg23).

We now require a way to get the actual image of a process. For macOS the BSD method is used and we obviously need to find another way for macOS.

Wed, Oct 13, 5:03 PM · gnupg (gpg23), MacOS, Bug Report

Fri, Oct 8

werner closed T5633: gpg key generation failure as Wontfix.
Fri, Oct 8, 3:23 PM · MacOS, Bug Report

Mon, Oct 4

p90089 added a comment to T5633: gpg key generation failure .

Currently, I am using --lock-never config to avoid generating lock file as a workaround.

Mon, Oct 4, 4:41 PM · MacOS, Bug Report

Sun, Oct 3

werner added a project to T5633: gpg key generation failure : MacOS.

Sorry, a hostname with slash is simply not allowed by IETF standards. Given that the hostname is part of temporary file names, you will run into an error. Yes, we could remap the slash in the mktemp function but there are lot of other plzces where the hostname is used and certain properties are expected.

Sun, Oct 3, 12:32 PM · MacOS, Bug Report

Mon, Sep 27

aconchillo added a comment to T5610: macOS 11 or newer support: Update libtool.

These are great news. Thank you!

Mon, Sep 27, 6:35 AM · MacOS, ntbtls, npth, libksba, libassuan, libgcrypt, gpgrt
gniibe added a comment to T5610: macOS 11 or newer support: Update libtool.

Pushed the change to libgpg-error and libgcrypt (1.9 and master).
Let us see if there are any problem(s) for that, I will apply it to other libraries when it will be found no problem.

Mon, Sep 27, 4:16 AM · MacOS, ntbtls, npth, libksba, libassuan, libgcrypt, gpgrt
gniibe renamed T5610: macOS 11 or newer support: Update libtool from Update libtool to macOS 11 or newer support: Update libtool.
Mon, Sep 27, 3:31 AM · MacOS, ntbtls, npth, libksba, libassuan, libgcrypt, gpgrt
gniibe added a comment to T5610: macOS 11 or newer support: Update libtool.

Thank you for the information.
For the record, I put the link to the email submitted:
https://lists.gnu.org/archive/html/libtool-patches/2020-06/msg00001.html

Mon, Sep 27, 3:30 AM · MacOS, ntbtls, npth, libksba, libassuan, libgcrypt, gpgrt

Wed, Sep 22

aconchillo added a comment to T5610: macOS 11 or newer support: Update libtool.

Oh, you are right, it's not upstream. It's actually applied to Homebrew (https://brew.sh/) libtool formula which is where I originally got libtool.m4, see:

Wed, Sep 22, 9:06 PM · MacOS, ntbtls, npth, libksba, libassuan, libgcrypt, gpgrt
gniibe added a comment to T5610: macOS 11 or newer support: Update libtool.

I see your point. I'd like to locate/identify where the change comes from.
I think that what you refer by "new libtool.m4" is actually macOS local change (I mean, not from libtool upstream, AFAIK).
Could you please point out the source of the change?

Wed, Sep 22, 2:01 AM · MacOS, ntbtls, npth, libksba, libassuan, libgcrypt, gpgrt

Tue, Sep 21

aconchillo added a comment to T5610: macOS 11 or newer support: Update libtool.

That would work, however we might hit this issue with a new macOS release. Would it make more sense to update to what the new libtool.m4 is doing? Linker flags are the same, it only changes the way they detect macOS versions:

Tue, Sep 21, 8:33 PM · MacOS, ntbtls, npth, libksba, libassuan, libgcrypt, gpgrt
werner added a comment to T5610: macOS 11 or newer support: Update libtool.

That does indeed not look like something which could introduce a regression.

Tue, Sep 21, 11:43 AM · MacOS, ntbtls, npth, libksba, libassuan, libgcrypt, gpgrt
gniibe added a comment to T5610: macOS 11 or newer support: Update libtool.

I misunderstood as if we need to update libtool from upstream.

Tue, Sep 21, 9:16 AM · MacOS, ntbtls, npth, libksba, libassuan, libgcrypt, gpgrt
werner triaged T5610: macOS 11 or newer support: Update libtool as Low priority.

macOS has low priority for us and I do not want to risk any regression.

Tue, Sep 21, 8:42 AM · MacOS, ntbtls, npth, libksba, libassuan, libgcrypt, gpgrt

Sep 2 2021

gniibe closed T5415: YubiKey no longer recognized in GnuPG 2.3.1 on macOS 10.15.7 as Resolved.
Sep 2 2021, 8:29 AM · MacOS, yubikey, Bug Report

Sep 1 2021

gniibe closed T5440: _DARWIN_C_SOURCE kind of "must" be 1, not "900000L" as Resolved.
Sep 1 2021, 8:07 AM · MacOS, libgcrypt, Bug Report

Aug 30 2021

gniibe closed T5365: --with-libgpg-error-prefix doesn't affect gpgrt-config path detection as Resolved.
Aug 30 2021, 7:05 AM · MacOS, gpgrt, Cross-Compiler, libgcrypt

Aug 25 2021

gniibe closed T5370: Apple M1 and Symbol not found: __gcry_mpih_mul_1 as Resolved.
Aug 25 2021, 3:59 AM · arm, MacOS, gnupg, Bug Report
gniibe closed T5268: macOS getentropy as Resolved.

Closing, as downstream ticket has been closed.

Aug 25 2021, 3:51 AM · libgcrypt, MacOS
gniibe set External Link to https://trac.macports.org/ticket/62431 on T5268: macOS getentropy.
Aug 25 2021, 3:49 AM · libgcrypt, MacOS
gniibe closed T5369: GnuPG build on Apple with Clang as Resolved.

Fixed in libgcrypt 1.9.4.

Aug 25 2021, 3:40 AM · libgcrypt, MacOS, Bug Report
gniibe changed the status of T5415: YubiKey no longer recognized in GnuPG 2.3.1 on macOS 10.15.7 from Open to Testing.

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

Aug 25 2021, 3:27 AM · MacOS, yubikey, Bug Report

Aug 13 2021

werner changed the edit policy for MacOS.
Aug 13 2021, 11:08 PM

Jul 28 2021

bernhard added a comment to T5250: macOS: gpgconf SIGSEGV when run via gpgme from the GUI application.

dlopen'ing of gpgme is NOT SUPPORTED. It is in general not a good idea to do this on standard Unix systems.

Jul 28 2021, 11:08 AM · gpgme, MacOS, Bug Report
werner added a comment to T5250: macOS: gpgconf SIGSEGV when run via gpgme from the GUI application.

To extend on this: dlopen'ing of gpgme is NOT SUPPORTED. It is in general not a good idea to do this on standard Unix systems. On Windows we could make it work because DLLs on that platform are well designed and not a hack like the Unix shared objects.

Jul 28 2021, 9:49 AM · gpgme, MacOS, Bug Report

Jul 27 2021

aheinecke claimed T5250: macOS: gpgconf SIGSEGV when run via gpgme from the GUI application.

We really want thunderbird users that interact with GPGME to have a great and stable user experience, but the problem with dynamic loading and self compiled versions is that we cannot really know the build settings and enviornment and it is very time consuming to reproduce that. GPGME does some very low level things for optimized IPC that can depend on build options etc. This is why I am mostly in favor that thunderbird ships a defined version that we can debug and see the settings.

Jul 27 2021, 4:47 PM · gpgme, MacOS, Bug Report
bernhard added a comment to T5250: macOS: gpgconf SIGSEGV when run via gpgme from the GUI application.

Reading the mozilla entry more carefully, there still seems to be an issue.

Jul 27 2021, 10:58 AM · gpgme, MacOS, Bug Report
bernhard added a comment to T5250: macOS: gpgconf SIGSEGV when run via gpgme from the GUI application.

https://blog.gerv.net/2012/01/mozilla-projects-and-gpled-code/

@kaie, thanks for the pointer!

Jul 27 2021, 10:27 AM · gpgme, MacOS, Bug Report

Jul 26 2021

kaie added a comment to T5250: macOS: gpgconf SIGSEGV when run via gpgme from the GUI application.

BTW @kaie

Thunderbird cannot use anything requiring GPL in its default configuration, because Thunderbird wants to distribute a single MPL licensed package that includes all components that are required for OpenPGP.

Any pointer why, they have made that choice, though? A bundle of MPL and GNU GPL components is fully allowed by the licenses as far as I know.

Jul 26 2021, 11:59 PM · gpgme, MacOS, Bug Report

Jul 24 2021

bernhard added a comment to T5250: macOS: gpgconf SIGSEGV when run via gpgme from the GUI application.

Using GPGME is probably the best way, even if gpgme-json might also work for some operations.

Jul 24 2021, 4:52 PM · gpgme, MacOS, Bug Report

Jun 24 2021

werner lowered the priority of T3958: GPGME: Qt Bindings and MacOS from Normal to Low.
Jun 24 2021, 6:31 PM · MacOS, qt, gpgme

Jun 7 2021

gniibe added a comment to T5442: Serial number detection of Yubikey 5 (Yubikey 5 doesn't work after updating to GnuPG 2.3.1).

In your log, it says:

usb_claim_interface failed: -3
Jun 7 2021, 4:46 AM · gnupg (gpg23), yubikey
gniibe added a comment to T5442: Serial number detection of Yubikey 5 (Yubikey 5 doesn't work after updating to GnuPG 2.3.1).

Sorry, I was wrong.

Jun 7 2021, 4:43 AM · gnupg (gpg23), yubikey

Jun 4 2021

werner added a comment to T5442: Serial number detection of Yubikey 5 (Yubikey 5 doesn't work after updating to GnuPG 2.3.1).

I need to see how we can pass the check permission notice up to gpg. This is a too common problem and thus serves some special treatment.

Jun 4 2021, 12:22 PM · gnupg (gpg23), yubikey
Suertzz added a comment to T5442: Serial number detection of Yubikey 5 (Yubikey 5 doesn't work after updating to GnuPG 2.3.1).

GPG Version :

Jun 4 2021, 11:58 AM · gnupg (gpg23), yubikey
Suertzz added a comment to T5442: Serial number detection of Yubikey 5 (Yubikey 5 doesn't work after updating to GnuPG 2.3.1).

I see your situation

Could you please help me to analyze what's going on?
Please add following lines to your scdaemon.conf to see CCID driver's debug output:

debug-ccid-driver
verbose
verbose
verbose

And share the debug output.

Jun 4 2021, 2:08 AM · gnupg (gpg23), yubikey
gniibe added a comment to T5442: Serial number detection of Yubikey 5 (Yubikey 5 doesn't work after updating to GnuPG 2.3.1).

Ah, I think that your problem was fixed in rG53bdc6288f9b: scd: Recover the partial match for PORTSTR for PC/SC. (to be 2.3.2).

Jun 4 2021, 2:02 AM · gnupg (gpg23), yubikey
gniibe triaged T5442: Serial number detection of Yubikey 5 (Yubikey 5 doesn't work after updating to GnuPG 2.3.1) as High priority.
Jun 4 2021, 1:58 AM · gnupg (gpg23), yubikey
gniibe claimed T5442: Serial number detection of Yubikey 5 (Yubikey 5 doesn't work after updating to GnuPG 2.3.1).
Jun 4 2021, 1:57 AM · gnupg (gpg23), yubikey
gniibe reopened T5442: Serial number detection of Yubikey 5 (Yubikey 5 doesn't work after updating to GnuPG 2.3.1) as "Open".

I see your situation

Jun 4 2021, 1:57 AM · gnupg (gpg23), yubikey
Suertzz added a comment to T5442: Serial number detection of Yubikey 5 (Yubikey 5 doesn't work after updating to GnuPG 2.3.1).

If possible, please let us know how you configure the permission to access CCID device with 2.2 (and with 2.3)?

Jun 4 2021, 1:40 AM · gnupg (gpg23), yubikey
gniibe added a comment to T5442: Serial number detection of Yubikey 5 (Yubikey 5 doesn't work after updating to GnuPG 2.3.1).

If possible, please let us know how you configure the permission to access CCID device with 2.2 (and with 2.3)?

Jun 4 2021, 1:32 AM · gnupg (gpg23), yubikey

Jun 3 2021

Suertzz added a comment to T5415: YubiKey no longer recognized in GnuPG 2.3.1 on macOS 10.15.7.

Please excuse my late reply. I was busy with other things over the last few weeks.

Yes, putting disable-ccid into ~/.gnupg/scdaemon.conf works for me with GnuPG 2.3.1 under macOS Catalina (10.15).

I still don't understand what the problem is/was, so I cannot judge whether it's better to recommend this manual configuration for Mac users or to disable CCID by default on macOS.

Jun 3 2021, 11:20 PM · MacOS, yubikey, Bug Report
KasparEtter added a comment to T5415: YubiKey no longer recognized in GnuPG 2.3.1 on macOS 10.15.7.

Please excuse my late reply. I was busy with other things over the last few weeks.

Jun 3 2021, 9:58 AM · MacOS, yubikey, Bug Report

Jun 2 2021

werner moved T5440: _DARWIN_C_SOURCE kind of "must" be 1, not "900000L" from For 1.9 to Backlog on the libgcrypt board.
Jun 2 2021, 12:57 PM · MacOS, libgcrypt, Bug Report
werner moved T5440: _DARWIN_C_SOURCE kind of "must" be 1, not "900000L" from For 1.8 to For 1.9 on the libgcrypt board.
Jun 2 2021, 12:56 PM · MacOS, libgcrypt, Bug Report
werner moved T5440: _DARWIN_C_SOURCE kind of "must" be 1, not "900000L" from Backlog to For 1.8 on the libgcrypt board.
Jun 2 2021, 12:56 PM · MacOS, libgcrypt, Bug Report
gniibe added a comment to T5369: GnuPG build on Apple with Clang.

jitterentropy is also used in Linux kernel, and some people use clang to build it these days. So, I checked the kernel's one. It is simply compiled -O0 by Makefile, and there's no pragma line now (as of v5.13).

Jun 2 2021, 3:16 AM · libgcrypt, MacOS, Bug Report

Jun 1 2021

werner reopened T5369: GnuPG build on Apple with Clang as "Open".

I don't think that it is a good idea to silence this warning. The pragma is esssential for proper random numbers and if clang hijacks a GCC's name space but implements something different it is better to have a warning than to fall into the pit full of dragons.

Jun 1 2021, 8:40 AM · libgcrypt, MacOS, Bug Report