Appearance
SEC461 / MD-PIP-CONFIG-TRUSTED-HOST
SEC461 flags AI-native markdown when a pip config set, pip3 config set, or python -m pip config set command sets global.trusted-host.
Why It Matters
Setting trusted-host weakens normal trust checks for package resolution. In shared AI-native instructions, that turns a persistent verification bypass into copy-pastable setup guidance.
What Triggers It
- AI-native markdown surface
- the same parsed markdown region contains:
pip config setpip3 config set- or
python -m pip config set
- the same region also contains:
global.trusted-host ...- or
global.trusted-host=...
The finding points to the global.trusted-host token.
What Does Not Trigger It
- unrelated pip config keys like
global.timeout - install-time
--trusted-hostexamples, because those are covered bySEC448 - unrelated prose that mentions trust or hosts without a matching pip config command
Example
Bad:
bash
pip config set global.trusted-host pypi.example.testBetter:
bash
pip config set global.index-url https://pypi.example.test/simpleRemediation
Remove the trusted-host config and rely on normal TLS-verified Python package sources instead.