public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: "Alexander A. Klimov" <grandmaster@al2klimov.de>
Cc: torvalds@linux-foundation.org, davej@codemonkey.org.uk,
	kvalo@codeaurora.org, luis.f.correia@gmail.com,
	cyphar@cyphar.com, paulburton@kernel.org, ribalda@kernel.org,
	martink@posteo.de, geert+renesas@glider.be,
	mchehab+samsung@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] CREDITS: replace HTTP links with HTTPS ones and add myself
Date: Fri, 10 Jul 2020 15:46:30 -0600	[thread overview]
Message-ID: <20200710154630.31521104@lwn.net> (raw)
In-Reply-To: <20200710194342.33107-1-grandmaster@al2klimov.de>

On Fri, 10 Jul 2020 21:43:42 +0200
"Alexander A. Klimov" <grandmaster@al2klimov.de> wrote:

> Regarding the links:
> 
> 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.
> 
> Regarding the addition of myself:

A couple of things here...

> Rationale:
> * 93431e0607e5

This is ... not particularly self-explanatory.  Is that meant to be a
commit reference?  If so, you would want to use the normal format.

> * the replaced links in this patch

If you are going to do something like make an addition to the file, you
need to do that separately from a cleanup patch.

But somebody has to say this: I don't think we have any sort of laid-down
policy for what it takes to be mentioned in CREDITS, but I don't think that
your work thus far clears whatever bar we might set.  We don't immortalize
every person who submits some cleanup patches, or this file would be a long
one indeed.  If you would like to be remembered for your kernel work, I
would respectfully suggest that you move beyond mechanical cleanups into
higher-level work.

One other little thing that jumped out at me:

>  N: Alan Cox
> -W: http://www.linux.org.uk/diary/
> +W: https://www.linux.org.uk/diary/
>  D: Linux Networking (0.99.10->2.0.29)
>  D: Original Appletalk, AX.25, and IPX code
>  D: 3c501 hacker

That link just redirects to linux.com, which is probably not what Alan had
in mind.  Replacing the link with one into the wayback machine (or perhaps
just removing it entirely) would seem like a more useful change than adding
HTTPS to a link that clearly does not reach the intended destination.

Thanks,

jon

  reply	other threads:[~2020-07-10 21:46 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-10 19:43 [PATCH] CREDITS: replace HTTP links with HTTPS ones and add myself Alexander A. Klimov
2020-07-10 21:46 ` Jonathan Corbet [this message]
2020-07-11  5:36   ` Alexander A. Klimov
2020-07-11  5:51   ` [PATCH] CREDITS: Replace HTTP links with HTTPS ones Alexander A. Klimov
2020-07-13 17:43     ` Jonathan Corbet
2020-07-13 22:12       ` Alexander A. Klimov
2020-07-13 22:46         ` Jonathan Corbet
2020-07-14 17:55       ` [PATCH v2] " Alexander A. Klimov
2020-07-14 19:39         ` [PATCH] CREDITS: remove link: http://www.cs.helsinki.fi/u/penberg/ Alexander A. Klimov
2020-07-14 19:39         ` [PATCH] CREDITS: remove link http://www.mathematik.uni-stuttgart.de/~floeff Alexander A. Klimov
2020-07-15  7:02           ` Philippe Mathieu-Daudé
2020-07-14 19:39         ` [PATCH] CREDITS: remove link: http://www.andante.org Alexander A. Klimov
2020-07-15  7:07           ` Philippe Mathieu-Daudé
2020-07-23 20:54         ` [PATCH v2] CREDITS: Replace HTTP links with HTTPS ones Jonathan Corbet
2020-07-14 19:38       ` [PATCH] CREDITS: remove link http://www.dementia.org/~shadow Alexander A. Klimov
2020-07-14 21:47         ` Jonathan Corbet
2020-07-14 21:56           ` Randy Dunlap
2020-07-15  6:23           ` Christian Kujau
2020-07-15 17:56         ` Marc Dionne

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=20200710154630.31521104@lwn.net \
    --to=corbet@lwn.net \
    --cc=cyphar@cyphar.com \
    --cc=davej@codemonkey.org.uk \
    --cc=geert+renesas@glider.be \
    --cc=grandmaster@al2klimov.de \
    --cc=kvalo@codeaurora.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luis.f.correia@gmail.com \
    --cc=martink@posteo.de \
    --cc=mchehab+samsung@kernel.org \
    --cc=paulburton@kernel.org \
    --cc=ribalda@kernel.org \
    --cc=torvalds@linux-foundation.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