Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"pinning" packages to a source repository #50

Open
vadave opened this issue Aug 24, 2022 · 0 comments
Open

"pinning" packages to a source repository #50

vadave opened this issue Aug 24, 2022 · 0 comments

Comments

@vadave
Copy link

vadave commented Aug 24, 2022

Another possible "fundable": Many organizations maintain internal package repositories for libraries that are not publicly shared. This has led to "dependency confusion" attacks, where researchers or malicious actors register a package of the same name in the public (pypi) repository with a higher version number than what the organization publishes internally, causing the pip resolver to select that (malicious) package during package resolution.

While pip does offer other mechanisms to mitigate this attack (hashes and URL-based references being the two that come to mind), those mechanisms do have downsides (hashes still require trust-on-first-use, and URL-based references can be difficult to maintain for larger organizations operating multiple enclaves/private repositories). I'd love to see pip introduce a mechanism allowing users to specify specifically which repository to use for designated packages, vice the current mechanism of querying all configured repositories for the requested packages.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant