Consider signing updates.xml to prevent malicious updates

We currently fully trust the Updates.xml that we fetch from the remote server. This could make it easy to let a user unconsciously install tainted packages/updates from an attacker that managed to manipulate the local network.

A possible counter-measure would be to verify the server/Updates.xml, either through https certificate verification, or through signing Updates.xml with a cryptographic key.