Elgato_dark/python-tuf
1
0
Fork 0
mirror of https://github.com/theupdateframework/python-tuf synced 2026-05-24 10:08:28 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
python-tuf/tuf/ngclient
History
Martin Vrachev 5fd3ddccbc ngclient: pick old timestamp if new.ver is equal 
In the spec version 1.0.30, a new change has been added considering what
should happen if there is a new timestamp with the same version.
It says the following:
"In case they [versions] are equal, discard the new
timestamp metadata and abort the update cycle.
This is normal and it shouldn't raise any error."

In other words, if there is a new timestamp with the same version, then
stop the update process and use the old timestamp.

Those changes reflect these latest specification modifications.

Signed-off-by: Martin Vrachev <mvrachev@vmware.com>
2022-06-21 14:52:31 +03:00
..
_internal ngclient: pick old timestamp if new.ver is equal 2022-06-21 14:52:31 +03:00
__init__.py Add client config module 2021-07-05 18:35:32 +03:00
config.py Unify wording of docstrings language in ngclient 2022-02-11 14:51:51 +02:00
fetcher.py Fixes #1916 2022-05-17 09:40:16 +05:30
README.md Improve README 2021-07-05 10:45:19 +03:00
updater.py ngclient: pick old timestamp if new.ver is equal 2022-06-21 14:52:31 +03:00

README.md

Next-gen TUF client for Python

This package provides modules for TUF client implementers.

tuf.ngclient.Updater is a class that implements the client workflow described in the TUF specification (see https://theupdateframework.github.io/specification/latest/#detailed-client-workflow)

tuf.ngclient.FetcherInterface is an abstract class that client implementers can implement a concrete class of in order to reuse their own networking/download libraries -- a Requests-based implementation is used by default.

This package:

  • Aims to be a clean, easy-to-validate reference client implementation written in modern Python
  • At the same time aims to be the library of choice for anyone implementing a TUF client in Python: light-weight, easy to integrate and with minimal required dependencies
  • Is still under development but is planned to become the default client in this implementation (i.e., the older tuf.client will be deprecated in the future)