Søg i Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Læs mere

New PGP keyy?

  • 2 svar
  • 1 har dette problem
  • 13 visninger
  • Seneste svar af rjmx

more options

I have an automated process to download new Mozilla releases: It downloads them, downloads the SHA file, checks the SHA file's PGP signature, then checks the file's SHA hash.

Today, while downloading Firefox 89.0, It bombed out, telling me that the signing key is "4360FE2109C49763186F8E21EBE41E90F6F12F6D", and that I don't have that public key.

No problem, I thought. Mozilla's probably just got a new signing key. I'll just grab a copy from the keyservers.

But I can't. It doesn't appear on any of the three keyservers I tried (MIT, PGP Global Directory, or key-server.io). Have I missed something? If it's only available on the Mozilla website, that doesn't sound very safe. PGP public keys are supposed to be, well, publicly available.

So where's the key?

I have an automated process to download new Mozilla releases: It downloads them, downloads the SHA file, checks the SHA file's PGP signature, then checks the file's SHA hash. Today, while downloading Firefox 89.0, It bombed out, telling me that the signing key is "4360FE2109C49763186F8E21EBE41E90F6F12F6D", and that I don't have that public key. No problem, I thought. Mozilla's probably just got a new signing key. I'll just grab a copy from the keyservers. But I can't. It doesn't appear on any of the three keyservers I tried (MIT, PGP Global Directory, or key-server.io). Have I missed something? If it's only available on the Mozilla website, that doesn't sound very safe. PGP public keys are supposed to be, well, publicly available. So where's the key?

Alle svar (2)

more options

Ændret af TyDraniu den

more options

Ah. I see. Thanks.

So that temporarily solves the problem.

However, publishing it only on the mozilla website is not safe. An attacker could mirror the entire Mozilla website, then add their own malicious code to, say, Firefox, and sign it with another key, even putting that key in the KEY file. They could could redirect people to their website, say with a DNS hack, and we'd be none the wiser.

Why is it so difficult to upload the updated key to public keyservers?