linux-kernel - Re: [PATCH] Replace HTTP links with HTTPS ones: Documentation/admin-guide

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <c776dba2-1be2-9296-cf79-4788a3eddfd0@al2klimov.de>
Date:   Mon, 22 Jun 2020 20:17:30 +0200
From:   "Alexander A. Klimov" <grandmaster@...klimov.de>
To:     Pavel Machek <pavel@...x.de>
Cc:     corbet@....net, changbin.du@...el.com, masahiroy@...nel.org,
        rostedt@...dmis.org, j.neuschaefer@....net,
        andy.shevchenko@...il.com, mchehab+samsung@...nel.org,
        logang@...tatee.com, abbotti@....co.uk, jacob.e.keller@...el.com,
        colin.king@...onical.com, gregkh@...uxfoundation.org,
        mgreer@...malcreek.com, tytso@....edu, jack@...e.cz,
        ebiggers@...gle.com, tglx@...utronix.de, akpm@...ux-foundation.org,
        paulmck@...nel.org, pawan.kumar.gupta@...ux.intel.com,
        jgross@...e.com, mike.kravetz@...cle.com, cohuck@...hat.com,
        jacek.anaszewski@...il.com, alex@...xanderweb.de,
        dwlsalmeida@...il.com, dsterba@...e.com, linux-doc@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Replace HTTP links with HTTPS ones:
 Documentation/admin-guide



Am 22.06.20 um 00:04 schrieb Pavel Machek:
> Hi!
> 
>> Rationale:
>> Reduces attack surface on kernel devs opening the links for MITM
>> as HTTPS traffic is much harder to manipulate.
> 
>> +++ b/Documentation/admin-guide/README.rst
>> @@ -1,6 +1,6 @@
>>   .. _readme:
>>   
>> -Linux kernel release 5.x <http://kernel.org/>
>> +Linux kernel release 5.x <https://kernel.org/>
>>   =============================================
>>
> 
> You need to add one "=" here, IIRC.
OK, forget this mail thread. I've corrected this and am going to submit 
a replacement patch.

> 									Pavel
>