From: "Serge E. Hallyn" <serge@hallyn.com>
To: Paul Moore <paul@paul-moore.com>
Cc: Ariel Otilibili <ariel.otilibili-anieli@eurecom.fr>,
linux-security-module@vger.kernel.org,
Serge Hallyn <serge@hallyn.com>,
"Andrew G . Morgan" <morgan@kernel.org>
Subject: Re: [PATCH 1/1] uapi: fix broken link in linux/capability.h
Date: Tue, 1 Jul 2025 21:20:48 -0500 [thread overview]
Message-ID: <aGSXgF797s+Oz4C5@mail.hallyn.com> (raw)
In-Reply-To: <66376202561209641dad1c8894ec62cb@paul-moore.com>
On Tue, Jul 01, 2025 at 10:05:45PM -0400, Paul Moore wrote:
> On Jun 29, 2025 Ariel Otilibili <ariel.otilibili-anieli@eurecom.fr> wrote:
> >
> > The link to the libcap library is outdated:
> >
> > > $ curl "https://www.kernel.org/pub/linux/libs/security/linux-privs/kernel-2.6/"
> > >
> > > <html>
> > > <head><title>Index of /pub/linux/libs/security/linux-privs/kernel-2.6/</title></head>
> > > <body>
> > > <h1>Index of /pub/linux/libs/security/linux-privs/kernel-2.6/</h1><hr><pre><a href="../">../</a>
> > > </pre><hr></body>
> > > </html>
> >
> > Instead, use a link to the libcap2 library:
> >
> > > $ curl "https://www.kernel.org/pub/linux/libs/security/linux-privs/libcap2/"
> > >
> > > <html>
> > > <head><title>Index of /pub/linux/libs/security/linux-privs/libcap2/</title></head>
> > > <body>
> > > <h1>Index of /pub/linux/libs/security/linux-privs/libcap2/</h1><hr><pre><a href="../">../</a>
> > > <a href="old/">old/</a> 08-Nov-2007 06:34 -
> > > <a href="libcap-2.00.tar.gz">libcap-2.00.tar.gz</a> 11-Jan-2014 16:49 37K
> > > <a href="libcap-2.00.tar.sign">libcap-2.00.tar.sign</a> 11-Jan-2014 16:49 819
> > > [...]
> > > <a href="libcap-2.76.tar.sign">libcap-2.76.tar.sign</a> 13-Apr-2025 18:20 833
> > > <a href="libcap-2.76.tar.xz">libcap-2.76.tar.xz</a> 13-Apr-2025 18:20 195K
> > > <a href="sha256sums.asc">sha256sums.asc</a> 13-Apr-2025 18:25 14K
> > > </pre><hr></body>
> > > </html>
> >
> > As well, give the complete reference of the POSIX compliance.
> >
> > Signed-off-by: Ariel Otilibili <ariel.otilibili-anieli@eurecom.fr>
> > Acked-by: Andrew G. Morgan <morgan@kernel.org>
> > ---
> > Cc: Serge Hallyn <serge@hallyn.com>
> > Cc: Andrew G. Morgan <morgan@kernel.org>
> > ---
> > include/uapi/linux/capability.h | 5 +++--
> > 1 file changed, 3 insertions(+), 2 deletions(-)
>
> My personal preference would be for a commit description that doesn't
> wrap when running 'git log' on a 80 char wide terminal, but ultimately
Agreed. Would you mind updating that, and then I'll pull it in?
thanks,
-serge
> that is Serge's call to make. Otherwise, the updated URL looks good to
> me.
>
> Reviewed-by: Paul Moore <paul@paul-moore.com>
>
> --
> paul-moore.com
next prev parent reply other threads:[~2025-07-02 2:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-29 12:03 [PATCH 0/1] uapi: fix broken link in linux/capability.h Ariel Otilibili
2025-06-29 12:03 ` [PATCH 1/1] " Ariel Otilibili
2025-06-29 14:27 ` Andrew G. Morgan
2025-06-29 23:16 ` Ariel Otilibili-Anieli
2025-07-02 2:05 ` Paul Moore
2025-07-02 2:20 ` Serge E. Hallyn [this message]
2025-07-02 10:05 ` Ariel Otilibili-Anieli
2025-07-05 0:25 ` sergeh
2025-07-02 10:00 ` [PATCH v2 0/1] " Ariel Otilibili
2025-07-02 10:00 ` [PATCH v2 1/1] " Ariel Otilibili
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=aGSXgF797s+Oz4C5@mail.hallyn.com \
--to=serge@hallyn.com \
--cc=ariel.otilibili-anieli@eurecom.fr \
--cc=linux-security-module@vger.kernel.org \
--cc=morgan@kernel.org \
--cc=paul@paul-moore.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.