-
-
Notifications
You must be signed in to change notification settings - Fork 404
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Harden Content-Security-Policy - bring all ressources to local OMBI, no Gitlab, no Google should be triggered #4492
Comments
Hi! |
Another image path is the Google Play app store image that is coming from: https://play.google.com/intl/en/badges/static/images/badges/en_badge_web_generic.png and could be hosted within the app. The issue with the avatar is Gravatar is also possible. Your example shows GitHub because it's the default icon being pulled from the Ombi docs repo. https://github.com/Ombi-app/Ombi/search?q=raw.githubusercontent.com There are however two async calls to raw.githubusercontent.com which might also be problematic currently from a non image scenario. |
Thanks for the investigations, i'm open for any PR's regarding this |
Hosting the Google Play image is simply enough, however there does seem to be logic currently that's dynamically generating the Google Play store image relative to the locale set on preferences which Google provides. However it appears that another screen just has the EN Google Play image static. Possibly some code duplication that can be resolved at the same time. The fallback Ombi logo can be moved into the app rather than calling GitHub paths, but external images for Gravatar may still need adding to img-src because there's not really a way around that. |
Are they coming from |
Gravatar avatars are being served from the main domain www.gravatar.com so this should be acceptable to add as https://www.gravatar.com on img-src without being too wide in the same way as the image.tmdb.org domain. The raw.githubusercontent.com domain is serving: https://raw.githubusercontent.com/Ombi-app/Ombi/gh-pages/img/android-chrome-512x512.png which can be moved into the app. The fonts are currently being served by Google Fonts, the WOFF font files would need to be moved into the app assets and referenced as font-face rules instead. The Google Play image badge can be self hosted, but it looks like someone made the Google Play badge language aware and dynamically configures the path with the language set to serve a translated badge (Google hosts many language specific versions). You can see this on the user preferences page. Replicating this would mean self hosting a lot of versions of the Google Play badge to keep this. behaviour. Lines 59 to 61 in 9d54543
There is also duplication of the app store badges on two different screens which could possibly do with being referenced as it's own template file to be included in both, without duplicating. |
This is German Article about bad experience of using even Google fonts: https://www.golem.de/news/google-fonts-abmahnungen-an-webseitenbetreiber-mit-google-schriftarten-2208-167472.html |
This is not something that's top of the priority list for me, but I'd be happy for any pull requests |
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
All Fonts and Pictures must be part of the local OMBI resources.
Desktop (please complete the following information):
Ombi Version (please complete the following information):
The text was updated successfully, but these errors were encountered: