From: Masami Hiramatsu <mhiramat@kernel.org>
To: "Naveen N. Rao" <naveen.n.rao@linux.ibm.com>
Cc: "Alexander A. Klimov" <grandmaster@al2klimov.de>,
anil.s.keshavamurthy@intel.com, corbet@lwn.net,
davem@davemloft.net, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
Ananth N Mavinakayanahalli <ananth@linux.ibm.com>
Subject: Re: [PATCH] Replace HTTP links with HTTPS ones: kprobes
Date: Mon, 13 Jul 2020 23:20:11 +0900 [thread overview]
Message-ID: <20200713232011.da584d6f7147b54ba083556f@kernel.org> (raw)
In-Reply-To: <1594388442.4mjtjyic5z.naveen@linux.ibm.com>
Hi Naveen and Alexander,
On Fri, 10 Jul 2020 19:14:47 +0530
"Naveen N. Rao" <naveen.n.rao@linux.ibm.com> wrote:
> Masami Hiramatsu wrote:
> > On Tue, 7 Jul 2020 21:49:59 +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.
> >>
> >> Deterministic algorithm:
> >> For each file:
> >> If not .svg:
> >> For each line:
> >> If doesn't contain `\bxmlns\b`:
> >> For each link, `\bhttp://[^# \t\r\n]*(?:\w|/)`:
> >> If both the HTTP and HTTPS versions
> >> return 200 OK and serve the same content:
> >> Replace HTTP with HTTPS.
> >
> > OK, but it seems that some of them are disappeared :(
> >
> > http://www-106.ibm.com/developerworks/library/l-kprobes.html?ca=dgr-lnxw42Kprobe
> >
> > -> https://www.ibm.com/developerworks/library/l-kprobes/index.html
>
> That looks right.
>
> >
> > http://www.redhat.com/magazine/005mar05/features/kprobes/
> >
> > -> I can not find that.
>
> Ditto, we should drop that.
>
> >
> >> - http://www-users.cs.umn.edu/~boutcher/kprobes/
> >> - http://www.linuxsymposium.org/2006/linuxsymposium_procv2.pdf (pages 101-115)
> >
> > Both are not found.
>
> It looks like the first link is gone, but there seems to be a copy in
> the web archive:
> https://web.archive.org/web/20061106154519/http://www-users.cs.umn.edu/~boutcher/kprobes/
>
> I suppose we can drop that link.
>
> >
> > (OT, it seems http://www.linuxsymposium.org/ has been left from historical
> > Linux Symposium, we must remove it asap)
>
> Indeed, I think that link pointed to the Kprobes paper:
> https://www.kernel.org/doc/ols/2006/ols2006v2-pages-109-124.pdf
Ah, there is.
Thank you for the confirmation.
Alexander, can you update other urls instead of just replacing the http with https?
>
>
> - Naveen
>
--
Masami Hiramatsu <mhiramat@kernel.org>
next prev parent reply other threads:[~2020-07-13 14:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-07 19:49 [PATCH] Replace HTTP links with HTTPS ones: kprobes Alexander A. Klimov
2020-07-08 9:42 ` Masami Hiramatsu
2020-07-09 19:16 ` [PATCH] kprobes: Replace HTTP links with HTTPS ones Alexander A. Klimov
2020-07-13 15:40 ` Jonathan Corbet
2020-07-13 21:58 ` Alexander A. Klimov
2020-07-21 13:31 ` Masami Hiramatsu
2020-07-10 13:44 ` [PATCH] Replace HTTP links with HTTPS ones: kprobes Naveen N. Rao
2020-07-13 14:20 ` Masami Hiramatsu [this message]
2020-07-13 22:02 ` Alexander A. Klimov
2020-07-20 12:01 ` Masami Hiramatsu
2020-07-21 9:30 ` Naveen N. Rao
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=20200713232011.da584d6f7147b54ba083556f@kernel.org \
--to=mhiramat@kernel.org \
--cc=ananth@linux.ibm.com \
--cc=anil.s.keshavamurthy@intel.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=grandmaster@al2klimov.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=naveen.n.rao@linux.ibm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.