linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: "Alexander A. Klimov" <grandmaster@al2klimov.de>
Cc: jack@suse.com, corbet@lwn.net, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] udf: Replace HTTP links with HTTPS ones
Date: Tue, 14 Jul 2020 14:38:06 +0200	[thread overview]
Message-ID: <20200714123806.GI23073@quack2.suse.cz> (raw)
In-Reply-To: <20200713200738.37800-1-grandmaster@al2klimov.de>

On Mon 13-07-20 22:07:38, Alexander A. Klimov 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 neither `\bgnu\.org/license`, nor `\bmozilla\.org/MPL\b`:
>             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>

Thanks. I've queued the patch to my tree.

								Honza

> ---
>  Continuing my work started at 93431e0607e5.
>  See also: git log --oneline '--author=Alexander A. Klimov <grandmaster@al2klimov.de>' v5.7..master
>  (Actually letting a shell for loop submit all this stuff for me.)
> 
>  If there are any URLs to be removed completely or at least not just HTTPSified:
>  Just clearly say so and I'll *undo my change*.
>  See also: https://lkml.org/lkml/2020/6/27/64
> 
>  If there are any valid, but yet not changed URLs:
>  See: https://lkml.org/lkml/2020/6/26/837
> 
>  If you apply the patch, please let me know.
> 
>  Sorry again to all maintainers who complained about subject lines.
>  Now I realized that you want an actually perfect prefixes,
>  not just subsystem ones.
>  I tried my best...
>  And yes, *I could* (at least half-)automate it.
>  Impossible is nothing! :)
> 
> 
>  Documentation/filesystems/udf.rst | 2 +-
>  fs/udf/ecma_167.h                 | 2 +-
>  fs/udf/super.c                    | 4 ++--
>  3 files changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/Documentation/filesystems/udf.rst b/Documentation/filesystems/udf.rst
> index d9badbf285b2..f9489ddbb767 100644
> --- a/Documentation/filesystems/udf.rst
> +++ b/Documentation/filesystems/udf.rst
> @@ -72,4 +72,4 @@ For the latest version and toolset see:
>  
>  Documentation on UDF and ECMA 167 is available FREE from:
>  	- http://www.osta.org/
> -	- http://www.ecma-international.org/
> +	- https://www.ecma-international.org/
> diff --git a/fs/udf/ecma_167.h b/fs/udf/ecma_167.h
> index 736ebc5dc441..185c3e247648 100644
> --- a/fs/udf/ecma_167.h
> +++ b/fs/udf/ecma_167.h
> @@ -2,7 +2,7 @@
>   * ecma_167.h
>   *
>   * This file is based on ECMA-167 3rd edition (June 1997)
> - * http://www.ecma.ch
> + * https://www.ecma.ch
>   *
>   * Copyright (c) 2001-2002  Ben Fennema
>   * Copyright (c) 2017-2019  Pali Rohár <pali@kernel.org>
> diff --git a/fs/udf/super.c b/fs/udf/super.c
> index f747bf72edbe..1c42f544096d 100644
> --- a/fs/udf/super.c
> +++ b/fs/udf/super.c
> @@ -11,8 +11,8 @@
>   *  This code is based on version 2.00 of the UDF specification,
>   *  and revision 3 of the ECMA 167 standard [equivalent to ISO 13346].
>   *    http://www.osta.org/
> - *    http://www.ecma.ch/
> - *    http://www.iso.org/
> + *    https://www.ecma.ch/
> + *    https://www.iso.org/
>   *
>   * COPYRIGHT
>   *  This file is distributed under the terms of the GNU General Public
> -- 
> 2.27.0
> 
-- 
Jan Kara <jack@suse.com>
SUSE Labs, CR

      reply	other threads:[~2020-07-14 12:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-13 20:07 [PATCH] udf: Replace HTTP links with HTTPS ones Alexander A. Klimov
2020-07-14 12:38 ` Jan Kara [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=20200714123806.GI23073@quack2.suse.cz \
    --to=jack@suse.cz \
    --cc=corbet@lwn.net \
    --cc=grandmaster@al2klimov.de \
    --cc=jack@suse.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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 NNTP newsgroup(s).