Besu update - unsigned error

[DamoDubes]

Hi. So a Besu update (24.1.2) has just been announced on my Dappnode dashboard. Clicking the link takes me to the Besu package screen, however the Besu update is showing as “unsigned”, and a warning about an “unsafe origin” is present. Is there a reason for this? I was not expecting unsigned files within Dappnode. Is this safe? Thoughts?
Thanks

Before filing a new topic, please provide the following information.

Core DAppNode Packages versions

• bind.dnp.dappnode.eth: 0.2.11
• core.dnp.dappnode.eth: 0.2.90
• dappmanager.dnp.dappnode.eth: 0.2.84, commit: 657ee5f4
• ipfs.dnp.dappnode.eth: 0.2.22
• wifi.dnp.dappnode.eth: 0.2.9
• wireguard.dnp.dappnode.eth: 0.1.3

System info

• dockerComposeVersion: 2.24.5
• dockerServerVersion: 25.0.3
• dockerCliVersion: 25.0.3
• os: ubuntu
• versionCodename: jammy
• architecture: amd64
• kernel: 5.15.0-94-generic
• Disk usage: 65%

[chuygarcia.eth (Chuy Garcia)]

GM! We’re currently having issues with the signature for the Besu package, however this is still being maintained and published. We’ll hopefully get this fixed before the Dencun fork, but in the meantime you can double-check you’re installing the correct package in the Dappnode repository: Releases · dappnode/DAppNodePackage-besu · GitHub

We’re sorry about this inconvenience!