-
Notifications
You must be signed in to change notification settings - Fork 285
Closed
Labels
1.0.0 blockersTo be addressed before 1.0.0 releaseTo be addressed before 1.0.0 releasebacklogIssues to address with priority for current development goalsIssues to address with priority for current development goalsclientRelated to the client (updater) implementationRelated to the client (updater) implementationngclient
Milestone
Description
Description of issue or feature request:
After the acceptance of TAP10 the framework no longer handles compressed metadata. Instead,
the specification should instead recommend that compression be implemented at the presentation layer of the OSI protocol stack, which is better suited to handle decompression of data. Once decompressed, metadata can be validated against the hashes and signatures listed in the Snapshot file.
However, the implementation explicitly asks server to not compress data to avoid potential issues with some server configurations.
Two questions coming from this observation:
- Do all the calculations up to now (for example the ones in PEP458) consider uncompressed metadata?
- Should the implementation match tap10 and allow handling of compressed metadata at a lower level?
Current behavior:
Client explicitly asks server to not compress data
Expected behavior:
Allow handling of compressed metadata at the presentation layer
jkujoshuagl
Metadata
Metadata
Assignees
Labels
1.0.0 blockersTo be addressed before 1.0.0 releaseTo be addressed before 1.0.0 releasebacklogIssues to address with priority for current development goalsIssues to address with priority for current development goalsclientRelated to the client (updater) implementationRelated to the client (updater) implementationngclient