Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionMichael Vollmer
2021-10-11 16:09:43 UTC
Description of problem:
If a user wants to manually manage the sub[ug]id ranges before he creates the users those changes don't get reflected in /etc/subuid and /etc/subgid
Version-Release number of selected component (if applicable):
# rpm -qa|grep shado
shadow-utils-4.6-12.el8.x86_64
How reproducible:
always
Steps to Reproduce:
1. echo container:493216:65536 >> /etc/subuid
echo container:493216:65536 >> /etc/subgid
2. useradd container
3. cat /etc/subuid
container:493216:65536
container:558752:65536
Actual results:
I see two independent entries for the same user with different ranges. The first one is the expected one which I put manually. The second one comes from useradd and is auto generated.
According to the man page of useradd this should NOT happen:
SUB_GID_MIN (number), SUB_GID_MAX (number), SUB_GID_COUNT (number)
If /etc/subuid exists, the commands useradd and newusers (unless the user already have subordinate group IDs) allocate SUB_GID_COUNT unused group IDs from the range SUB_GID_MIN to SUB_GID_MAX for each new
user.
The default values for SUB_GID_MIN, SUB_GID_MAX, SUB_GID_COUNT are respectively 100000, 600100000 and 65536.
SUB_UID_MIN (number), SUB_UID_MAX (number), SUB_UID_COUNT (number)
If /etc/subuid exists, the commands useradd and newusers (unless the user already have subordinate user IDs) allocate SUB_UID_COUNT unused user IDs from the range SUB_UID_MIN to SUB_UID_MAX for each new
user.
I want to highlight "unless the user already have subordinate group/user IDs"
Expected results:
useradd honors the predefined values in /etc/subuid, /etc/subgid and doesn't add different values for the new created user.
Additional info:
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Low: shadow-utils security and bug fix update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2023:7112
Description of problem: If a user wants to manually manage the sub[ug]id ranges before he creates the users those changes don't get reflected in /etc/subuid and /etc/subgid Version-Release number of selected component (if applicable): # rpm -qa|grep shado shadow-utils-4.6-12.el8.x86_64 How reproducible: always Steps to Reproduce: 1. echo container:493216:65536 >> /etc/subuid echo container:493216:65536 >> /etc/subgid 2. useradd container 3. cat /etc/subuid container:493216:65536 container:558752:65536 Actual results: I see two independent entries for the same user with different ranges. The first one is the expected one which I put manually. The second one comes from useradd and is auto generated. According to the man page of useradd this should NOT happen: SUB_GID_MIN (number), SUB_GID_MAX (number), SUB_GID_COUNT (number) If /etc/subuid exists, the commands useradd and newusers (unless the user already have subordinate group IDs) allocate SUB_GID_COUNT unused group IDs from the range SUB_GID_MIN to SUB_GID_MAX for each new user. The default values for SUB_GID_MIN, SUB_GID_MAX, SUB_GID_COUNT are respectively 100000, 600100000 and 65536. SUB_UID_MIN (number), SUB_UID_MAX (number), SUB_UID_COUNT (number) If /etc/subuid exists, the commands useradd and newusers (unless the user already have subordinate user IDs) allocate SUB_UID_COUNT unused user IDs from the range SUB_UID_MIN to SUB_UID_MAX for each new user. I want to highlight "unless the user already have subordinate group/user IDs" Expected results: useradd honors the predefined values in /etc/subuid, /etc/subgid and doesn't add different values for the new created user. Additional info: