linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: "Alexander A. Klimov" <grandmaster@al2klimov.de>,
	dledford@redhat.com, jgg@ziepe.ca, linux-rdma@vger.kernel.org,
	target-devel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] SCSI RDMA PROTOCOL (SRP) TARGET: Replace HTTP links with HTTPS ones
Date: Fri, 10 Jul 2020 07:22:08 -0700	[thread overview]
Message-ID: <3d230abd-752e-8ac1-e18d-b64561b409ff@acm.org> (raw)
In-Reply-To: <20200709194820.27032-1-grandmaster@al2klimov.de>

On 2020-07-09 12:48, Alexander A. Klimov wrote:
> diff --git a/drivers/infiniband/ulp/srpt/Kconfig b/drivers/infiniband/ulp/srpt/Kconfig
> index 4b5d9b792cfa..f63b34d9ae32 100644
> --- a/drivers/infiniband/ulp/srpt/Kconfig
> +++ b/drivers/infiniband/ulp/srpt/Kconfig
> @@ -10,4 +10,4 @@ config INFINIBAND_SRPT
>  	  that supports the RDMA protocol. Currently the RDMA protocol is
>  	  supported by InfiniBand and by iWarp network hardware. More
>  	  information about the SRP protocol can be found on the website
> -	  of the INCITS T10 technical committee (http://www.t10.org/).
> +	  of the INCITS T10 technical committee (https://www.t10.org/).

It is not clear to me how modifying an URL in a Kconfig file helps to
reduce the attack surface on kernel devs?

Thanks,

Bart.



  reply	other threads:[~2020-07-10 14:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-09 19:48 [PATCH] SCSI RDMA PROTOCOL (SRP) TARGET: Replace HTTP links with HTTPS ones Alexander A. Klimov
2020-07-10 14:22 ` Bart Van Assche [this message]
2020-07-10 18:12   ` Alexander A. Klimov
2020-07-12 19:52     ` Bart Van Assche
2020-07-12 20:15       ` Alexander A. Klimov
2020-07-13 13:50         ` Jason Gunthorpe
2020-07-13 21:48           ` [PATCH v2] IB: " 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=3d230abd-752e-8ac1-e18d-b64561b409ff@acm.org \
    --to=bvanassche@acm.org \
    --cc=dledford@redhat.com \
    --cc=grandmaster@al2klimov.de \
    --cc=jgg@ziepe.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=target-devel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).