From: Joe Perches <joe@perches.com>
To: Jonathan Corbet <corbet@lwn.net>,
"Alexander A. Klimov" <grandmaster@al2klimov.de>
Cc: mchehab+samsung@kernel.org, alexandre.belloni@bootlin.com,
nicolas.ferre@microchip.com, robh@kernel.org,
j.neuschaefer@gmx.net, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] Replace HTTP links with HTTPS ones: Documentation/arm
Date: Fri, 26 Jun 2020 15:01:31 -0700 [thread overview]
Message-ID: <58f25e61b285362ab28d14ac55d1cd632c460fa8.camel@perches.com> (raw)
In-Reply-To: <20200626150911.3d4f9ca7@lwn.net>
On Fri, 2020-06-26 at 15:09 -0600, Jonathan Corbet wrote:
> On Fri, 26 Jun 2020 21:44:08 +0200
> "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.
[]
> > Changes in v2:
> > Undone all handhelds.org changes and 0 of 0 wearablegroup.org changes.
>
> I wasn't asking that the changes be undone, I was asking that those links
> simply be removed. They are actively harmful - much more so than any http:
> links - and shouldn't be there. *Sigh*. I guess I'll just do that.
One argument to mark old/invalid links differently somehow is
that the wayback machine at archive.org may still have them.
But when the domain has been transferred to a 3rd party, it is
possibly harmful.
Another option might be to grab any archive.org content and
put it into a Documentation/archived/outdated directory or
the like.
For instance:
https://web.archive.org/web/20090423133742/http://www.handhelds.org/projects/h1940.html
Then gain, this might as well be prehistoric content.
next prev parent reply other threads:[~2020-06-26 22:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-26 19:44 Alexander A. Klimov
2020-06-26 21:09 ` Jonathan Corbet
2020-06-26 22:01 ` Joe Perches [this message]
2020-06-27 7:10 ` Alexander A. Klimov
2020-06-29 18:36 ` Jonathan Corbet
2020-07-08 12:44 ` Nicolas Ferre
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=58f25e61b285362ab28d14ac55d1cd632c460fa8.camel@perches.com \
--to=joe@perches.com \
--cc=alexandre.belloni@bootlin.com \
--cc=corbet@lwn.net \
--cc=grandmaster@al2klimov.de \
--cc=j.neuschaefer@gmx.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+samsung@kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=robh@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
all inboxes | Powered by JetHome®