mes

Hi, I recently began getting errors related to key signing when doing `apt update`. Err:5 http://armbian.lv.auroradev.org/apt trixie InRelease Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing key on DF00FAF1C577104B50BF1D0093D6889F9F0E78D5 is not bound: No binding signature at time 2026-10-26T05:34:21Z because: Policy rejected non-revocation signature (PositiveCertification) requiring second pre-image resistance because: SHA1 is not considered secure since 2026-02-01T00:00:00Z Missing key 8CFA83D13EB2181EEF5843E41EB30FAF236099FE, which is needed to v erify signature. W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. OpenPGP signature verification failed: http://armbian.lv.auroradev.org/apt trixie InRelease: Sub-proc ess /usr/bin/sqv returned an error code (1), error message is: Signing key on DF00FAF1C577104B50BF1D0093D6889F9F0E78D5 is not bound: No binding signature at time 2026-10-26T05:34:21Z because: Policy rejected non-revoc ation signature (PositiveCertification) requiring second pre-image resistance because: SHA1 is not considered secure since 2026-02-01T00:00:00Z Missing key 8CFA83D13EB2181EEF5843E41EB30FAF236099FE, which is needed to verify sign ature. W: Failed to fetch http://apt.armbian.com/dists/trixie/InRelease Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing key on DF00FAF1C577104B50BF1D0093D6889F9F0E78D5 is not bound: No binding s ignature at time 2026-10-26T05:34:21Z because: Policy rejected non-revocation signature (PositiveCertification) requiring second pre-image resistance because: SHA1 is not considered secure since 2026-02-01T00:00:00Z Missing ke y 8CFA83D13EB2181EEF5843E41EB30FAF236099FE, which is needed to verify signature. I asked for help on #armbian on libera.chat, and based on help from igorpec, I found the following resources: * https://wiki.debian.org/SecureApt?pow_referer=https%3A%2F%2Fnoai.duckduckgo.com%2F#How_to_tell_apt_what_to_trust * https://armbian.atomonetworks.com/apt/ * https://github.com/armbian/configng#compatibility (make sure to click the arrow and expose the content under "Add the Armbian key and repository, then install the tool:") Using these, I solved these errors and warnings with the following procedure: Backup the existing armbian.gpg key: `mv /usr/share/keyrings/armbian.gpg /usr/share/keyrings/armbian.gpg.bak`. Probably unnecessary Download and convert the new armbian signing key: `curl -fsSL https://apt.armbian.com/armbian.key | sudo gpg --dearmor --yes --output /usr/share/keyrings/armbian.gpg` Give the new key the appropriate permissions: `chmod 664 /usr/share/keyrings/armbian.gpg` Now `apt update` does not give errors or warnings. Please note, this procedure gives a lot of trust to the key at the URL https://apt.armbian.com/armbian.key which may or may not be appropriate depending on your circumstances. Looking forward to any improvements the community can suggest to this procedure. Thanks! -mes Context: * running nextcloudpi, which uses armbian. * recently updated to trixie using ncp-dist-upgrade script * I did not find any helpful documentation on the online armbian documentation site: https://docs.armbian.com/