feat: add dangerous-prefixes.conf #20
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
added 3 commits
December 12, 2025 17:50
…x check Previously, the dangerous prefix check was incorrectly limited to only run when APT::Get::AutomaticRemove was set to true. This meant that dangerous prefix protection was not applied to regular package removal operations. Changes: - Removed the conditional check for APT::Get::AutomaticRemove - Dangerous prefix checking now runs regardless of automatic remove setting - Maintained whitelist functionality for exempting specific packages - Added example packages to dangerous-prefixes.conf whitelist This fix ensures that dangerous prefix protection works consistently for all package removal operations, providing better system safety.
…x check Previously, the dangerous prefix check was incorrectly limited to only run when APT::Get::AutomaticRemove was set to true. This meant that dangerous prefix protection was not applied to regular package removal operations. Changes: - Removed the conditional check for APT::Get::AutomaticRemove - Dangerous prefix checking now runs regardless of automatic remove setting - Maintained whitelist functionality for exempting specific packages - Added example packages to dangerous-prefixes.conf whitelist This fix ensures that dangerous prefix protection works consistently for all package removal operations, providing better system safety.
…x check Previously, the dangerous prefix check was incorrectly limited to only run when APT::Get::AutomaticRemove was set to true. This meant that dangerous prefix protection was not applied to regular package removal operations. Changes: - Removed the conditional check for APT::Get::AutomaticRemove - Dangerous prefix checking now runs regardless of automatic remove setting - Maintained whitelist functionality for exempting specific packages - Added example packages to dangerous-prefixes.conf whitelist This fix ensures that dangerous prefix protection works consistently for all package removal operations, providing better system safety.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.