Python reference implementation of The Update Framework (TUF)
Find a file
Lukas Puehringer 9ec845cbc1 Adopt CI change in TUF docs
Replace mentions of travis/appveyor with GitHub Actions in
governance (contribution) and readme (badges) documents.

Signed-off-by: Lukas Puehringer <lukas.puehringer@nyu.edu>
2020-12-17 10:28:38 +01:00
.github Add basic GitHub workflow to run tests and linters 2020-12-17 10:28:31 +01:00
docs Adopt CI change in TUF docs 2020-12-17 10:28:38 +01:00
tests Fix failing tests on GitHub windows runners 2020-12-16 17:37:57 +01:00
tuf client: update expiration check to match spec 2020-12-08 14:05:44 +00:00
.fossa.yml Switch to fossa requirements analysis strategy 2019-09-17 12:52:22 +02:00
.gitignore Teach git to ignore Emacs backup files 2020-10-26 16:26:52 +00:00
.gitmodules Remove ssl_commons and ssl_crypto submodules 2017-01-09 13:00:25 -05:00
.travis.yml Adopt removal of Python 3.5 support in test config 2020-12-10 18:20:29 +01:00
appveyor.yml Remove breaking python3.9 appveyor build 2020-12-11 11:40:54 +01:00
LICENSE Move license files to root directory 2018-02-05 10:27:04 -05:00
LICENSE-MIT Move license files to root directory 2018-02-05 10:27:04 -05:00
MANIFEST.in MANIFEST.in: Include LICENSE files 2020-10-05 13:13:58 +03:00
pylintrc Add _repository_name and _targets_directory to Pylint's exclude-protected 2018-04-18 11:04:57 -04:00
README.md Adopt CI change in TUF docs 2020-12-17 10:28:38 +01:00
requirements-dev.txt Revise requirements files again 2020-02-18 16:11:31 +01:00
requirements-pinned.txt Update pinned dependencies for testing 2020-12-10 18:21:01 +01:00
requirements-test.txt Add >=Py3.5 constraint for bandit test dependency 2020-12-07 14:16:07 +01:00
requirements.txt Update pinned dependencies for testing 2020-12-10 18:21:01 +01:00
setup.cfg Restructure requirements files 2020-02-06 17:35:51 +01:00
setup.py Update setup.py to drop support for Python 3.5 2020-12-10 18:14:55 +01:00
tox.ini Work around pypa/pip#9215 with old resolver 2020-12-16 17:39:36 +01:00

TUF A Framework for Securing Software Update Systems

Build Coveralls Dependabot Status FOSSA Status CII PyPI


This repository is the reference implementation of The Update Framework (TUF). It is written in Python and intended to conform to version 1.0 of the TUF specification. This implementation is in use in production systems, but is also intended to be a readable guide and demonstration for those working on implementing TUF in their own languages, environments, or update systems.

About The Update Framework

The Update Framework (TUF) design helps developers maintain the security of a software update system, even against attackers that compromise the repository or signing keys. TUF provides a flexible specification defining functionality that developers can use in any software update system or re-implement to fit their needs.

TUF is hosted by the Linux Foundation as part of the Cloud Native Computing Foundation (CNCF) and its design is used in production by various tech companies and open source organizations. A variant of TUF called Uptane is used to secure over-the-air updates in automobiles.

Please see the TUF Introduction and TUF's website for more information about TUF!

Documentation

Contact

Please contact us via our mailing list. Questions, feedback, and suggestions are welcomed on this low volume mailing list.

We strive to make the specification easy to implement, so if you come across any inconsistencies or experience any difficulty, do let us know by sending an email, or by reporting an issue in the GitHub specification repo.

Security Issues and Bugs

Security issues can be reported by emailing jcappos@nyu.edu.

At a minimum, the report must contain the following:

  • Description of the vulnerability.
  • Steps to reproduce the issue.

Optionally, reports that are emailed can be encrypted with PGP. You should use PGP key fingerprint E9C0 59EC 0D32 64FA B35F 94AD 465B F9F6 F8EB 475A.

Please do not use the GitHub issue tracker to submit vulnerability reports. The issue tracker is intended for bug reports and to make feature requests. Major feature requests, such as design changes to the specification, should be proposed via a TUF Augmentation Proposal (TAP).

Limitations

The reference implementation may behave unexpectedly when concurrently downloading the same target files with the same TUF client.

License

This work is dual-licensed and distributed under the (1) MIT License and (2) Apache License, Version 2.0. Please see LICENSE-MIT and LICENSE.

Acknowledgements

This project is hosted by the Linux Foundation under the Cloud Native Computing Foundation. TUF's early development was managed by members of the Secure Systems Lab at New York University. We appreciate the efforts of Konstantin Andrianov, Geremy Condra, Vladimir Diaz, Yuyu Zheng, Sebastien Awwad, Santiago Torres-Arias, Trishank Kuppusamy, Zane Fisher, Pankhuri Goyal, Tian Tian, Konstantin Andrianov, and Justin Samuel who are among those who helped significantly with TUF's reference implementation. Contributors and maintainers are governed by the CNCF Community Code of Conduct.

This material is based upon work supported by the National Science Foundation under Grant Nos. CNS-1345049 and CNS-0959138. Any opinions, findings, and conclusions or recommendations expressed in this material are those of the author(s) and do not necessarily reflect the views of the National Science Foundation.