Skip to content
A framework for securing software update systems
Branch: develop
Clone or download
Latest commit 37d5833 Mar 13, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github
docs
tests Remove redundant words in comment Feb 26, 2019
tuf Update version to 0.11.2.dev3 Jan 10, 2019
.gitignore Ignore virtualenv and pyenv files Dec 8, 2017
.gitmodules Remove ssl_commons and ssl_crypto submodules Jan 9, 2017
.pyup.yml
.travis.yml
LICENSE Move license files to root directory Feb 5, 2018
LICENSE-MIT
MANIFEST.in
README.md
appveyor.yml
ci-requirements.txt minor: undo some import/dependency re-ordering Aug 31, 2018
dev-requirements.txt DOC: Clarify update instructions for requirements files Jan 8, 2019
pylintrc
requirements.in minor: undo some import/dependency re-ordering Aug 31, 2018
requirements.txt
setup.cfg Update release files. Jul 16, 2014
setup.py Update version to 0.11.2.dev3 Jan 10, 2019
tox.ini

README.md

A Framework for Securing Software Update Systems

Travis-CI Coveralls PyUp Python 3 FOSSA CII

TUF

The Update Framework (TUF) helps developers maintain the security of a software update system, even against attackers that compromise the repository or signing keys. TUF provides a flexible framework and specification that developers can adopt into any software update system.

TUF is hosted by the Linux Foundation as part of the Cloud Native Computing Foundation (CNCF) and is used in production by companies such as Cloudflare, DataDog, DigitalOcean, Docker, Flynn, IBM, Kolide, LEAP, Microsoft, RedHat, and VMware. A variant of TUF called Uptane is widely used to secure over-the-air updates in automobiles.

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).

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 managed by Prof. Justin Cappos and other 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, 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.

You can’t perform that action at this time.