Conversation
Contributor
Author
|
This helps when people add static uids after the fact since it gives a save range that won't be used by userborn ever. |
nikstur
reviewed
Jul 25, 2026
nikstur
left a comment
nikstur
left a comment
Owner
There was a problem hiding this comment.
Thanks! This generally makes sense but it cannot be wired up in Nixpkgs right now because there is no option for it.
Sites that assign static IDs out of band (e.g. for NFS) need a range that userborn will never allocate from dynamically. login.defs already models this as UID_MIN/UID_MAX and GID_MIN/GID_MAX, which nixpkgs exposes via security.loginDefs.settings, so mirror that with separate normalUidRange/normalGidRange fields that the NixOS module can pass through directly.
Mic92
force-pushed
the
normal-id-range
branch
from
September 13, 2026 17:25
c0a5b1b to
4164c31
Compare
Mic92
added a commit
to TUM-DSE/nixpkgs
that referenced
this pull request
Sep 13, 2026
…nges
Userborn ignored `expires`, so accounts past their expiration date could
still log in, unlike with the perl activation script. It also hardcoded
the dynamic allocation range instead of following
security.loginDefs.settings.{UID,GID}_{MIN,MAX}.
Bump to a fork carrying both upstream PRs until they are released:
- nikstur/userborn#72 (expires)
- nikstur/userborn#61 (normalUidRange/normalGidRange)
Mic92
added a commit
to TUM-DSE/nixpkgs
that referenced
this pull request
Sep 17, 2026
…nges
Userborn ignored `expires`, so accounts past their expiration date could
still log in, unlike with the perl activation script. It also hardcoded
the dynamic allocation range instead of following
security.loginDefs.settings.{UID,GID}_{MIN,MAX}.
Bump to a fork carrying both upstream PRs until they are released:
- nikstur/userborn#72 (expires)
- nikstur/userborn#61 (normalUidRange/normalGidRange)
Mic92
added a commit
to TUM-DSE/nixpkgs
that referenced
this pull request
Sep 22, 2026
…nges
Userborn ignored `expires`, so accounts past their expiration date could
still log in, unlike with the perl activation script. It also hardcoded
the dynamic allocation range instead of following
security.loginDefs.settings.{UID,GID}_{MIN,MAX}.
Bump to a fork carrying both upstream PRs until they are released:
- nikstur/userborn#72 (expires)
- nikstur/userborn#61 (normalUidRange/normalGidRange)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stacked on #60.
Adds a top-level
normalIdRangeconfig field (default 1000-29999) controlling the range for dynamically allocated normal user/group IDs, so statically assigned IDs (e.g. for NFS) can be kept outside of it. System IDs stay at 1-999.