Software updates and TUF
The Release Role
The release role is used to sign the metadata within the update system to ensure clients see a consistent state. This basically links up the signatures, the root keys, and the signed files into a cohesive package. Otherwise, an attacker could modify the metadata to cause you to download an older version, for example.
The Timestamp Role
The final role is the timestamp role, which is used to provide information on the availability of updates. Basically, you modify the timestamp file when a new update is ready and sign it to let clients know a new update is available. However, when an update is not available, how do clients know they aren't simply being fed an old version of the file? By re-signing the file frequently, the client will know that even though the file has not changed, it is still valid.
Typically, you want to re-sign the timestamp file daily – ideally, every few hours – so this activity should be automated. Again, if possible, this should be done on a server that is separate from the server on which files are then uploaded to become publicly available.
Why Metadata Matters
You might wonder why you should you be concerned about signing multiple files and metadata within the update system. Why not just create a new version of the software then sign and upload it? By supporting the signing of multiple separate files and using metadata to define updates, you can avoid situations in which your version of an application and a library cause a security vulnerability or simply don't work together. You can also prevent clients from updating a library, which then breaks the system. Additionally, this approach allows you to update separate components individually. Thus, for a large application that includes optional plugins, you can separate everything.
Buy this article as PDF
Xen project announces a privilege escalation problem for Qemu host systems
Attackers can compromise an Android phone just by sending a text message
PC vendor will pre-install Ubuntu on portables in India.
More embarrassment for Adobe's embattled multimedia tool
Mozilla’s script blocker add-on could be putting malware sites on the whitelist.
The Internet community officially banishes the notoriously unsafe Secure Sockets Layer protocol.
Popular desktop environment continues the Gnome 2 legacy – with new support for the Gnome 3 toolkit.
The Obama White House has issued a memorandum telling all US government agencies they must use HTTPS for all websites and web communication.
New program will dial up security for the Firefox browser.
Red Hat's community distro embraces the cloud.