Linux-Doc Archive on lore.kernel.org
 help / color / Atom feed
From: Masahiro Yamada <masahiroy@kernel.org>
To: "Alexander A. Klimov" <grandmaster@al2klimov.de>
Cc: Michal Marek <michal.lkml@markovi.net>,
	Jonathan Corbet <corbet@lwn.net>,
	Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
	"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	clang-built-linux <clang-built-linux@googlegroups.com>
Subject: Re: [PATCH for v5.9] kbuild: Replace HTTP links with HTTPS ones
Date: Sat, 1 Aug 2020 21:33:08 +0900
Message-ID: <CAK7LNAQywudK9hJLeAT+Z3HWt4bgR+Tf3PWWtqkc7LT=eKBMyA@mail.gmail.com> (raw)
In-Reply-To: <20200719194602.61387-1-grandmaster@al2klimov.de>

On Mon, Jul 20, 2020 at 4:46 AM 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 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>
> ---

Applied to linux-kbuild. Thanks.



>  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/kbuild/Kconfig.recursion-issue-02 |  2 +-
>  Documentation/kbuild/kconfig-language.rst       | 14 +++++++-------
>  Documentation/kbuild/llvm.rst                   |  2 +-
>  scripts/package/mkdebian                        |  2 +-
>  scripts/package/mkspec                          |  2 +-
>  5 files changed, 11 insertions(+), 11 deletions(-)
>
> diff --git a/Documentation/kbuild/Kconfig.recursion-issue-02 b/Documentation/kbuild/Kconfig.recursion-issue-02
> index b9fd56c4b57e..df245fd7670d 100644
> --- a/Documentation/kbuild/Kconfig.recursion-issue-02
> +++ b/Documentation/kbuild/Kconfig.recursion-issue-02
> @@ -42,7 +42,7 @@
>  # "select FW_LOADER" [0], in the end the simple alternative solution to this
>  # problem consisted on matching semantics with newly introduced features.
>  #
> -# [0] http://lkml.kernel.org/r/1432241149-8762-1-git-send-email-mcgrof@do-not-panic.com
> +# [0] https://lkml.kernel.org/r/1432241149-8762-1-git-send-email-mcgrof@do-not-panic.com
>
>  mainmenu "Simple example to demo cumulative kconfig recursive dependency implication"
>
> diff --git a/Documentation/kbuild/kconfig-language.rst b/Documentation/kbuild/kconfig-language.rst
> index a1601ec3317b..41bee6a171e3 100644
> --- a/Documentation/kbuild/kconfig-language.rst
> +++ b/Documentation/kbuild/kconfig-language.rst
> @@ -688,10 +688,10 @@ and real world requirements were not well understood. As it stands though
>  only reverse engineering techniques have been used to deduce semantics from
>  variability modeling languages such as Kconfig [3]_.
>
> -.. [0] http://www.eng.uwaterloo.ca/~shshe/kconfig_semantics.pdf
> -.. [1] http://gsd.uwaterloo.ca/sites/default/files/vm-2013-berger.pdf
> -.. [2] http://gsd.uwaterloo.ca/sites/default/files/ase241-berger_0.pdf
> -.. [3] http://gsd.uwaterloo.ca/sites/default/files/icse2011.pdf
> +.. [0] https://www.eng.uwaterloo.ca/~shshe/kconfig_semantics.pdf
> +.. [1] https://gsd.uwaterloo.ca/sites/default/files/vm-2013-berger.pdf
> +.. [2] https://gsd.uwaterloo.ca/sites/default/files/ase241-berger_0.pdf
> +.. [3] https://gsd.uwaterloo.ca/sites/default/files/icse2011.pdf
>
>  Full SAT solver for Kconfig
>  ~~~~~~~~~~~~~~~~~~~~~~~~~~~
> @@ -710,10 +710,10 @@ such efforts somehow on Kconfig. There is enough interest from mentors of
>  existing projects to not only help advise how to integrate this work upstream
>  but also help maintain it long term. Interested developers should visit:
>
> -http://kernelnewbies.org/KernelProjects/kconfig-sat
> +https://kernelnewbies.org/KernelProjects/kconfig-sat
>
> -.. [4] http://www.cs.cornell.edu/~sabhar/chapters/SATSolvers-KR-Handbook.pdf
> -.. [5] http://gsd.uwaterloo.ca/sites/default/files/vm-2013-berger.pdf
> +.. [4] https://www.cs.cornell.edu/~sabhar/chapters/SATSolvers-KR-Handbook.pdf
> +.. [5] https://gsd.uwaterloo.ca/sites/default/files/vm-2013-berger.pdf
>  .. [6] https://cados.cs.fau.de
>  .. [7] https://vamos.cs.fau.de
>  .. [8] https://undertaker.cs.fau.de
> diff --git a/Documentation/kbuild/llvm.rst b/Documentation/kbuild/llvm.rst
> index c776b6eee969..2aac50b97921 100644
> --- a/Documentation/kbuild/llvm.rst
> +++ b/Documentation/kbuild/llvm.rst
> @@ -76,7 +76,7 @@ Getting Help
>  Getting LLVM
>  -------------
>
> -- http://releases.llvm.org/download.html
> +- https://releases.llvm.org/download.html
>  - https://github.com/llvm/llvm-project
>  - https://llvm.org/docs/GettingStarted.html
>  - https://llvm.org/docs/CMake.html
> diff --git a/scripts/package/mkdebian b/scripts/package/mkdebian
> index df1adbfb8ead..48fbd3d0284a 100755
> --- a/scripts/package/mkdebian
> +++ b/scripts/package/mkdebian
> @@ -175,7 +175,7 @@ Section: kernel
>  Priority: optional
>  Maintainer: $maintainer
>  Build-Depends: bc, rsync, kmod, cpio, bison, flex | flex:native $extra_build_depends
> -Homepage: http://www.kernel.org/
> +Homepage: https://www.kernel.org/
>
>  Package: $packagename
>  Architecture: $debarch
> diff --git a/scripts/package/mkspec b/scripts/package/mkspec
> index 8640c278f1aa..7c477ca7dc98 100755
> --- a/scripts/package/mkspec
> +++ b/scripts/package/mkspec
> @@ -46,7 +46,7 @@ sed -e '/^DEL/d' -e 's/^\t*//' <<EOF
>         License: GPL
>         Group: System Environment/Kernel
>         Vendor: The Linux Community
> -       URL: http://www.kernel.org
> +       URL: https://www.kernel.org
>  $S     Source: kernel-$__KERNELRELEASE.tar.gz
>         Provides: $PROVIDES
>         %define __spec_install_post /usr/lib/rpm/brp-compress || :
> --
> 2.27.0
>


-- 
Best Regards
Masahiro Yamada

      reply index

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-19 19:46 Alexander A. Klimov
2020-08-01 12:33 ` Masahiro Yamada [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='CAK7LNAQywudK9hJLeAT+Z3HWt4bgR+Tf3PWWtqkc7LT=eKBMyA@mail.gmail.com' \
    --to=masahiroy@kernel.org \
    --cc=clang-built-linux@googlegroups.com \
    --cc=corbet@lwn.net \
    --cc=grandmaster@al2klimov.de \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.lkml@markovi.net \
    /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

Linux-Doc Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-doc/0 linux-doc/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-doc linux-doc/ https://lore.kernel.org/linux-doc \
		linux-doc@vger.kernel.org
	public-inbox-index linux-doc

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-doc


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git