From: Mike Frysinger <vapier@gentoo.org>
To: "Frank Ch. Eigler" <fche@elastic.org>
Cc: Overseers mailing list <overseers@sourceware.org>
Subject: Re: Content-Security-Policy on sourceware.org breaking HTML manuals
Date: Sun, 24 Dec 2023 21:01:55 -0500 [thread overview]
Message-ID: <ZYjik8pHpNrC_i5N@vapier> (raw)
In-Reply-To: <ZYjZVt5EDr5yBNMM@elastic.org>
[-- Attachment #1: Type: text/plain, Size: 1231 bytes --]
On 24 Dec 2023 20:22, Frank Ch. Eigler wrote:
> > tl;dr: can we add "; style-src 'unsafe-inline' http: https:" to
> > sourceware.org's CSP header ?
>
> There are a couple of ways in which this can be configured. For
> example, if you identify a URL location hierarchy where this would
> help, we can add it to the whitelist in sourceware-GENERAL.conf L32.
unfortunately, projects don't seem to be consistent here. maybe if we
declared a rule like **/manual/** would allow inline csp, we could get
people to harmonize on a common layout (and leave symlinks for the old
paths so we don't break people).
quick survey of some projects ...
binutils: https://sourceware.org/binutils/docs*/**
bzip2: https://sourceware.org/bzip2/manual/**
cgen: https://sourceware.org/cgen/docs*/**
gdb: https://sourceware.org/gdb/current/onlinedocs/**
glibc: https://sourceware.org/glibc/manual/**
newlib: https://sourceware.org/newlib/lib*.html
(although i'm trying to change newlib to a manual/** system)
psim: https://sourceware.org/psim/manual/**
sid: https://sourceware.org/sid/**
sim: https://sourceware.org/gdb/sim/manual/**
(i haven't published this yet)
-mike
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-12-25 2:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-25 1:15 Mike Frysinger
2023-12-25 1:22 ` Frank Ch. Eigler
2023-12-25 2:01 ` Mike Frysinger [this message]
2023-12-25 9:28 ` Frank Ch. Eigler
2023-12-27 6:39 ` Mike Frysinger
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZYjik8pHpNrC_i5N@vapier \
--to=vapier@gentoo.org \
--cc=fche@elastic.org \
--cc=overseers@sourceware.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).