From: imp@bsdimp.com (Warner Losh)
Subject: [TUHS] Utility privs
Date: Sat, 28 Apr 2018 15:03:06 -0600 [thread overview]
Message-ID: <CANCZdfqF5oj=-qgCrt=oHSvEtkLQEGf4k=dyxEO5_HNwyGDDRA@mail.gmail.com> (raw)
In-Reply-To: <021201d3df11$6ba65fa0$42f31ee0$@ronnatalie.com>
On Sat, Apr 28, 2018 at 10:53 AM, Ron Natalie <ron at ronnatalie.com> wrote:
> Depending on the system PS may or may not need to be setuid to work by
> non-root users.
>
> Ping needs to be setuid because it uses raw sockets which are restricted
> (much like opening listens on low number ports) in many systems.
>
OSes could provide a controlled interface to ping, but there's not enough
of a win to do so.
Warner
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20180428/84a64901/attachment.html>
prev parent reply other threads:[~2018-04-28 21:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-28 16:53 Ron Natalie
2018-04-28 21:03 ` Warner Losh [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='CANCZdfqF5oj=-qgCrt=oHSvEtkLQEGf4k=dyxEO5_HNwyGDDRA@mail.gmail.com' \
--to=imp@bsdimp.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;
as well as URLs for NNTP newsgroup(s).