util-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: L A Walsh <lkml@tlinx.org>
To: Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org
Subject: Re: Bug: mount doing bad security check: only root can use -types, (effective EUID is 5013)
Date: Tue, 06 Jun 2017 07:15:01 -0700	[thread overview]
Message-ID: <5936B8E5.8050901@tlinx.org> (raw)
In-Reply-To: <20170606093607.xrxel4ny4hjoe4iv@ws.net.home>

Karel Zak wrote:
> ruid = getuid();
>     euid = geteuid();
>
>     cxt->restricted = (uid_t) 0 == ruid && ruid == euid ? 0 : 1;
>
> in your case geteuid() returns 5013.
>   
----
    But my EUID isn't 5013 ("LOGINUID" is). That's the complaint/bug. 
I looked at 'id': it doesn't show euid:

Ishtar:/tmp> sudo bash -c 'id; echo "UID=$UID, EUID=$EUID"; /bin/mount 
devpts /tmp/mnt -t devpts'
uid=0(root) gid=0(root) groups=...
UID=0, EUID=0
mount: only root can use "--types" option (effective UID is 5013)

I also mentioned I'm using
'sudo', which also sets both the UID & EUID to the new USER (unless
you go out of your way to configure it not to do so -- in which case
many things don't function normally -- including bash which would
operate in restricted mode (like rbash).




  reply	other threads:[~2017-06-06 14:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-05 23:07 Bug: mount doing bad security check: only root can use -types, (effective EUID is 5013) L A Walsh
2017-06-06  9:36 ` Karel Zak
2017-06-06 14:15   ` L A Walsh [this message]
2017-06-06 15:10     ` Karel Zak
2017-06-06 15:11     ` L A Walsh
2017-06-06 15:21       ` Tilman Schmidt
2017-06-06 16:03         ` Karel Zak
2017-06-06 16:10         ` L A Walsh
2017-06-06 17:12           ` Patch: ensure mount & umount are root-owned before setting SUID bit L A Walsh
2017-06-20 11:14             ` Karel Zak

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=5936B8E5.8050901@tlinx.org \
    --to=lkml@tlinx.org \
    --cc=kzak@redhat.com \
    --cc=util-linux@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).