Bug 1859252
| Summary: | [RFE] support pluggable data sources for subid ranges configurable via /etc/nsswitch.conf | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Phil Jasbutis <pjasbuti> |
| Component: | shadow-utils | Assignee: | Alexey Tikhonov <atikhono> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Anuj Borah <aborah> |
| Severity: | medium | Docs Contact: | Alexandra Nikandrova <anikandr> |
| Priority: | medium | ||
| Version: | 9.0 | CC: | aborah, anikandr, atikhono, bbaude, byodlows, cheimes, dapospis, dlavu, dornelas, dpal, dwalsh, fhirtz, fsayyed, grajaiya, gscrivan, gunther.mayer, ipedrosa, jhrozek, jligon, jnovy, lslebodn, lsm5, mheon, mzidek, pbrezina, rmanes, robert.zaage, sgoveas, smccarty, thalman, tscherf, tsweeney |
| Target Milestone: | beta | Keywords: | FutureFeature, Triaged |
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | sync-to-jira | ||
| Fixed In Version: | shadow-utils-4.8.1-9.el9 | Doc Type: | Enhancement |
| Doc Text: |
.The support for managing subID ranges is available in the shadow-utils
Previously, `shadow-utils` configured the subID ranges automatically from the `/etc/subuid` and `/etc/subgid` files. With this update, the configuration of subID ranges is available in the `/etc/nsswitch.conf` file by setting a value in the `subid` field. For more information, see `man subuid` and `man subgid`. Also, with this update, an SSSD implementation of the `shadow-utils` plugin is available, which provides the subID ranges from the IPA server. To use this functionality, add the `subid: sss` value to the `/etc/nsswitch.conf` file. This solution might be useful in the containerized environment to facilitate rootless containers.
Note that in case the `/etc/nsswitch.conf` file is configured by the `authselect` tool, you must follow the procedures described in the `authselect` documentation. When it is not the case, you can modify the `/etc/nsswitch.conf` file manually.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-12-07 21:20:54 UTC | Type: | Feature Request |
| 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: | 1989476, 2019921 | ||
| Bug Blocks: | 1186913 | ||
|
Description
Phil Jasbutis
2020-07-21 14:52:48 UTC
This is totally out of Podman's hands this request needs to be handled by shadow-utils/sssd we need a way of getting this information in Podman and newuidmap/newgidmap. We need Full discussion has been open for 1.5 years. https://github.com/shadow-maint/shadow/issues/154 Upstream tickets: * shadow-utils: https://github.com/shadow-maint/shadow/issues/154 * SSSD: https://github.com/SSSD/sssd/issues/5197 * FreeIPA: https://pagure.io/freeipa/issue/8361 Hi, I would even opt for a radically new handling of this issue in the Kernel itself: 1) Make "subuid/subgid" a primary citizen in the linux kernel - Each user can have the full range subuid 0...2^32-1, no need to allocate ranges and keep them disjunct 2) Make this a "secondary citizen" in the filesystem code (e.g. using xattr /acl) [primary citizen would be preferrable, but perhaps that needs very heavy changes] E.g. When accessing files, use both UID + SubUID for checking permissions. 2a) I do not know if extended attributes already are in NFS standards, e.g. see https://tools.ietf.org/html/rfc8276 from Dec. 2017) Both items also have more implications and architecture/design/implementation choices which need to be well-thought. This is just the high level idea. Of course this is not in the hand of podman, but would require kernel changes (the same happened for namespaces). Regards, Gunther e.g. the kernel already has Real_UID, Saved_UID, Effective_UID, so why not another "SubUID" ? Also realize that anytime you are playing with DAC (UIDs/GIDS) you are risking CVE Vulnerabilities. which means changes would take many YEARS to get implemeneted if ever. So I would rather deal with this in user space. https://github.com/shadow-maint/shadow/pull/321 was merged upstream |