From: Austin Gonyou <austin@digitalroadkill.net>
To: linux-kernel@vger.kernel.org
Subject: [RFC] Groups beyond 32
Date: 17 Jul 2002 15:09:16 -0500 [thread overview]
Message-ID: <1026936556.25347.48.camel@UberGeek> (raw)
When changing the kernel to handle groups beyond 32, and of course the
glibc as well, I noticed that I could no longer SSH out of the box.
The problem with this is not huge, ask a few questions, some more
recompiling and then ssh will start working. Fine.
The problem now is more one of maintenance. Most distributions do not
support groups > 32 AFAIK. So, it's lead me to ask the following
questions:
1. Why, in general, is the limit so low?
For specific application, mainly auditing and such, this would be
advantageous I think.
2. What is required to limit the dependence on groups to just GLIBC or
just the kernel? Is that even possible?
3. Is there any true advantage to supporting more than 32 groups, or
creating "meta-groups" to get around the problem?
The main reason I ask, is because just like the unknown with ssh not
supporting > 32 groups without modification, there can be others. Plus
with most distros, using automated upgrades via push, or some such
mechanism is encumbered by customizations to glibc, ssh, and potentially
other packages.
--
Austin Gonyou <austin@digitalroadkill.net>
next reply other threads:[~2002-07-17 20:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-17 20:09 Austin Gonyou [this message]
2002-07-17 23:36 ` [RFC] Groups beyond 32 H. Peter Anvin
2002-07-17 23:42 ` Tim Hockin
2002-07-18 5:07 ` Austin Gonyou
-- strict thread matches above, loose matches on Subject: below --
2002-07-18 14:57 Jesse Pollard
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=1026936556.25347.48.camel@UberGeek \
--to=austin@digitalroadkill.net \
--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