Again... Tricky issue. Considering the precise bug you found, it comes
from the fact that the max [GU]ID was statically defined as 65,535. I'll
fix that easily, but I lack a generic way of detecting the actual system
maximum for gid_t. I guess I've found a hack that will work, though.
That will be for the next release. For now, stay with IDs below 65,535 -
anyway, defaults in /etc/login.defs are 60,000. Do you really need this,
or is that just a question of principles? ;-)
There's also a broader issue: the D-Bus protocol uses a 32-byte int for
[UG]IDs, because we use -1 to mean "none" when talking about main group.
So we cannot allow values above G_MAXINT32, which is 2,147,483,647. That
can be considered enough, though - but platforms often allow to reach
G_MAXUINT32, which is twice this limit, and could go further. This needs
a change in the protocol.
** Changed in: system-tools-backends (Ubuntu)
Importance: Undecided => Medium
** Changed in: system-tools-backends (Ubuntu)
Status: Confirmed => Triaged
** Also affects: liboobs (Ubuntu)
Importance: Undecided
Status: New
** Changed in: liboobs (Ubuntu)
Status: New => Triaged
** Changed in: liboobs (Ubuntu)
Importance: Undecided => Medium
--
problem with big uids in "Users and Groups" tool
https://bugs.launchpad.net/bugs/303997
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
