b163caa29b
in test_download.py. In the process, added another test cert and generalized the server process killer in test_download.py. Additionally, I added another expected-to-be-good certificate that was generated in the same way as the new bad certificates (but for their individual flaws of course). This is because the new certs aren't exactly like the old good cert, so that we have another cert to test against in case the way the certs were generated turns out to matter at some point in the future. Also slightly increased a start-servers delay in the test in response to one test system taking too long and seeing connection issues. Probably not helped by the number of processes. Clarified a related comment in the test code. Also made a note that environment variable cleanup would be good to add to test_download.py, either copied from or moved somewhere accessible from test_proxy_use.py Signed-off-by: Sebastien Awwad <sebastien.awwad@gmail.com> |
||
|---|---|---|
| .github | ||
| docs | ||
| tests | ||
| tuf | ||
| .gitignore | ||
| .gitmodules | ||
| .pyup.yml | ||
| .travis.yml | ||
| appveyor.yml | ||
| ci-requirements.txt | ||
| dev-requirements.txt | ||
| LICENSE | ||
| LICENSE-MIT | ||
| MANIFEST.in | ||
| pylintrc | ||
| README.md | ||
| requirements.in | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| tox.ini | ||
A Framework for Securing Software Update Systems
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 Docker, DigitalOcean, Flynn, LEAP, Kolide, Cloudflare, 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. 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.