[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bf85e454-cccc-37ef-d55f-d44a5c5c51df@acm.org>
Date: Sun, 12 Jul 2020 12:52:02 -0700
From: Bart Van Assche <bvanassche@....org>
To: "Alexander A. Klimov" <grandmaster@...klimov.de>,
dledford@...hat.com, jgg@...pe.ca, linux-rdma@...r.kernel.org,
target-devel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] SCSI RDMA PROTOCOL (SRP) TARGET: Replace HTTP links with
HTTPS ones
On 2020-07-10 11:12, Alexander A. Klimov wrote:
> Am 10.07.20 um 16:22 schrieb Bart Van Assche:
>> 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?
>
> Not on all, just on the ones who open it.
Is changing every single HTTP URL in the kernel into a HTTPS URL the best
solution? Is this the only solution? Has it been considered to recommend
kernel developers who are concerned about MITM attacks to install a browser
extension like HTTPS Everywhere instead?
Thanks,
Bart.
Powered by blists - more mailing lists