From: Austin Gonyou <austin@coremetrics.com>
To: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Max groups at 32?
Date: 03 Jun 2002 22:31:44 -0500 [thread overview]
Message-ID: <1023161504.4595.5.camel@UberGeek> (raw)
[-- Attachment #1: Type: text/plain, Size: 1315 bytes --]
I'm not sure if this is a Linux capabilities problem, a PAM problem, or
what, but I've noticed that If I add a user to > 32 groups...that user
cannot access anything in a directory owned by a group > the 32nd group.
Has anyone else experienced this?
Here is a sample script to help troubleshoot if you're interested:
#!/bin/bash
x=34;
useradd testuser
while [ ! $x -lt 1 ]
do groupadd group$x
gpasswd -a testuser group$x
x=$(( $x - 1 ))
done
groups
read
printf "press any key..."
groups testuser
printf "press any key..."
read
mkdir /testdir
chown root:group1 /testdir
chmod 770 /testdir
su - testuser -c "ls /testdir"
printf "press any key..."
read
userdel -r testuser
If all has gone properly, and group1 is *not* in the first groups
listing, (not "groups testuser"), then the user will not be able to even
ls /testdir, and you'll get permission denied.
Please advise, if you can.
TIA.
--
Austin Gonyou
Systems Architect, CCNA
Coremetrics, Inc.
Phone: 512-698-7250
email: austin@coremetrics.com
"One ought never to turn one's back on a threatened danger and
try to run away from it. If you do that, you will double the danger.
But if you meet it promptly and without flinching, you will
reduce the danger by half."
Sir Winston Churchill
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 232 bytes --]
next reply other threads:[~2002-06-04 3:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-04 3:31 Austin Gonyou [this message]
2002-06-04 3:39 ` Max groups at 32? Jeff Garzik
2002-06-04 21:05 ` Tomasz Kłoczko
2002-06-04 21:18 ` Tim Hockin
2002-06-04 21:24 ` David S. Miller
2002-06-04 21:38 ` Tim Hockin
2002-06-04 21:57 ` Tim Hockin
2002-06-04 21:40 ` Trond Myklebust
2002-06-04 3:53 ` Andreas Dilger
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=1023161504.4595.5.camel@UberGeek \
--to=austin@coremetrics.com \
--cc=linux-kernel@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