Skip to content

gnupg: add patch to work with pinentry-mac - #69405

Closed
LinusU wants to merge 1 commit into
Homebrew:masterfrom
LinusU:gnupg-pinentry-mac
Closed

gnupg: add patch to work with pinentry-mac#69405
LinusU wants to merge 1 commit into
Homebrew:masterfrom
LinusU:gnupg-pinentry-mac

Conversation

@LinusU

@LinusU LinusU commented Jan 20, 2021

Copy link
Copy Markdown
Contributor
  • Have you followed the guidelines for contributing?
  • Have you checked that there aren't other open pull requests for the same formula update/change?
  • Have you built your formula locally with brew install --build-from-source <formula>, where <formula> is the name of the formula you're submitting?
  • Is your test running fine brew test <formula>, where <formula> is the name of the formula you're submitting?
  • Does your build pass brew audit --strict <formula> (after doing brew install <formula>)?

As discussed in #68265 (comment) this adds the patch to GnuPG recommended by the GPGTools team to workaround for a bug in gpg-agent when a wrong password from the cache is returned by pinentry-mac.

@SMillerDev

Copy link
Copy Markdown
Member

Has this patch been submitted upstream?

@LinusU

LinusU commented Jan 20, 2021

Copy link
Copy Markdown
Contributor Author

I'm not sure.

@lukele do you know if anyone at GPGTools have submitted this upstream?

@lukele

lukele commented Jan 20, 2021

Copy link
Copy Markdown

@SMillerDev @LinusU since this is only relevant for pinentry-mac (in combination with macOS Keychain as pin cache), not the general pinentry implementation, it was not. We have discussed it a few years ago, but there has not been any progress since.

@lukele

lukele commented Jan 20, 2021

Copy link
Copy Markdown

Is it possible to have homebrew recognize MacGPG2 as installed version of gnupg so packages depending on gnupg don't have to install the gnupg package (creating a conflict)

@SMillerDev

Copy link
Copy Markdown
Member

No, all packages that homebrew depends on must be installed using homebrew.

@lukele

lukele commented Jan 20, 2021

Copy link
Copy Markdown

Ok, thanks. That's unfortunate.

@SMillerDev

Copy link
Copy Markdown
Member

since this is only relevant for pinentry-mac (in combination with macOS Keychain as pin cache), not the general pinentry implementation, it was not. We have discussed it a few years ago, but there has not been any progress since.

If the goal is to upstream the pinentry modifications. Why not try and upstream this already?

@BrewTestBot

Copy link
Copy Markdown
Contributor

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@BrewTestBot BrewTestBot added the stale No recent activity label Feb 11, 2021
@lukele

lukele commented Feb 15, 2021

Copy link
Copy Markdown

As has been reported on the GnuPG mailing list it appears that the old pinentry version did not cache passphrases in macOS Keychain. The new one does by default.

So you might want to add a patch which changes the following line from @YES to @NO in order to restore the previous default:
https://github.com/GPGTools/pinentry/blob/85b3564ea3976c48d62028ccba26c2ac3e5b0241/macosx/AppDelegate.m#L38

@BrewTestBot BrewTestBot removed the stale No recent activity label Feb 15, 2021
@BrewTestBot

Copy link
Copy Markdown
Contributor

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@BrewTestBot BrewTestBot added the stale No recent activity label Mar 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

stale No recent activity

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants