Age | Commit message (Collapse) | Author | Files | Lines |
|
(cherry picked from commit f15d286aaca6f7bd9f246c72978992ea8bb73e63)
|
|
(cherry picked from commit 545ba18df2ca2077d6c1a69e02648ad88dd5d968)
|
|
Reusing the same private/public key on renewal has two issues:
- some providers don't accept to sign the same public key
again (Buypass Go SSL)
- keeping the same private key forever partly defeats the purpose of
renewing the certificate often
Therefore, let's remove this option. People wanting to keep the same
key can set extraLegoRenewFlags to `[ --reuse-key ]` to keep the
previous behavior. Alternatively, we could put this as an option whose
default value is true.
(cherry picked from commit 632c8e1d54e299f656aa677f25552e1127f12849)
|
|
Co-authored-by: Martin Weinelt <mweinelt@users.noreply.github.com>
(cherry picked from commit 964fc7cfef94bd598d816979a4ca1a42d9753d23)
|
|
iptables is currently defined in `all-packages.nix` to be
iptables-compat. That package does however not contain `ethertypes`.
Only `iptables-nftables-compat` contains this file so the symlink
dangles.
(cherry picked from commit 2eeecef3fc70e35b2f4c6d8424e4c726c140e330)
|
|
A secret key generated by the nixos module was misspelled, which could
possibly impact the security of session cookies.
To recover from this situation we will wipe all security keys that were
previously generated by the NixOS module, when the misspelled one is
found. This will result in all session cookies being invalidated. This
is confirmed by the wordpress documentation:
> You can change these at any point in time to invalidate all existing
> cookies. This does mean that all users will have to login again.
https://wordpress.org/support/article/editing-wp-config-php/#security-keys
Meanwhile this issue shouldn't be too grave, since the salting function
of wordpress will rely on the concatenation of both the user-provided
and automatically generated values, that are stored in the database.
> Secret keys are located in two places: in the database and in the
> wp-config.php file. The secret key in the database is randomly
> generated and will be appended to the secret keys in wp-config.php.
https://developer.wordpress.org/reference/functions/wp_salt/
Fixes: 2adb03fdaea6186299c6ff578bb6814d8f3bb30b ("nixos/wordpress:
generate secrets locally")
Reported-by: Moritz Hedtke <Moritz.Hedtke@t-online.de>
(cherry picked from commit 724ed08df02546fea2ab38613d615dd47461528c)
|
|
Assert that the PostgreSQL version being deployed is the one used
upstream. Allow the user to override this assertion, since it's not
always possible or preferable to use the recommended one.
(cherry picked from commit 544adbfcab2e92c2fe5774cae67f2edf165eb97e)
|
|
(cherry picked from commit 42b8e7685d5fe5280f8f6101a6d19016b92f3a5c)
|
|
(cherry picked from commit 7953b6e532be68c76e0e02bf6c83ff9350ad529e)
|
|
As per `man systemd.path`:
> When a service unit triggered by a path unit terminates
> (regardless whether it exited successfully or failed),
> monitored paths are checked immediately again,
> **and the service accordingly restarted instantly**.
Thus the existence of the path unit made it impossible to stop the
wireguard service using e.g.
systemctl stop wireguard-wg0.service
Systemd path units are not intended for program inputs such
as private key files.
This commit simply removes this usage; the private key is still
generated by the `generateKeyServiceUnit`.
(cherry picked from commit d344dccf3dc592242f11ef993acb9ecee8d84796)
|
|
LimitNPROC=64 is too low for bitwarden_rs to start on a 32 thread machine.
Remove the limit.
This fixes:
```
bitwarden_rs[38701]: /--------------------------------------------------------------------\
bitwarden_rs[38701]: | Starting Bitwarden_RS |
bitwarden_rs[38701]: |--------------------------------------------------------------------|
bitwarden_rs[38701]: | This is an *unofficial* Bitwarden implementation, DO NOT use the |
bitwarden_rs[38701]: | official channels to report bugs/features, regardless of client. |
bitwarden_rs[38701]: | Send usage/configuration questions or feature requests to: |
bitwarden_rs[38701]: | https://bitwardenrs.discourse.group/ |
bitwarden_rs[38701]: | Report suspected bugs/issues in the software itself at: |
bitwarden_rs[38701]: | https://github.com/dani-garcia/bitwarden_rs/issues/new |
bitwarden_rs[38701]: \--------------------------------------------------------------------/
bitwarden_rs[38701]: [INFO] No .env file found.
bitwarden_rs[38701]: [2021-05-24 03:34:41.121][bitwarden_rs::api::core::sends][INFO] Initiating send deletion
bitwarden_rs[38701]: [2021-05-24 03:34:41.122][start][INFO] Rocket has launched from http://127.0.0.1:8222
bitwarden_rs[38701]: [2021-05-24 03:34:41.126][panic][ERROR] thread 'unnamed' panicked at 'failed to spawn thread: Os { code: 11, kind: WouldBlock, message: "Resource temporarily unavailable" }': /build/rustc-1.52.1-src/library/std/src/thread/mod.rs:620
bitwarden_rs[38701]: 0: bitwarden_rs::init_logging::{{closure}}
bitwarden_rs[38701]: 1: std::panicking::rust_panic_with_hook
bitwarden_rs[38701]: 2: std::panicking::begin_panic_handler::{{closure}}
bitwarden_rs[38701]: 3: std::sys_common::backtrace::__rust_end_short_backtrace
bitwarden_rs[38701]: 4: rust_begin_unwind
bitwarden_rs[38701]: 5: core::panicking::panic_fmt
bitwarden_rs[38701]: 6: core::result::unwrap_failed
bitwarden_rs[38701]: 7: hyper::server::listener::spawn_with
bitwarden_rs[38701]: 8: hyper::server::listener::ListenerPool<A>::accept
bitwarden_rs[38701]: 9: std::sys_common::backtrace::__rust_begin_short_backtrace
bitwarden_rs[38701]: 10: core::ops::function::FnOnce::call_once{{vtable.shim}}
bitwarden_rs[38701]: 11: std::sys::unix::thread::Thread::new::thread_start
bitwarden_rs[38701]: 12: start_thread
bitwarden_rs[38701]: 13: __GI___clone
bitwarden_rs[38701]: [2021-05-24 03:34:41.126][panic][ERROR] thread 'main' panicked at 'internal error: entered unreachable code: the call to `handle_threads` should block on success': /build/bitwarden_rs-1.20.0-vendor.tar.gz/rocket/src/rocket.rs:751
bitwarden_rs[38701]: 0: bitwarden_rs::init_logging::{{closure}}
bitwarden_rs[38701]: 1: std::panicking::rust_panic_with_hook
bitwarden_rs[38701]: 2: std::panicking::begin_panic_handler::{{closure}}
bitwarden_rs[38701]: 3: std::sys_common::backtrace::__rust_end_short_backtrace
bitwarden_rs[38701]: 4: rust_begin_unwind
bitwarden_rs[38701]: 5: core::panicking::panic_fmt
bitwarden_rs[38701]: 6: rocket::rocket::Rocket::launch
bitwarden_rs[38701]: 7: bitwarden_rs::main
bitwarden_rs[38701]: 8: std::sys_common::backtrace::__rust_begin_short_backtrace
bitwarden_rs[38701]: 9: std::rt::lang_start::{{closure}}
bitwarden_rs[38701]: 10: std::rt::lang_start_internal
bitwarden_rs[38701]: 11: main
```
(cherry picked from commit d95960e2755c1c2a8913cc27d0daada84c0c560c)
|
|
Note that it made into 2 entries, one about new options in the first section.
Another in the breaking compatibility section due to the openFirewall option
which changes the behavior.
Co-authored-by: schmittlauch <t.schmittlauch+nixos@orlives.de>
(cherry picked from commit 93a80a4390499b4204cf6836bcc6cab5debecccb)
|
|
The tests timeout on AArch64 (e.g. [0] and [1]), likely because the QEMU
option "-vga virtio" isn't supported there (unfortunately I currently
lack access to an AArch64 system with NixOS to investigate).
This also affects the test for Cage but that one is already limited to
x86_64-linux.
[0]: https://hydra.nixos.org/build/144148809
[1]: https://hydra.nixos.org/build/144103034
(cherry picked from commit abb9ea73f7b2bd8d0862be47a0a1010d7644136b)
|
|
* The options tlsKey and tlsCert require being accessible by DynamicUser at runtime, which currently requires copying the files into the matrix service state directory. Fixing this might require breaking changes. Thus the module should not be included in a stable release.
|
|
|
|
When running - as suggested - `slaptest -f slapd.conf $TMPDIR` I get the
following result:
[root@ldap:/tmp/tmp.De46ABIbFf]# slaptest -f /nix/store/lks3ihydj40ff6yqvz0k33ycrc9vbyry-slapd.conf $TMPDIR
usage: slaptest [-v] [-d debuglevel] [-f configfile] [-F configdir] [-o <name>[=<value>]] [-n databasenumber] [-u] [-Q]
[root@ldap:/tmp/tmp.De46ABIbFf]# echo $?
1
Adding a `-F` option fixes the issue.
(cherry picked from commit b5a12b4b61fca35c7ca94de0338a7e16841888f4)
|
|
(cherry picked from commit 140828ce3843444a8536db884147ed5c4b941259)
|
|
https://github.com/NixOS/nixpkgs/issues/58198
(cherry picked from commit 81e04717e8f30496ec9ec9edb6b0588deca41ee2)
|
|
This reverts commit aeeee447bcc181d57a19d348f857326f4e1959fe.
(cherry picked from commit 113823669b9b71fff84bc592d1fd6022635c28eb)
Signed-off-by: Domen Kožar <domen@dev.si>
|
|
nixos/filesystems: condition mount-pstore.service on unmounted /sys/fs/pstore
(cherry picked from commit d7555732bc8bb8a2acb50fd4ecba96c825b4f21e)
Reason: activation throws an error from failing to start the unit
|
|
CommonMark"
This reverts commit 6c14851943fe55da9df88a502d1e1fe2271d9666.
|
|
This reverts commit 7501467903faa3de62f6a45d5ee2fda35154b8a2.
|
|
This reverts commit 6543c61311c0397775253dd3d7f1f41154fc6189.
|
|
Forgot to merge staging-next into master before branching off.
This is meant to include the additional stabilization changes.
|
|
Conflicts:
pkgs/tools/networking/xh/default.nix
|
|
|
|
Also updates it to mention running md-to-db.sh.
|
|
|
|
|
|
|
|
|
|
|
|
nixos/cinnamon: add polkit_gnome to fix #124062
|
|
nixos/cinnamon: add cinnamon-translations to systemPackages
|
|
This allows other cinnamon applications to use the locales
Without this the cinnamon UI is not properly translated
|
|
|
|
nixos-containers: Increase startup timeout for imperative containers
|
|
nixos/matrix-synapse: protect created files
|
|
Enforce UMask on the systemd unit to restrict the permissions of files
created. Especially the homeserver signing key should not be world
readable, and media is served through synapse itself, so no other user
needs access to these files.
Use a prestart chmod to fixup the permissions on the signing key.
|
|
|
|
|
|
nixos/plasma5: also add plasma-pa when using pipewire with pulseaudio support
|
|
|
|
|
|
nixos/nix-daemon: fix sandbox-paths option
|
|
In newer versions of Nix (at least on 2.4pre20201102_550e11f) the
`extra-` prefix for config options received a special meaning and the
option `extra-sandbox-paths` isn't recognized anymore. This commit fixes
it.
It doesn't cause a behavior change when using older versions of Nix but
does cause an extra newline to appear in the config, thus changing the
hash.
|
|
|
|
|
|
|
|
https://github.com/NixOS/nixpkgs/pull/118232
|