From: Rob Landley <rob@landley.net>
To: "Alexander A. Klimov" <grandmaster@al2klimov.de>,
ysato@users.sourceforge.jp, dalias@libc.org, broonie@kernel.org,
sboyd@kernel.org, arnd@arndb.de, linux-sh@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] SUPERH: Replace HTTP links with HTTPS ones
Date: Sun, 12 Jul 2020 06:06:14 -0500 [thread overview]
Message-ID: <8b008a69-e73a-43cc-3dba-c1bce90c9902@landley.net> (raw)
In-Reply-To: <20200709021737.22667-1-grandmaster@al2klimov.de>
On 7/8/20 9:17 PM, Alexander A. Klimov wrote:
> diff --git a/arch/sh/Kconfig b/arch/sh/Kconfig
> index 9fc2b010e938..bc91bdb0b665 100644
> --- a/arch/sh/Kconfig
> +++ b/arch/sh/Kconfig
> @@ -74,7 +74,7 @@ config SUPERH
> The SuperH is a RISC processor targeted for use in embedded systems
> and consumer electronics; it was also used in the Sega Dreamcast
> gaming console. The SuperH port has a home page at
> - <http://www.linux-sh.org/>.
> + <https://www.linux-sh.org/>.
That's a historical page last edited in 2006 (according to
http://www.linux-sh.org/shwiki/RecentChanges/ anyway) with a self-signed
certificate that pops up a full page warning on chrome about the certificate
being invalid, in a wiki that can theoretically be edited by arbitrary third
parties anyway.
Not a huge man-in-the-middle target.
Rob
next prev parent reply other threads:[~2020-07-12 10:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-09 2:17 Alexander A. Klimov
2020-07-12 11:06 ` Rob Landley [this message]
2020-07-12 11:11 ` [PATCH] sh: " Alexander A. Klimov
2020-07-12 11:30 ` Rob Landley
2020-07-12 23:39 ` Rich Felker
2020-07-13 6:34 ` 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=8b008a69-e73a-43cc-3dba-c1bce90c9902@landley.net \
--to=rob@landley.net \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=dalias@libc.org \
--cc=grandmaster@al2klimov.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=sboyd@kernel.org \
--cc=ysato@users.sourceforge.jp \
/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®