All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Weiner <hannes@saeurebad.de>
To: Markku Savela <msa@moth.iki.fi>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Radical idea? Remove all automatic privilege escalation base on executable file attributes!
Date: Fri, 08 Aug 2008 13:00:55 +0200	[thread overview]
Message-ID: <877iar4vq0.fsf@skyscraper.fehenstaub.lan> (raw)
In-Reply-To: <87abfn94rs.fsf@burp.tkv.asdf.org> (Markku Savela's message of "Fri, 08 Aug 2008 13:31:51 +0300")

Hi,

Markku Savela <msa@moth.iki.fi> writes:

> That is, remove
>
>  - setuid/setgid feature from Linux
>
>  - cancel the capability attributes in files (or only only allow
>    downgrading of capabilities)
>
> (e.g. mount everything as nosuid or something, but eventually, the
> code could be removed from the kernel)
>
> The only way to escalate privileges would be to request starting of
> the executable by some daemon (like upstart), which would grant or
> deny the request based totally on some user space policies.

Let's just hope then that this central facility is not buggy itself.
Because if that would be the only way to acquire privileges as
non-priviledged user, it is likely that every machine runs it.

Opposed to a bug in one setuid program that not everyone is even
garuanteed to have installed.

	Hannes

      reply	other threads:[~2008-08-08 11:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-08 10:31 Radical idea? Remove all automatic privilege escalation base on executable file attributes! Markku Savela
2008-08-08 11:00 ` Johannes Weiner [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=877iar4vq0.fsf@skyscraper.fehenstaub.lan \
    --to=hannes@saeurebad.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=msa@moth.iki.fi \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.