Skip to content
This repository was archived by the owner on Apr 12, 2021. It is now read-only.
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: NixOS/nixpkgs-channels
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: a2eed09a8c85
Choose a base ref
...
head repository: NixOS/nixpkgs-channels
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: c0611717dcab
Choose a head ref
  • 7 commits
  • 7 files changed
  • 5 contributors

Commits on Dec 21, 2018

  1. security.pam: make pam_unix.so required, not sufficient 

    Having pam_unix set to "sufficient" means early-succeeding account
management group, as soon as pam_unix.so is succeeding.

This is not sufficient. For example, nixos modules might install nss
modules for user lookup, so pam_unix.so succeeds, and we end the stack
successfully, even though other pam account modules might want to do
more extensive checks.

Other distros seem to set pam_unix.so to 'required', so if there are
other pam modules in that management group, they get a chance to do some
validation too.

For SSSD, @PsyanticY already added a workaround knob in
NixOS/nixpkgs#31969, while stating this should
be the default anyway.

I did some thinking in what could break - after this commit, we require
pam_unix to succeed, means we require `getent passwd $username` to
return something.
This is the case for all local users due to the passwd nss module, and
also the case for all modules installing their nss module to
nsswitch.conf - true for ldap (if not explicitly disabled) and sssd.

I'm not so sure about krb5, cc @eqyiel for opinions. Is there some nss
module loaded? Should the pam account module be placed before pam_unix?

We don't drop the `security.pam.services.<name?>.sssdStrictAccess`
option, as it's also used some lines below to tweak error behaviour
inside the pam sssd module itself (by changing it's 'control' field).

This is also required to get admin login for Google OS Login working
(#51566), as their pam_oslogin_admin accounts module takes care of sudo
configuration.
    @flokli
    flokli committed Dec 21, 2018
    Copy the full SHA
    d180bf3 View commit details

  2. clojure: 1.9.0.391 -> 1.10.0.403

    @jlesquembre
    jlesquembre committed Dec 21, 2018
    Copy the full SHA
    5d9d164 View commit details

  3. Merge pull request #52488 from flokli/pam_account_unix_required 

    security.pam: make pam_unix.so required, not sufficient
    @flokli
    flokli authored Dec 21, 2018
    Copy the full SHA
    9c86e8f View commit details

  4. nixpkgs/firecracker: init at 0.12.0 

    This currently uses a binary-only package, since building
jailer/firecracker all on their own is somewhat complex from my
attempts.

This will later be changed into a source-only build, ideally.

Signed-off-by: Austin Seipp <aseipp@pobox.com>
    @thoughtpolice
    thoughtpolice committed Dec 21, 2018
    Copy the full SHA
    814319f View commit details

  5. Merge pull request #52631 from jlesquembre/clojure 

    clojure: 1.9.0.391 -> 1.10.0.403
    @Mic92
    Mic92 authored Dec 21, 2018
    Copy the full SHA
    435ba2b View commit details

  6. pythonPackages.uritemplate_py: remove 

    This package is the same as uritemplate.
    @lopsided98
    lopsided98 committed Dec 21, 2018
    Copy the full SHA
    26869e7 View commit details

  7. Merge pull request #52641 from lopsided98/uritemplate-merge 

    pythonPackages.uritemplate_py: remove
    @Mic92
    Mic92 authored Dec 21, 2018
    Copy the full SHA
    c061171 View commit details
Loading