-
Notifications
You must be signed in to change notification settings - Fork 43
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
omaha: Write only SHA256 hash for extra files
For extra files there is only one hash attribute but it was used for both a SHA1 and SHA256 entry in the Omaha response. On the wire and in the UI it's unclear which of the formats it should be. Since we use Omaha more in free style let's only set the SHA256 entry and expect the user to supply this hash in the UI. With a change in go-omaha we can also omit the empty regular SHA1 hash entry but in any case the client would be expected to know about the SHA256 attribute and use this instead. This would match what's done in https://chromium.googlesource.com/chromium/src.git/+/master/docs/updater/protocol_3_1.md
- Loading branch information
Showing
3 changed files
with
6 additions
and
4 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters