Feature #2912
closed
Updater handles unsigned updates poorly when used on beta/snapshot releases
0%
Description
Running 2.1 beta, and notified of an available snapshot update, the updater attempts to download the update but only afterwards advises it can't do anything anyway, because it's not signed.
The user can fix this by allowing unsigned updates, but if that's needed for beta versions, the code should 'know' or detect it's unsigned, before downloading it all, not download it all then fail.
Improve or warn user of the possible need to flip this setting?
Updated by Jim Pingle over 12 years ago
There is no way to know or detect the fact that the update is signed or unsigned until it has been fully downloaded. The gz signature comes at the tail end of the file and can't be properly verified otherwise (to my knowledge)
It may, however, be possible to change that to prompt at the end of the process to allow the user to continue.
Updated by Chris Buechler over 12 years ago
- Tracker changed from Bug to Feature
- Priority changed from Normal to Low
indeed it's not possible to do as described, but I've been irked on more than one occasion by it just bailing out with "update is unsigned" at the end of auto-update. No reason it couldn't give an option to the user to proceed at that point.