From: Willy Tarreau <wtarreau@free.fr>
To: nawilson@nawilson.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: PATCH] Allow setuid/setgid core files
Date: Sun, 21 Apr 2002 10:24:26 +0200 (CEST) [thread overview]
Message-ID: <200204210824.g3L8OR720085@ns.home.local> (raw)
Hello Neil,
I think I will try your patch since I have also had the same need
several times. In fact, not dumping a setuid core seems logical
for shared systems with lots of users, but on secured servers
which only host one daemon or two, and on which there's not any
user account, it's a bit annoying. In this case, if anyone gets
in the system, he's root anyway, so the initial protection
doesn't apply.
BTW, what uid/gid will the core get ? I think that it should get
the highest level so that if someone breaks in through a service
which uses this feature and which has dropped its uid/gid, at
least he cannot read eventual cores from previous attempts.
Comments ?
Willy
next reply other threads:[~2002-04-21 8:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-21 8:24 Willy Tarreau [this message]
2002-04-21 14:10 ` Neil A. Wilson
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=200204210824.g3L8OR720085@ns.home.local \
--to=wtarreau@free.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=nawilson@nawilson.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
all inboxes | Powered by JetHome®