Signed ubuntu2004 InRelease file is incorrect

$ curl https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2004/x86_64/InRelease
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Origin: NVIDIA
Label: NVIDIA CUDA
Architecture: 
Date: Mon, 25 Apr 2022 23:27:19 +0000
MD5Sum:
 c35996b985a95c9beea3bf629befafa2                                          2743487 Packages
 a5513131dbd2d4e50f185422ebb43ac9                                           481481 Packages.gz
SHA1:
 e68a3352d3bb57458bb1aad2d47f3e2038f50a4f                                  2743487 Packages
 c5ea9556407a3b5daec4aac530cd038e9b490441                                   481481 Packages.gz
SHA256:
 d5a0d1f0512596c2d2aa2f79e08895443e2e2c6140daf96fd9600ec34e931f2f          2743487 Packages
 8556d67c6d380c957f05057f448d994584a135d7ed75e5ae6bb25c3fc1070b0b           481481 Packages.gz
Acquire-By-Hash: no
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQIcBAEBCAAGBQJiZy5bAAoJEKS0aZY7+GPMD8EP/ioR1CnOsj5h5tmrCs1tOW15
s2L8ItIhi6Gu/WQIRqQMwVhrxv+ggjyPaEj2hBJ2Xmtu7gZajYESk2rczCLN+e+k
NSCEGO9R4eBGjciPb2u0wwiAIVJ8kcyr9oBwIZv0Qukto0+gscUsoFO+fiDWolaA
j89aqFEoNt1s1N8W7llQFsoKSp6DHtYKlQvCFcTDF2AUmTP5T7pNK4Ctuj6WKkYM
qx0BCzoDakDzmcMk3/pzMP2fuVX29LVKksnGA2yxZFPfCwKFpAaLV07QZOF9VUL9
+rSz4zLvTMab53qy3SxNNwPLg0XxfejmdVTSns4ZkBv0scc1s2w7DpL2NsNKHvPQ
QPxRg9CfOSG5MnC8jQc3vZpioDTx/rUM8PXJzQq20BNLVVjlixPX8hUarmqWxcM9
k3fsgq/YZf0goTTEic2op3G2E+rfLw/P3Q5Qj/wogGrAHnnhhMjb1U8dHiubbdUd
pluDo+s5kLqzf/Nc72uXVMB07jt8gnCrZOXqIoAYI113XCa89BvJxlshrTxBZPJ3
7Mg9G46mXt2RkwaxKBSejKAjQ55gLxs8BzGjUbHGbPwm1JYp4HAFf8bk9yI8Znd6
ZVKFlec8i3GLhPkC8kAq/m4/bDt5ShAo1UBHnB12RrKcWJUoWvvKBEtYs8TW3CHO
fG7CIYghxzhNXNeIcCkH
=Y+cf
-----END PGP SIGNATURE-----

The unsigned Release file is correct:

$ curl https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2004/x86_64/Release
Origin: NVIDIA
Label: NVIDIA CUDA
Architecture: x86_64
Date: Tue, 12 Apr 2022 23:01:21 +0000
MD5Sum:
 50f768aecbc90dd96ea4b8842150f8ab                                          2743487 Packages
 cd72a21dc262a770ae7b0351bfff924e                                           631054 Packages.gz
SHA1:
 28ee95b0bcdb38feb60309f8a95e110c30cf91a8                                  2743487 Packages
 9e87bad0626194e7969bdac0c9b2ded96d30bd69                                   631054 Packages.gz
SHA256:
 3c64ffe4e155a2dc94046697da31d4241a5ff736fc439d4743e28c4cbde02af4          2743487 Packages
 4dbb95f642f3d642bd1538ff5555964f71f537df2dcc2842c183c28a15bcf7fe           631054 Packages.gz
Acquire-By-Hash: no
2 Likes

We’re re-signing the repository and pushing again, you may have caught a mirror in the middle of an update. Can you please wait a bit and check again?

1 Like

Any updates? We’re dead in the water while this is down.

1 Like

Could this also be the cause of my “NO_PUBKEY” error message? The install script for 20.04 worked yesterday… sorta. At least the public key was recognized.

But the script might install the wrong version of the 470 driver … 470.42.01 vs 470.103.01 currently installed on me machine.

I believe the re-signing is due to the key rotation, but you’ll need to import the new keys:

@jbroadus1 Thanks! Certainly explains why the keys are not working.

@jbroadus1 I did what’s told in the announcement, it didn’t work out. Does it work for you?

Not immediately, but it looks like the signatures have been updated now.