public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: Helge Kreutzmann <debian@helgefjell.de>
Cc: mario.blaettermann@gmail.com, linux-man@vger.kernel.org
Subject: Re: Issue in man page user_namespaces.7
Date: Sun, 4 Dec 2022 21:20:02 +0100	[thread overview]
Message-ID: <d527cf65-0015-8deb-9855-8d693b3cae88@gmail.com> (raw)
In-Reply-To: <20221204090720.GA1027@Debian-50-lenny-64-minimal>


[-- Attachment #1.1: Type: text/plain, Size: 904 bytes --]



On 12/4/22 10:07, Helge Kreutzmann wrote:
> Without further ado, the following was found:
> 
> Issue:    Text missing? in order to drop → in order to drop privileges?

 From what I read, I think it wanted to say "drop groups".

Fixed.  Thanks!

Cheers,

Alex

> 
> "/* Linux 3.19 made a change in the handling of setgroups(2) and the\n"
> "   \\(aqgid_map\\(aq file to address a security issue. The issue allowed\n"
> "   *unprivileged* users to employ user namespaces in order to drop\n"
> "   The upshot of the 3.19 changes is that in order to update the\n"
> "   \\(aqgid_maps\\(aq file, use of the setgroups() system call in this\n"
> "   user namespace must first be disabled by writing \"deny\" to one of\n"
> "   the /proc/PID/setgroups files for this namespace.  That is the\n"
> "   purpose of the following function. */\n"

-- 
<http://www.alejandro-colomar.es/>

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2022-12-04 20:20 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-04  9:07 Issue in man page user_namespaces.7 Helge Kreutzmann
2022-12-04 20:20 ` Alejandro Colomar [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-03-11 17:13 Helge Kreutzmann
2023-03-11 23:25 ` Alejandro Colomar
2023-03-12  5:06   ` Helge Kreutzmann
2023-03-12 10:55     ` Alejandro Colomar
2023-01-22 19:31 Helge Kreutzmann
2023-01-22 19:31 Helge Kreutzmann
2023-01-22 21:16 ` Alejandro Colomar
2022-12-04  9:07 Helge Kreutzmann
2022-12-04  9:07 Helge Kreutzmann
2022-12-04 20:14 ` Alejandro Colomar
2022-12-04  9:07 Helge Kreutzmann
2022-12-04 20:15 ` Alejandro Colomar
2022-12-04  9:07 Helge Kreutzmann
2022-12-04  9:07 Helge Kreutzmann
2022-03-13 12:34 Helge Kreutzmann
2022-03-13 12:34 Helge Kreutzmann
2022-03-13 12:34 Helge Kreutzmann
2022-03-13 12:34 Helge Kreutzmann

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=d527cf65-0015-8deb-9855-8d693b3cae88@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=debian@helgefjell.de \
    --cc=linux-man@vger.kernel.org \
    --cc=mario.blaettermann@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox