Trouble at the top: can Python extend the chains of trust in infrastructure firmware?

arXiv:2609.27802 · cs.CR · Submitted 2026-08-17 · Read on arXiv

cs.CR

Submitted: 2026-08-17

Updated: 2026-08-17

Code: https://github.com/brettcannon/presentations

Terminology

• Verification — 12× in this paper · explained in 2 episodes
• Core — 4× in this paper · explained in 2 episodes
• Provenance — 4× in this paper · explained in 3 episodes
• Trusted Path Execution — 4× in this paper
• Adversarial scenarios — 2× in this paper · explained in 1 episode
• Analyzer — 1× in this paper · explained in 1 episode
• Generalization — 1× in this paper · explained in 13 episodes
• IEEE Symposium on Security and Privacy — 1× in this paper
• Modularity — 1× in this paper · explained in 9 episodes
• Python Enhancement Proposals — 1× in this paper
• Software for Open Networking in the Cloud — 1× in this paper

Sources

• GoLeash: Mitigating Golang Software Supply Chain Attacks with Runtime Policy Enforcement
• MalGuard: Towards Real-Time, Accurate, and Actionable Detection of Malicious Packages in PyPI Ecosystem
• The Art of Hide and Seek: Making Pickle-Based Model Supply Chain Poisoning Stealthy Again

Related papers

• SoK: AI-Augmented Binary Reversing
• Relaxed Sender Anonymity for CBDC Interbank Settlement: A Zero-Knowledge Approach on Permissioned EVM
• Calibration-Family Overfit: Why Trusted Sabotage Monitors Don't Transfer Across Lineages
• Efficient Fuzzy PSI under One-Sided Assumptions
• Sealing the Audit-Runtime Gap for LLM Skills
• Token Composition: A Graph Based on EVM Logs