-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Some key signatures are considered weak with gnupg 2.4 #45
Comments
lazka
added a commit
to lazka/msys2-pacman
that referenced
this issue
Dec 8, 2023
Our keyring contains SHA1 signatures, which gnupg 2.4 no longer imports by default. We can't easily get rid of them now, so allow them for now. See msys2/MSYS2-keyring#45
lazka
added a commit
to lazka/msys2-pacman
that referenced
this issue
Dec 8, 2023
Our keyring contains SHA1 signatures, which gnupg 2.4 no longer imports by default. We can't easily get rid of them now, so allow them for now. See msys2/MSYS2-keyring#45
lazka
added a commit
to msys2/msys2-pacman
that referenced
this issue
Dec 8, 2023
Our keyring contains SHA1 signatures, which gnupg 2.4 no longer imports by default. We can't easily get rid of them now, so allow them for now. See msys2/MSYS2-keyring#45
As of today the repos no longer contain packages signed by the weak key. Older versions still do of course.. |
elieux
added a commit
that referenced
this issue
Apr 10, 2024
New option is required to maintain status quo for current keys with GnuPG v2.4. See #45. See: msys2/msys2-pacman@4903343
lazka
added a commit
to lazka/msys2-pacman
that referenced
this issue
May 5, 2024
Our keyring contains SHA1 signatures, which gnupg 2.4 no longer imports by default. We can't easily get rid of them now, so allow them for now. See msys2/MSYS2-keyring#45
lazka
added a commit
to lazka/msys2-pacman
that referenced
this issue
May 5, 2024
Our keyring contains SHA1 signatures, which gnupg 2.4 no longer imports by default. We can't easily get rid of them now, so allow them for now. See msys2/MSYS2-keyring#45
lazka
added a commit
to lazka/msys2-pacman
that referenced
this issue
May 5, 2024
Our keyring contains SHA1 signatures, which gnupg 2.4 no longer imports by default. We can't easily get rid of them now, so allow them for now. See msys2/MSYS2-keyring#45
lazka
added a commit
to msys2/msys2-pacman
that referenced
this issue
May 5, 2024
Our keyring contains SHA1 signatures, which gnupg 2.4 no longer imports by default. We can't easily get rid of them now, so allow them for now. See msys2/MSYS2-keyring#45
672 packages left on the server, 226 come from i686. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Updating to gnupg 2.4 results in the Alexey's packager key losing trust:
This is because the packager key has 3 out of currently 4 signatures using a weak algo (SHA1), the 4. is Ray's revoked key, so ignore:
--allow-weak-key-signatures
in pacman-keyIn theory, Alexey could re-sign his packagers key with a better algo, and @elieux could add a signature for Alexey's packagers key, which would with mine get us back to three non-weak signatures. Not sure that's worth it.
I've added a regression test in msys2/msys2-tests#56 as well, so we notice when the key trust fails in the future.
The text was updated successfully, but these errors were encountered: