Use pre-signed URLs for media storage when using S3 #9
Conversation
This file contains 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
jesseplusplus
added a commit
that referenced
this pull request
Feb 8, 2023
originally introduced in #9
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.
The default way mastodon uses S3 for object storage is insecure:
This PR overrides all urls to be expiring urls when using S3 to fix these issues.
I did this with a monkey patch of the
urlmethod instead of changing all uses ofurltoexpiring_urlto minimize conflicts with upstream. I also had to manually gsub the output to use the local S3 alias due to thoughtbot/paperclip#2196.