Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

many: do not use nss when looking up for users/groups from snapd snap #13776

Merged
merged 2 commits into from
Sep 30, 2024
Merged

many: do not use nss when looking up for users/groups from snapd snap #13776

merged 2 commits into from
Sep 30, 2024

Commits on Sep 19, 2024

  1. many: do not use runtime nss when looking up for users/groups from sn… 

    …apd snap

When snapd runs as a snap, it has its own runtime. This may not have
NSS plugins needed for the host. For example to get users from
AD/LDAP/Kerberos, or systemd-homed, or custom user databses.  In
general we can use tag `osusergo` to make go not to use the local
configuration (i.e. `/etc/nsswitch.conf`), however, even if it is fine
for most databases, we really need users and groups to be resolved
with the host configuration.

To be able to load correctly plugins, we expect the host system to
provide `getent`. And we query `passwd` and `group` databases through
this command.

In the future we should connect the systemd-userdb if it is
running and use `getent` only as fallback.
    @valentindavid
    valentindavid committed Sep 19, 2024
    Configuration menu
    Copy the full SHA
    d05eb8f View commit details
    Browse the repository at this point in the history

  2. .golangci.yml: verify for forbidden use of os/user

    @valentindavid
    valentindavid committed Sep 19, 2024
    Configuration menu
    Copy the full SHA
    22f3403 View commit details
    Browse the repository at this point in the history