Update ImageMagick policy to allow the XC module #815
Merged
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
The presentation format recording scripts use the xc module (which stands for "Constant Color" to generate placeholder images for slides which are missing / failed to convert and a few other circumstances. The XC module is safe to enable, since it doesn't involve reading any files - it only generates single-color in memory images, and image sizes (memory usage) are limited by other sections of the policy.
ffdixon
approved these changes
Dec 10, 2025
ffdixon
approved these changes
Dec 10, 2025
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.
The presentation format recording scripts use the ImageMagick XC module (which stands for "Constant Color") to generate placeholder images for slides which are missing / failed to convert and a few other circumstances.
The XC module is safe to enable, since it doesn't involve reading any files - it only generates single-color in memory images, and image sizes (memory usage) are limited by other sections of the policy.
Fix proposed by @schrd in bigbluebutton/bigbluebutton#24352 (comment)
Fixes bigbluebutton/bigbluebutton#24352