Skip to content
This repository was archived by the owner on Mar 29, 2022. It is now read-only.

Uptane should not default to using two kinds of hashes in fileinfo (image info) #90

Open
awwad opened this issue May 4, 2017 · 0 comments

Comments

@awwad
Copy link
Contributor

awwad commented May 4, 2017

Currently, Uptane operates with tuf.conf.REPOSITORY_HASH_ALGORITHMS set to ['sha256', 'sha512'], TUF's default, which results in fileinfo (Targets role(s) metadata about images) being generated using both types of hashes. In order to save space in messages to Secondaries in-vehicle, we should use one type of hash, especially for partial verification secondaries. Currently, there is a related bug in TUF that makes this a problem, so we're going to wait until it's fixed in TUF.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant