Upgrading from 4.0.5: "Unable to finish URI (https://repo.turris.cz/hbs/mox/lists/base.lua): Signature verification failure"

Alright, got a little further thanks to @cynerd! Here’s the full list of steps to make it as easy as possible for anyone to get closer.

  1. ssh root@[router IP]
  2. cd /etc/updater/keys/
  3. vim release.pub
  4. Confirm that the first line is a comment and the second line is a base64 encoded key (ends in ==)
  5. If it doesn’t, run the following line by line to fix the .pub and .pub.sig files (the following is for stable branch):
curl -O https://repo.turris.cz/turris-stable/root/etc/updater/keys/release.pub
curl -O https://repo.turris.cz/turris-stable/root/etc/updater/keys/release.pub.sig
curl -O https://repo.turris.cz/turris-stable/root/etc/updater/keys/standby.pub
curl -O https://repo.turris.cz/turris-stable/root/etc/updater/keys/standby.pub.sig
  1. pkgupdate

Note that running pkgupdate will require your attention as it may prompt you to press enter to continue to update to whatever release it finds.

Currently pkgupdate is now stuck on sha256 sum of python3-cryptography which I’m trying to figure out.

INFO:Downloading packages
line not found
line not found
line not found
DIE:
corruption: The sha256 sum of python3-cryptography does not match
Aborted

Edit: running again causes it to fail at a different package, so likely too many packages to update in a short amount of time, causing pkgupdate to fail? Would prefer not to dangerously use opkg upgrade [pkg], hopefully there’s a way to increase the upper time limit of pkgupdate…

Edit2: Have tried opkg upgrade [all luci-*, i18n, and l10 packages] which should be safe to upgrade w/o breaking core functions, still at about 600 list-upgradable packages

Edit3: Got lucky on another run, now running 5.1 after running pkgupdate after the first successful run to pick up the pkg adds

1 Like