Bug 1671670
| Summary: | [RFE] Allow user names to be numeric when the SHADOW_ALLOW_ALL_NUMERIC_USER environment variable is set [rhel-7.6.z] | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | RAD team bot copy to z-stream <autobot-eus-copy> |
| Component: | shadow-utils | Assignee: | Tomas Mraz <tmraz> |
| Status: | CLOSED ERRATA | QA Contact: | Filip Dvorak <fdvorak> |
| Severity: | high | Docs Contact: | Mirek Jahoda <mjahoda> |
| Priority: | high | ||
| Version: | 7.6 | CC: | dapospis, mjahoda |
| Target Milestone: | rc | Keywords: | FutureFeature, Reopened, ZStream |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | shadow-utils-4.1.5.1-25.el7_6.1 | Doc Type: | Release Note |
| Doc Text: |
The useradd and groupadd commands disallow user and group names consisting purely of numeric characters since Red Hat Enterprise Linux 7.6. The reason for not allowing such names is that this can confuse potentially many tools that work with user and group names and user and group ids (which are numbers). However due to some deployments depending on allowing all-numeric user names this erratum makes useradd and groupadd commands to allow all-numeric user and group names if environment variable SHADOW_ALLOW_ALL_NUMERIC_USER is set. Please note that the all-numeric user and group names are deprecated in Red Hat Enterprise Linux 7 and the support will be completely removed in Red Hat Enterprise Linux 8.
|
Story Points: | --- |
| Clone Of: | 1651450 | Environment: | |
| Last Closed: | 2019-03-13 18:45:52 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1651450 | ||
| Bug Blocks: | |||
|
Description
RAD team bot copy to z-stream
2019-02-01 08:57:46 UTC
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, 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/RHEA-2019:0507 |