Sanitize summary and URL to prevent malicious attacks#67
Merged
Conversation
Closed
hroncok
reviewed
Apr 20, 2026
befeleme
force-pushed
the
sanitize_inputs_2
branch
from
c9cf4df to
07ad5bb
Compare
Contributor
Imagine you want to reuse the sanitizer from this PR in fedora-python/pyp2rpm#301 -- so you decided to release it on PyPI as a common package called rpm-sanitizer. And in the summary, you write: Replaces dangerous stuff like %(rm -rf) with an escaped form |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Smaller, targeted sanitization. There isn't a good ready-made solution to sanitize these fields. For all the others, packaging.metadata.Metadata instance can be used, which I prepare separately.