Securing Content Distribution with The Update Framework (TUF)
summary
The Update Framework (TUF) provides concrete defenses: cryptographic signatures plus metadata expiry to enforce freshness, consistency, integrity, role-based keys with root/timestamp/snapshot/targets delegation, and threshold signing to limit blast radius when keys go offline or are stolen. Real integrations include CNAB, AWS BottleRocket OS, Datadog and ongoing PyPI/Drupal/TYPO3/Joomla work; a Python reference implementation is being refactored, Go is largely dormant, and PHP and Rust clients exist. Enhancements address replay, mix‑and‑match, and dependency‑confusion attacks.
AI-written summary · about
chapters (21)
- 0:00Intro
- 0:33Agenda
- 1:30Content Distribution
- 1:55Software Supply Chain
- 3:13Attacker Target
- 3:51Software Updates
- 5:53SSLTLS
- 9:03dependency substitution attacks
- 11:02What can TUF do
- 12:16Content protection
- 14:13Reducing key loss
- 16:19Hierarchical trust delegation tree
- 17:15Hierarchical trust delegation diagram
- 19:10Summary
- 19:34TUF Overview
- 20:31TUF Specification
- 23:05augmentation proposals
- 24:18reference implementation
- 25:46other implementations
- 27:05integrations
- 29:00outro
related talks
22mSecuring Content Repositories with the Update Framework (TUF)
27mUpdates from The Update Framework
41mUsing TUF to Mitigate Repository Compromises
34mWhen the Going Gets Tough, Get TUF Going! [I]
18mBeyond signatures: Using TUF and Notary to Secure Software Distribution
41mWhen The Going Gets Tough, Get TUF Going!
29mTUF-en up Your Software Supply Chain
42mImproving Package Repository Security – From White Papers to Practice