From: Juliusz Chroboczek <jch@irif.fr> To: "Michael Ströder" <michael@stroeder.com> Cc: galene@lists.galene.org Subject: [Galene] Re: "This operation is insecure" Date: Wed, 27 Jan 2021 22:42:29 +0100 [thread overview] Message-ID: <87ft2m9hve.wl-jch@irif.fr> (raw) In-Reply-To: <61231ca5-474e-d180-391e-8f0b0ddb77d0@stroeder.com> > FWIW the Apache httpd config settings: > Header onsuccess unset Content-Security-Policy > Header always set Content-Security-Policy "base-uri 'self'; child-src > 'self'; connect-src 'self'; default-src 'self'; font-src 'self'; > form-action 'self'; frame-ancestors 'none'; frame-src 'none'; img-src > 'self' data:; media-src 'self'; object-src 'self'; script-src 'self'; > style-src 'self';" > Note that this worked just fine until recent update. I find that suprising. The "wss:" entry in connect-src was added back in the spring of 2020 because without it Galène wouldn't work on iPads. As to "media-src blob:", streaming videos from disk won't work without it. Perhaps you could explain why you are munging the headers in the frontend. Is there an actual attack that you're concerned about? If so, then we should think together about avoiding the attack, rather than having each user use their own idiosyncratic set of security-related headers. -- Juliusz
next prev parent reply other threads:[~2021-01-27 21:42 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-27 18:24 [Galene] " Michael Ströder 2021-01-27 18:52 ` [Galene] " Michael Ströder 2021-01-27 20:05 ` Juliusz Chroboczek 2021-01-27 20:08 ` Juliusz Chroboczek 2021-01-27 20:17 ` Michael Ströder 2021-01-27 20:30 ` Juliusz Chroboczek 2021-01-27 21:09 ` Michael Ströder 2021-01-27 21:12 ` Michael Ströder 2021-01-27 21:42 ` Juliusz Chroboczek [this message] 2021-01-27 22:15 ` Michael Ströder 2021-01-28 13:11 ` Michael Ströder 2021-01-28 16:16 ` Michael Ströder 2021-02-01 0:45 ` Juliusz Chroboczek 2021-02-01 9:10 ` Michael Ströder
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: https://lists.galene.org/postorius/lists/galene.lists.galene.org/ * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=87ft2m9hve.wl-jch@irif.fr \ --to=jch@irif.fr \ --cc=galene@lists.galene.org \ --cc=michael@stroeder.com \ --subject='[Galene] Re: "This operation is insecure"' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox