[SERVER-25422] Debian Wheezy mongodb 3.2 repository signed with a bad key Created: 03/Aug/16  Updated: 03/Aug/16  Resolved: 03/Aug/16

Status: Closed
Project: Core Server
Component/s: Packaging
Affects Version/s: 3.2.8
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Holger Freyther Assignee: Unassigned
Resolution: Duplicate Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-25421 Ubuntu Install - GPG error BADSIG D68... Closed
Related
related to SERVER-22143 GPG error - BADSIG D68FA50FEA312927 Closed
Operating System: ALL
Steps To Reproduce:

This seems to be SERVER-22144 happening again

$ curl http://repo.mongodb.org/apt/debian/dists/wheezy/mongodb-org/3.2/Release > Release
$ curl http://repo.mongodb.org/apt/debian/dists/wheezy/mongodb-org/3.2/Release.gpg > Release.gpg
shasum *
a4f86ac7fe5581db025a60f8aadeeb288f8a142a  Release
2cb1424a220dfccb3eec6ef4cea6590729131979  Release.gpg
(reverse-i-search)`re': curl http://repo.mongodb.org/apt/debian/dists/wheezy/mongodb-org/3.2/Release.gpg > Release.gpg
$ gpg --recv-key EA312927
..
$ gpg --verify Release.gpg Release
gpg: Signature made Tue Aug  2 04:21:56 2016 CEST using RSA key ID EA312927
gpg: BAD signature from "MongoDB 3.2 Release Signing Key <packaging@mongodb.com>" [unknown]

apt-get is printing:
W: GPG error: http://repo.mongodb.org wheezy/mongodb-org/3.2 Release: The following signatures were invalid: BADSIG D68FA50FEA312927 MongoDB 3.2 Release Signing Key <packaging@mongodb.com>

Participants:

 Description   

W: GPG error: http://repo.mongodb.org wheezy/mongodb-org/3.2 Release: The following signatures were invalid: BADSIG D68FA50FEA312927 MongoDB 3.2 Release Signing Key <packaging@mongodb.com>

with todays update. A new (invalid?) signature has been made yesterday.



 Comments   
Comment by Ramon Fernandez Marina [ 03/Aug/16 ]

Thanks for your report hfreyther, and sorry you're running into this. We're having some issues with our repositories that are being investigated at high priority. The behavior you describe was just reported in SERVER-25421, so I'm going to close your ticket as a duplicate. Please watch SERVER-25421 for updates.

Thank you,
Ramón.

Generated at Thu Feb 08 04:09:08 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.