From: Jesse Pollard <jesse@cats-chateau.net>
To: Dhruv Gami <gami@d10systems.com>,
Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>
Cc: linux-kernel@vger.kernel.org
Subject: Re: setgid - its current use
Date: Thu, 8 Apr 2004 09:08:28 -0500 [thread overview]
Message-ID: <04040809082800.04599@tabby> (raw)
In-Reply-To: <Pine.LNX.4.58.0404072304500.14350@d10systems.homelinux.com>
On Wednesday 07 April 2004 22:06, Dhruv Gami wrote:
> On Thu, 8 Apr 2004, Denis Vlasenko wrote:
> > On Thursday 08 April 2004 04:46, Dhruv Gami wrote:
> > > I'd like to know the possibility of using setgid for users to switch
> > > their groups and work as a member of a particular group. Essentially,
> > > if i want one user, who belongs to groups X, Y and Z to create a file
> > > as a member of group Y while he's logged on as a member of group X,
> > > would it be possible through setgid() ?
> >
> > it is possible through chmod
>
> but that would be an explicit way of doing it, right ? I'm looking for
> doing this via some system calls or something transparent to the user. At
> most I'd like to query the user for the group as which he wants to work.
> Which would essentially be a question I ask at login or beginning of a
> session.
You want the "newgrp" utility.
>From the manpage:
Newgrp changes the group identification of its caller, analogously to
login(1). The same person remains logged in, and the current directory
is unchanged, but calculations of access permissions to files are per-
formed with respect to the new group ID.
If no group is specified, the GID is changed to the login GID.
next prev parent reply other threads:[~2004-04-08 14:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-08 1:46 setgid - its current use Dhruv Gami
2004-04-08 7:41 ` Denis Vlasenko
2004-04-08 3:06 ` Dhruv Gami
2004-04-08 11:49 ` Miquel van Smoorenburg
2004-04-08 14:08 ` Jesse Pollard [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-04-08 17:40 Albert Cahalan
2004-04-09 1:46 ` Rob Couto
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=04040809082800.04599@tabby \
--to=jesse@cats-chateau.net \
--cc=gami@d10systems.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
/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.