Issue Weak Algorithm Warning (DSA1024) for Plesk Repositories on Ubuntu 24.04 LTS

[Janko1000]

me too

 

[stony]

me too
Synchronizing the Debian APT package index files...
Hit:2 Index of /pool/PSA_18.0.70_16953 noble InRelease
Hit:3 LiveConfig® Repository main InRelease
Hit:5 LiveConfig® Repository noble InRelease
Hit:6 Index of /PHP74_17 noble InRelease
Get:8 Index of /PHP80_17 noble InRelease [3545 B]
Hit:10 Index of /PHP81_17 noble InRelease
Get:11 Index of /PHP82_17 noble InRelease [4009 B]
Hit:12 Index of /grafana/deb stable InRelease
Get:13 Index of /PHP83_17 noble InRelease [4009 B]
Hit:14 Index of /PHP84_17 noble InRelease
Hit:15 Index of /pool/WPB_18.0.69_87 all InRelease
Hit:16 Index of /apps/ubuntu/ noble-apps-security InRelease
Hit:17 Index of /apps/ubuntu/ noble-apps-updates InRelease
Hit:18 Index of /ubuntu/24.04/slot-1/ noble InRelease
Hit:19 Index of /infra/ubuntu/ noble-infra-security InRelease
Hit:1 Index of /linux/distributions/ubuntu/ubuntu/ noble InRelease
Hit:4 Index of /linux/distributions/ubuntu/ubuntu/ noble-updates InRelease
Hit:20 Index of /infra/ubuntu/ noble-infra-updates InRelease
Hit:7 Index of /linux/distributions/ubuntu/ubuntu/ noble-backports InRelease
Hit:21 Index of /ubuntu/24.04/slot-2/ noble InRelease
Err:6 Index of /PHP74_17 noble InRelease
The following signatures were invalid: 8BADC1A02FC9C07FB8C20EC0BD11A6AA914BDF7E (untrusted public key algorithm: dsa1024)
Hit:9 Index of /linux/distributions/ubuntu/ubuntu/ noble-security InRelease
Hit:22 Index of /ubuntu/24.04/slot-3/ noble InRelease
Err:8 Index of /PHP80_17 noble InRelease
The following signatures were invalid: 8BADC1A02FC9C07FB8C20EC0BD11A6AA914BDF7E (untrusted public key algorithm: dsa1024)
Hit:23 Index of /ubuntu/24.04/slot-4/ noble InRelease
Hit:24 Index of /ubuntu/24.04/slot-5/ noble InRelease
Hit:25 Index of /ubuntu/24.04/slot-6/ noble InRelease
Hit:26 Index of /ubuntu/24.04/slot-7/ noble InRelease
Err:12 Index of /grafana/deb stable InRelease
The following signatures were invalid: 8BADC1A02FC9C07FB8C20EC0BD11A6AA914BDF7E (untrusted public key algorithm: dsa1024)
Hit:27 Index of /ubuntu/24.04/slot-8/ noble InRelease
Get:28 Index of /imunify360/ubuntu/24.04/ noble InRelease [1168 B]
Err:18 Index of /ubuntu/24.04/slot-1/ noble InRelease
The following signatures were invalid: 9EE467641C635726A184D64B8C55A6628608CB71 (untrusted public key algorithm: dsa1024)
Err:21 Index of /ubuntu/24.04/slot-2/ noble InRelease
The following signatures were invalid: 9EE467641C635726A184D64B8C55A6628608CB71 (untrusted public key algorithm: dsa1024)
Err:22 Index of /ubuntu/24.04/slot-3/ noble InRelease
The following signatures were invalid: 9EE467641C635726A184D64B8C55A6628608CB71 (untrusted public key algorithm: dsa1024)
Err:23 Index of /ubuntu/24.04/slot-4/ noble InRelease
The following signatures were invalid: 9EE467641C635726A184D64B8C55A6628608CB71 (untrusted public key algorithm: dsa1024)
Err:24 Index of /ubuntu/24.04/slot-5/ noble InRelease
The following signatures were invalid: 9EE467641C635726A184D64B8C55A6628608CB71 (untrusted public key algorithm: dsa1024)
Err:25 Index of /ubuntu/24.04/slot-6/ noble InRelease
The following signatures were invalid: 9EE467641C635726A184D64B8C55A6628608CB71 (untrusted public key algorithm: dsa1024)
Err:26 Index of /ubuntu/24.04/slot-7/ noble InRelease
The following signatures were invalid: 9EE467641C635726A184D64B8C55A6628608CB71 (untrusted public key algorithm: dsa1024)
Err:27 Index of /ubuntu/24.04/slot-8/ noble InRelease
The following signatures were invalid: 9EE467641C635726A184D64B8C55A6628608CB71 (untrusted public key algorithm: dsa1024)
Err:28 Index of /imunify360/ubuntu/24.04/ noble InRelease
The following signatures were invalid: 9EE467641C635726A184D64B8C55A6628608CB71 (untrusted public key algorithm: dsa1024)
Reading package lists...
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: Index of /PHP74_17 noble InRelease: The following signatures were invalid: 8BADC1A02FC9C07FB8C20EC0BD11A6AA914BDF7E (untrusted public key algorithm: dsa1024)
W: GPG error: Index of /PHP80_17 noble InRelease: The following signatures were invalid: 8BADC1A02FC9C07FB8C20EC0BD11A6AA914BDF7E (untrusted public key algorithm: dsa1024)
E: The repository 'Index of /PHP80_17 noble InRelease' is not signed.
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: Index of /grafana/deb stable InRelease: The following signatures were invalid: 8BADC1A02FC9C07FB8C20EC0BD11A6AA914BDF7E (untrusted public key algorithm: dsa1024)
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: Index of /ubuntu/24.04/slot-1/ noble InRelease: The following signatures were invalid: 9EE467641C635726A184D64B8C55A6628608CB71 (untrusted public key algorithm: dsa1024)
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: Index of /ubuntu/24.04/slot-2/ noble InRelease: The following signatures were invalid: 9EE467641C635726A184D64B8C55A6628608CB71 (untrusted public key algorithm: dsa1024)
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: Index of /ubuntu/24.04/slot-3/ noble InRelease: The following signatures were invalid: 9EE467641C635726A184D64B8C55A6628608CB71 (untrusted public key algorithm: dsa1024)
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: Index of /ubuntu/24.04/slot-4/ noble

 

[Achim Drees]

...same here

 

[H9k]

It's not a warning anymore, it's an error. Seems like Ubuntu now deprecated the algorithm altogether.
See here Resolved - Apt update warning weak algorithm (dsa1024)
Obiously, something went wrong on Plesk side. I"m sure they'll fix it soon.

 

[Michael.P]

I have the same problem in Ubuntu 24

 

[Harm Jakob Tolsma]

Same errors here and also the warnings about immunify360.
Plesk Obsidian v18.0.70_build1800250523.14 os_Ubuntu 24.04

 

[Nelly]

Yes same here,

Reason: 2025-06-02 06:25:19 INFO: pum is called with arguments: ['--list', '--repo-info', '--json']
/usr/lib/python3/dist-packages/apt/cache.py:562: Warning: W:An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: Index of /grafana/deb stable InRelease: The following signatures were invalid: 8BADC1A02FC9C07FB8C20EC0BD11A6AA914BDF7E (untrusted public key algorithm: dsa1024), W:Failed to fetch https://autoinstall.plesk.com/grafana/deb/dists/stable/InRelease The following signatures were invalid: 8BADC1A02FC9C07FB8C20EC0BD11A6AA914BDF7E (untrusted public key algorithm: dsa1024), W:Some index files failed to download. They have been ignored, or old ones used instead.
res = self._cache.update(fetch_progress, slist, pulse_interval)
2025-06-02 06:25:21 ERROR: Apt cache fetch failed. Try to run the `apt-get update` command.
2025-06-02 06:25:21 ERROR:
2025-06-02 06:25:21 ERROR: Exited with returncode 1.

 

[ArmReu]

Same here on a machine that's now running Plesk Obsidian 18.0.70 on Ubuntu 24 for PHP 7.4 and Imunify360.

Also it seams like related to now system updates being reported available but fail updating with "Error: Unable to receive update information for the package(s)"

 

[Krzysztof]

I confirm the bug on PLESK versions from 18.0.64 upwards for Ubuntu 24.04.
untrusted public key algorithm: dsa1024 for PHP7.4, grafana, PHP8.0
No error for: PHP8.1, 8.2, 8.3

 

[Sebahat.hadzhi]

This fixes the problem for system packages (but not for imunify360):

[Workaround] Apt Warning: Signature Key Uses Weak Algorithm | UbuntuHandbook

tldr: Add a file

/etc/apt/apt.conf.d/99weakkey-warning

with

APT::Key::Assert-Pubkey-Algo ">=rsa2048,ed25519,ed448,dsa1024";

inside to disable the warning.

To undo, rm the file.

This is a legit workaround also suggested by our team. However, please do proceed with caution as the action can impact the overall security of the system. Our team is already working on releasing a fix. I will follow up with more details.