[lkml]   [2020]   [Jun]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH v2] Replace HTTP links with HTTPS ones: Documentation/arm

Am 26.06.20 um 23:09 schrieb Jonathan Corbet:
> On Fri, 26 Jun 2020 21:44:08 +0200
> "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 both the HTTP and HTTPS versions
>> return 200 OK and serve the same content:
>> Replace HTTP with HTTPS.
>> Signed-off-by: Alexander A. Klimov <>
>> ---
>> Changes in v2:
>> Undone all changes and 0 of 0 changes.
> I wasn't asking that the changes be undone, I was asking that those links
> simply be removed. They are actively harmful - much more so than any http:
> links - and shouldn't be there. *Sigh*. I guess I'll just do that.
You know what: I totally agree with you! They are actively harmful and
shall not be there. End of story.

But *why* you don't let me work step-by-step and *focus on one task* at
a time?

I.e. focus (for now) on HTTP links which shall stay in the kernel tree
rather than on the ones which shall not.

IMAO both domains have literally nothing to do with e.g. the HTTPSified and

My trainers (employer) taught me to split commits (patches) per one
thing I've done. (What you asked for is a legit thing, but it's another

Also *after* finishing my current todo list I'll think about automating
the detection of such. (This would have a much larger coverage.)

> jon

 \ /
  Last update: 2020-06-27 09:11    [W:0.112 / U:6.792 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site