From: Alejandro Colomar <alx@kernel.org>
To: 孟敬姿 <mengjingzi@iie.ac.cn>
Cc: linux-man@vger.kernel.org, alx.manpages@gmail.com
Subject: Re: Recommendation for Adjusting Command Categorization in Manual Pages
Date: Sun, 11 Feb 2024 19:23:22 +0100 [thread overview]
Message-ID: <ZckQmoQvBn3GXX3i@debian> (raw)
In-Reply-To: <4199785d.2f13.18cf3132e26.Coremail.mengjingzi@iie.ac.cn>
[-- Attachment #1: Type: text/plain, Size: 2307 bytes --]
Hi Jingzi!
On Wed, Jan 10, 2024 at 07:12:49PM +0800, 孟敬姿 wrote:
> Hi! I hope this message finds you well.
>
> We have identified an issue in the categorization
> of certain commands in the man-pages and would like
> to bring it to your attention.
>
> Upon testing on Debian 11, we observed discrepancies
> between the stated privilege requirements in the manual
> pages and the actual behavior of some commands.
>
> According to the introduction pages, commands in section
> 8 require superuser privileges to run, but we found some
> commands that do not necessitate superuser privileges for
> execution:
> lnstat, findfs, blkid, lsblk, lsmod, lspci, modinfo,
> isosize, lastlog, tzselect, zdump, getcap, getpcaps,
> mklost_found, tracepath.
>
> These commands predominantly query system information and
> do not involve sensitive resources.
> For example, lnstat print Linux network statistics, the
> statics comes from /proc/net/stat which could be read by
> anyone. Lastlog reports the most recent login users, the
> similar commands like last, printky and users are all in
> section 1. And it is clearly stated in tracepath(8) that
> the command does not require superuser privileges.
>
> The introduction of section 1 claims that those commands
> to be user commands, but some commands require superuser
> privileges to run:
> dumpkeys, fgconsole, kbdindo, kbd_mode, showkey,
> deallocvt, tcpdump, chage, gpasswd, mesg, mkfifo.
>
> These commands manipulate special resources like keyboards,
> virtual terminals and pipes. Notably, tcpdump exists in both
> Section 1 and Section 8, but it can only be used with privileges.
>
> To enhance clarity and align with the intended privilege
> requirements, we recommend adjusting the categorization of these
> commands. This adjustment will ensure that users referring to
> the manual pages can accurately configure command permissions
> without unnecessary use of privileges and contribute to a more
> intuitive and accurate manual page structure.
>
> Best regards,
> Jingzi
Could you please suggest a specific patch to the manual pages?
Have a lovely day,
Alex
--
<https://www.alejandro-colomar.es/>
Looking for a remote C programming job at the moment.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2024-02-11 18:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 11:12 Recommendation for Adjusting Command Categorization in Manual Pages 孟敬姿
2024-02-11 18:23 ` Alejandro Colomar [this message]
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=ZckQmoQvBn3GXX3i@debian \
--to=alx@kernel.org \
--cc=alx.manpages@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=mengjingzi@iie.ac.cn \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).