From: "Michael Ströder" <michael@stroeder.com> To: galene@lists.galene.org Subject: [Galene] Re: "This operation is insecure" Date: Thu, 28 Jan 2021 14:11:37 +0100 [thread overview] Message-ID: <43b9a09b-da17-9efc-fa69-71b1fe616c56@stroeder.com> (raw) In-Reply-To: <87ft2m9hve.wl-jch@irif.fr> On 1/27/21 10:42 PM, Juliusz Chroboczek wrote: > Perhaps you could explain why you are munging the headers in the frontend. > Is there an actual attack that you're concerned about? I remember various pen-testing talks about attacking even via rogue frames, CSS files and fonts, depending on browser versions. So it's IMHO good practice to disable everything not really needed (least-privilege). Same spirit why I'm using systemd's sand-boxing options [1] and an AppArmor profile [2]. What you could do to prevent some of the attacks is to use Subresource Integrity Hashes in HTML source [3]. Yes, it requires you to commit the correct hashes in galene.html when changing any CSS, JS, font files included from there. > 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. Agreed. Avoiding attacks is a primary goal for you as a developer of a network service. And I appreciate that you take care. But you cannot influence the client side or fix issues yet unknown. E.g. the AppArmor profile is IMHO definitely a good mitigation against recent sudo attack vector or similar. Yes, I've already updated sudo on my systems. But we all learned about this only two days ago. The AppArmor profile was in place before. I'm super-concerned of this whole video conferencing stuff. Bad people can do really weird stuff with this great tool. We had some cases here in Germany were *very* inappropriate content was sent to pupils of an elementary school during an online lesson. :-( So better safe, than sorry. Ciao, Michael. P.S.: Yes, of course one of the Safari users asked me: "Why don't you use Zoom?" (sigh...). [1] https://build.opensuse.org/package/view_file/home:stroeder:network/galene/galene.service?expand=1 [2] https://build.opensuse.org/package/view_file/home:stroeder:network/galene/apparmor-usr.sbin.galene?expand=1 [3] https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity
next prev parent reply other threads:[~2021-01-28 13:11 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 2021-01-27 22:15 ` Michael Ströder 2021-01-28 13:11 ` Michael Ströder [this message] 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=43b9a09b-da17-9efc-fa69-71b1fe616c56@stroeder.com \ --to=michael@stroeder.com \ --cc=galene@lists.galene.org \ --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