mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: "Alexander A. Klimov" <grandmaster@al2klimov.de>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	"Daniel W. S. Almeida" <dwlsalmeida@gmail.com>,
	Al Viro <viro@zeniv.linux.org.uk>,
	Aleksa Sarai <cyphar@cyphar.com>, David Sterba <dsterba@suse.com>,
	Rob Herring <robh@kernel.org>,
	William Kucharski <william.kucharski@oracle.com>,
	"Matthew Wilcox (Oracle)" <willy@infradead.org>,
	John Hubbard <jhubbard@nvidia.com>,
	linux-fsdevel@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Replace HTTP links with HTTPS ones: Documentation/filesystems
Date: Fri, 26 Jun 2020 11:15:29 -0600	[thread overview]
Message-ID: <20200626111529.10e9e13b@lwn.net> (raw)
In-Reply-To: <20200621133552.46371-1-grandmaster@al2klimov.de>

On Sun, 21 Jun 2020 15:35:52 +0200
"Alexander A. Klimov" <grandmaster@al2klimov.de> wrote:

> Rationale:
> Reduces attack surface on kernel devs opening the links for MITM
> as HTTPS traffic is much harder to manipulate.
> 
> Deterministic algorithm:
> For each file:
>   If not .svg:
>     For each line:
>       If doesn't contain `\bxmlns\b`:
>         For each link, `\bhttp://[^# \t\r\n]*(?:\w|/)`:
>           If both the HTTP and HTTPS versions
>           return 200 OK and serve the same content:
>             Replace HTTP with HTTPS.
> 
> Signed-off-by: Alexander A. Klimov <grandmaster@al2klimov.de>
> ---
>  Documentation/filesystems/hfs.rst                    | 2 +-
>  Documentation/filesystems/hpfs.rst                   | 2 +-
>  Documentation/filesystems/nfs/rpc-server-gss.rst     | 6 +++---
>  Documentation/filesystems/path-lookup.rst            | 6 +++---
>  Documentation/filesystems/ramfs-rootfs-initramfs.rst | 8 ++++----
>  Documentation/filesystems/ubifs-authentication.rst   | 4 ++--
>  Documentation/filesystems/vfs.rst                    | 6 +++---
>  7 files changed, 17 insertions(+), 17 deletions(-)

I've applied this.  But some of the pages referenced here have not changed
in over 20 years; I suspect they may be just a wee bit out of date and not
entirely helpful for people trying to understand the kernel.  I *really*
wish we could be cleaning that stuff up rather than just changing URL
protocols...

Thanks,

jon

      reply	other threads:[~2020-06-26 17:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-21 13:35 Alexander A. Klimov
2020-06-26 17:15 ` Jonathan Corbet [this message]

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=20200626111529.10e9e13b@lwn.net \
    --to=corbet@lwn.net \
    --cc=cyphar@cyphar.com \
    --cc=dsterba@suse.com \
    --cc=dwlsalmeida@gmail.com \
    --cc=grandmaster@al2klimov.de \
    --cc=jhubbard@nvidia.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab+huawei@kernel.org \
    --cc=robh@kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    --cc=william.kucharski@oracle.com \
    --cc=willy@infradead.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

all inboxes | Powered by JetHome®