Docs: add security guidance for untrusted input - #4590
Closed
nanggo wants to merge 1 commit into
Closed
Conversation
Owner
|
Thank you very much for taking the time to open a PR. Inspired by this I've revisited and refreshed the existing security policy, expanding it to include some of the topics you've mentioned and discussed at #4098 - see commit 4180d8b This also adds a dedicated security page to the website as well as displaying it on the GitHub repo. |
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.
I use sharp to process untrusted remote images in an open-source social preview generator. This documents the relevant constructor defaults, download and runtime limits, loader restrictions, and when individual settings can be relaxed for trusted input.
Closes #4098.