From: "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: Daniel Lezcano <dlezcano-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
Cc: Linux Containers <containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>
Subject: Re: [patch 1/1][RFC] do not sys_reboot when not in init_pid_ns
Date: Tue, 4 Nov 2008 15:01:34 -0600 [thread overview]
Message-ID: <20081104210134.GA6238@us.ibm.com> (raw)
In-Reply-To: <4910B34B.7070901-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
Quoting Daniel Lezcano (dlezcano-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org):
> Daniel Hokka Zakrisson wrote:
> > Daniel Lezcano wrote:
> >
> > Wouldn't it be better to simply remove CAP_SYS_BOOT from containers
> > until sys_reboot emits some signal to userspace to restart/halt the
> > container? (This is what we do in Linux-VServer.)
>
> Ok, I will try, thanks.
>
> BTW, isn't possible that a process gave CAP_SYS_BOOT capability again to
> himself and being able to shutdown the host ? I guess I should remove
> CAP_SETPCAP too, no ?
No, remove it from your bounding set. You can never add bits back to
that set. prctl(PR_CAPBSET_DROP, CAP_SYS_BOOT);
-serge
next prev parent reply other threads:[~2008-11-04 21:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-02 0:00 [patch 1/1][RFC] do not sys_reboot when not in init_pid_ns Daniel Lezcano
[not found] ` <490CEDA0.6020800-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
2008-11-02 0:16 ` Daniel Hokka Zakrisson
2008-11-03 18:59 ` Dave Hansen
[not found] ` <54333.2001:16d8:ff15:101:219:d2ff:fed5:8193.1225584965.squirrel@intranet>
2008-11-02 23:04 ` Serge E. Hallyn
2008-11-04 20:40 ` Daniel Lezcano
[not found] ` <4910B34B.7070901-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
2008-11-04 21:01 ` Serge E. Hallyn [this message]
[not found] ` <20081104210134.GA6238-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2008-11-04 21:39 ` Daniel Lezcano
2008-11-04 22:14 ` Daniel Lezcano
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=20081104210134.GA6238@us.ibm.com \
--to=serue-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
--cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
--cc=dlezcano-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org \
/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