Added Python version checking and changed behavior in Python2.7.9+ to use custom certificate for target server inherited from command line argument. In Python versions < 2.7.9, proxy_server.py does not perform certificate validation of the target server. As that is not part of what the current tests using this script require, that is currently OK. In Python versions > 2.7.9 (SSLContext was added in 2.7.9), the same code actually does check the certificate, using the system's trusted CAs. As a result, since we are using custom certificates, we need to either disable certificate checking in 2.7.9 or load the specific CA for target test server, using the SSLContext and create_default_context functionality also added in 2.7.9. It is easier to do the latter, so the behavior in 2.7.9+ is to check the cert and below 2.7.9 is not to. Note that we do not support Python < 2.7. SSLContext is also available in all Python3 versions that we support. 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.