| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
nvidia: expose nvidia_x11_legacy390
|
|
For the hardened profile disable symmetric multi threading. There seems to be
no *proven* method of exploiting cache sharing between threads on the same CPU
core, so this may be considered quite paranoid, considering the perf cost.
SMT can be controlled at runtime, however. This is in keeping with OpenBSD
defaults.
TODO: since SMT is left to be controlled at runtime, changing the option
definition should take effect on system activation. Write to
/sys/devices/system/cpu/smt/control
|
|
For the hardened profile enable flushing whenever the hypervisor enters the
guest, but otherwise leave at kernel default (conditional flushing as of
writing).
|
|
Introduces the option security.protectKernelImage that is intended to control
various mitigations to protect the integrity of the running kernel
image (i.e., prevent replacing it without rebooting).
This makes sense as a dedicated module as it is otherwise somewhat difficult
to override for hardened profile users who want e.g., hibernation to work.
|
|
|
|
This, paired with the previous commit, ensures the channel won't be held
back from a kernel upgrade and a non-building sd image, while still
having a new-kernel variant available.
|
|
|
|
geoclue2: correct sysconfdir
|
|
|
|
Mobile updates
|
|
GCE OSLogin module: init
|
|
|
|
vdr: revisited version of https://github.com/NixOS/nixpkgs/pull/32050
|
|
|
|
|
|
used same plugin mechanism as kodi does
|
|
extraSessionFilePackages
Not everyone is using wayland just yet.
|
|
google-accounts-daemon
Use googleOsLogin for login instead.
This allows setting users.mutableUsers back to false, and to strip the
security.sudo.extraConfig.
security.sudo.enable is default anyhow, so we can remove that as well.
|
|
config.security.googleOsLogin.enable is set
|
|
The OS Login package enables the following components:
AuthorizedKeysCommand to query valid SSH keys from the user's OS Login
profile during ssh authentication phase.
NSS Module to provide user and group information
PAM Module for the sshd service, providing authorization and
authentication support, allowing the system to use data stored in
Google Cloud IAM permissions to control both, the ability to log into
an instance, and to perform operations as root (sudo).
|
|
googleOsLogin(AccountVerification|Authentication)
|
|
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
https://github.com/NixOS/nixpkgs/pull/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.
|
|
aarch64: ZHF for aarch64 (1/??)
|
|
|
|
clickhouse: 18.14.9 -> 18.14.18
|
|
Although the package itself builds fine, the module fails because it
tries to log into a non-existant file in `/var/log` which breaks the
service. Patching to default config to log to stdout by default fixes
the issue. Additionally this is the better solution as NixOS heavily
relies on systemd (and thus journald) for logging.
Also, the runtime relies on `/etc/localtime` to start, as it's not
required by the module system we set UTC as sensitive default when using
the module.
To ensure that the service's basic functionality is available, a simple
NixOS test has been added.
|
|
This flag causes the shairport-sync server to attempt to daemonize, but it looks like systemd is already handling that. With the `-d` argument, shairport-sync immediately exits—it seems that something (systemd I'm guessing?) is sending it SIGINT or SIGTERM.
The [upstream systemd unit](https://github.com/mikebrady/shairport-sync/blob/master/scripts/shairport-sync.service.in#L10) doesn't pass `-d`.
|
|
nixos/oh-my-zsh: fix wrong manual information
|
|
|
|
Manual still refers to 'programs.ohMyZsh' although it should be 'programs.zsh.ohMyZsh'.
|
|
nixos/bash: Fix prompt regression in Emacs term mode
|
|
Introduce hardware/bladeRF module
|
|
This allows to easily enable bladerf-related udev rules with nixos
configuration.
|
|
installer: Adds AArch64 UEFI installer support. (Work towards SBBR and EBBR support)
|
|
|
|
|
|
nixos: add AppStream module
|
|
Add bluez full package
|
|
Fix s2s_secure_auth.
|
|
pkgs.owncloud still pointed to owncloud 7.0.15 (from May 13 2016)
Last owncloud server update in nixpkgs was in Jun 2016.
At the same time Nextcloud forked away from it, indicating users
switched over to that.
cc @matej (original maintainer)
|
|
|
|
nixos/nextcloud: add basic module documentation and warn about current upgrading issues
|
|
|
|
|
|
nixos/openldap: Support configuring the log level
|
|
|
|
|
|
|
|
|
|
Disable nscd caching
|
