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

Revoking (Yanking) Parcels #296

Open
technosophos opened this issue Feb 3, 2022 · 0 comments
Open

Revoking (Yanking) Parcels #296

technosophos opened this issue Feb 3, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@technosophos
Copy link
Contributor

A desired feature of future-Bindle would be to mark an individual parcel as yanked.

Scenario: Say we have a single library that is frequently shared by many bindles. And imagine the case where a security vulnerability is discovered in this library. We could yank that individual parcel. The following effects could then be built on this feature:

  • When a user downloads a bindle that references a yanked parcel, we can at best warn, at worst prevent them from installing
  • Alternately, we could auto-yank all bindles that reference that parcel (which is heavy-handed, put possibly warranted)
  • We could provide a facility by which a yanked parcel could have a "recommended upgrade" and bindle authors would be notified of that upgrade. e.g. "mySSL 1.2.3 has a vulnerability. Upgrade to mySSL 1.5.6 or greater"

Whatever system we use, we would have to prevent a bad actor from maliciously yanking other people's bindles. e.g. if someone marked the MIT license parcel as "yanked", it could yank every single MIT-licensed bindle

@thomastaylor312 thomastaylor312 added the enhancement New feature or request label Feb 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants