From: Finn Thain <fthain@telegraphics.com.au>
To: "Alexander A. Klimov" <grandmaster@al2klimov.de>
Cc: geert@linux-m68k.org, funaho@jurai.org,
linux-m68k@lists.linux-m68k.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] m68k: Replace HTTP links with HTTPS ones
Date: Sun, 19 Jul 2020 17:51:03 +1000 (AEST) [thread overview]
Message-ID: <alpine.LNX.2.23.453.2007191659150.8@nippy.intranet> (raw)
In-Reply-To: <d4c73203-56ed-820f-82ee-c239d7976d33@al2klimov.de>
On Sat, 18 Jul 2020, Alexander A. Klimov wrote:
> *Sigh* ... yes, doing everything one nice day is better that doing just
> something right now.
I wasn't saying "do everything possible or else do nothing". I was trying
to point to the larger problem. The http links in the kernel source hardly
seem to matter when nothing I read on HTTPS links is trustworthy.
> But doing just something right now is better that doing nothing at all.
>
HTTPS is not new. MITM attack is as old as the Byzantian hills. Your
rationale for doing "something right now" is apparently that you trust the
people who maintain "kernel developers" browsers but mistrust the people
who maintain some network links and switches. That's fine and you should
set your policy accordingly. But you should not be surprised if others
have different threat models -- especially when you fail to offer an
actual case where this patch might have helped.
next prev parent reply other threads:[~2020-07-19 7:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 18:42 [PATCH] m68k: Replace HTTP links with HTTPS ones Alexander A. Klimov
2020-07-18 4:25 ` Finn Thain
2020-07-18 8:05 ` Alexander A. Klimov
2020-07-19 7:51 ` Finn Thain [this message]
2020-07-19 8:41 ` Alexander A. Klimov
2020-07-20 0:05 ` Finn Thain
2020-08-26 8:50 ` Geert Uytterhoeven
2020-08-26 18:52 ` [PATCH v2] " Alexander A. Klimov
2020-08-27 7:36 ` Geert Uytterhoeven
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=alpine.LNX.2.23.453.2007191659150.8@nippy.intranet \
--to=fthain@telegraphics.com.au \
--cc=funaho@jurai.org \
--cc=geert@linux-m68k.org \
--cc=grandmaster@al2klimov.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.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).