Linux Remote Processor Subsystem development
 help / color / mirror / Atom feed
From: Suman Anna <s-anna@ti.com>
To: "Alexander A. Klimov" <grandmaster@al2klimov.de>,
	<ohad@wizery.com>, <bjorn.andersson@linaro.org>,
	<linux-remoteproc@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Replace HTTP links with HTTPS ones: REMOTE PROCESSOR (REMOTEPROC) SUBSYSTEM
Date: Wed, 8 Jul 2020 13:53:36 -0500	[thread overview]
Message-ID: <f41ac867-e653-940d-374a-41e27f2697c3@ti.com> (raw)
In-Reply-To: <20200708153822.15031-1-grandmaster@al2klimov.de>

On 7/8/20 10:38 AM, 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>

Suggest a revision of patch title to
"remoteproc: Replace HTTP links with HTTPS ones"

With that,
Acked-by: Suman Anna <s-anna@ti.com>

> ---
>   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 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.
> 
> 
>   drivers/remoteproc/da8xx_remoteproc.c    | 2 +-
>   drivers/remoteproc/keystone_remoteproc.c | 2 +-
>   drivers/remoteproc/omap_remoteproc.c     | 2 +-
>   3 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/remoteproc/da8xx_remoteproc.c b/drivers/remoteproc/da8xx_remoteproc.c
> index 98e0be9476a4..9a4938c3025f 100644
> --- a/drivers/remoteproc/da8xx_remoteproc.c
> +++ b/drivers/remoteproc/da8xx_remoteproc.c
> @@ -27,7 +27,7 @@ MODULE_PARM_DESC(da8xx_fw_name,
>   
>   /*
>    * OMAP-L138 Technical References:
> - * http://www.ti.com/product/omap-l138
> + * https://www.ti.com/product/omap-l138
>    */
>   #define SYSCFG_CHIPSIG0 BIT(0)
>   #define SYSCFG_CHIPSIG1 BIT(1)
> diff --git a/drivers/remoteproc/keystone_remoteproc.c b/drivers/remoteproc/keystone_remoteproc.c
> index cd266163a65f..252ac6e2f653 100644
> --- a/drivers/remoteproc/keystone_remoteproc.c
> +++ b/drivers/remoteproc/keystone_remoteproc.c
> @@ -2,7 +2,7 @@
>   /*
>    * TI Keystone DSP remoteproc driver
>    *
> - * Copyright (C) 2015-2017 Texas Instruments Incorporated - http://www.ti.com/
> + * Copyright (C) 2015-2017 Texas Instruments Incorporated - https://www.ti.com/
>    */
>   
>   #include <linux/module.h>
> diff --git a/drivers/remoteproc/omap_remoteproc.c b/drivers/remoteproc/omap_remoteproc.c
> index 6955fab0a78b..d191610454d9 100644
> --- a/drivers/remoteproc/omap_remoteproc.c
> +++ b/drivers/remoteproc/omap_remoteproc.c
> @@ -2,7 +2,7 @@
>   /*
>    * OMAP Remote Processor driver
>    *
> - * Copyright (C) 2011-2020 Texas Instruments Incorporated - http://www.ti.com/
> + * Copyright (C) 2011-2020 Texas Instruments Incorporated - https://www.ti.com/
>    * Copyright (C) 2011 Google, Inc.
>    *
>    * Ohad Ben-Cohen <ohad@wizery.com>
> 


  reply	other threads:[~2020-07-08 18:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-08 15:38 [PATCH] Replace HTTP links with HTTPS ones: REMOTE PROCESSOR (REMOTEPROC) SUBSYSTEM Alexander A. Klimov
2020-07-08 18:53 ` Suman Anna [this message]
2020-07-08 19:25   ` [PATCH] remoteproc: Replace HTTP links with HTTPS ones Alexander A. Klimov

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=f41ac867-e653-940d-374a-41e27f2697c3@ti.com \
    --to=s-anna@ti.com \
    --cc=bjorn.andersson@linaro.org \
    --cc=grandmaster@al2klimov.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=ohad@wizery.com \
    /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