| Commit message (Collapse) | Author | Age |
| |
|
|\
| |
| | |
dovecot: v2.3.10 → v2.3.10.1
|
| |
| |
| |
| | |
Fixes: CVE-2020-10957, CVE-2020-10958, CVE-2020-10967
|
|/
|
|
|
|
|
|
| |
As per the updating notes[1], DISABLE_TLS replaces SUPPORT_TLS.
The build system also wants you to choose between OpenSSL and GnuTLS.
Since we were using OpenSSL until now, I chose that.
[1]: https://git.exim.org/exim.git/blob_plain/885bb037cb791e057de2105bb3790c6135914c62:/src/README.UPDATING
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
This makes packages use lapack and blas, which can wrap different
BLAS/LAPACK implementations.
treewide: cleanup from blas/lapack changes
A few issues in the original treewide:
- can’t assume blas64 is a bool
- unused commented code
|
| |
|
| |
|
|
|
|
| |
Update module accordingly.
|
| |
|
|\
| |
| | |
dovecot_pigeonhole: 0.5.9 -> 0.5.10
|
| | |
|
|/ |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Release notes aren't available at this time [1] it is likely to be
related to a recent mail to oss-security (either [2] or [3]).
[1] https://www.mail-archive.com/misc@opensmtpd.org/msg04888.html
[2] https://www.openwall.com/lists/oss-security/2020/02/24/5
[3] https://www.openwall.com/lists/oss-security/2020/02/24/4
|
|
|
|
|
|
| |
Fixes CVE-2020-7046 & CVE-2020-7957:
https://dovecot.org/pipermail/dovecot-news/2020-February/000429.html
|
|\
| |
| | |
rspamd: 2.2 -> 2.3
|
| | |
|
|\ \
| | |
| | | |
opensmtpd: 6.6.2p1 -> 6.6.3p1
|
| |/ |
|
|/ |
|
| |
|
|\ |
|
| |\
| | |
| | | |
sympa: init at 6.2.52 + NixOS module
|
| | | |
|
|/ / |
|
|\ \
| |/
|/|
| |
| | |
Includes update of stdenv bootstap tools (for three main platforms)
and many package fixes with new glibc.
|
| |\ |
|
| |\ \
| | | |
| | | |
| | | |
| | | | |
Conflicts:
pkgs/applications/misc/vit/default.nix
|
| |\ \ \ |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
dependency"
This reverts commit ce6b2419be6e16cc6b9096c99798a0d365b16486, which
was unnecessary (mailman worked just fine on its parent commit).
See #79222.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Please remove the explicit urllib3 dependency from this expression again once
https://github.com/NixOS/nixpkgs/issues/79222 is fixed.
|
| | | | | |
|
| | | | | |
|
| |_|_|/
|/| | |
| | | |
| | | | |
The merge 98640fd48212f8e6552517f667bba1901f5936d4 was done incorrectly.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Previously, some files were copied into the Nixpkgs tree, which meant
we wouldn't easily be able to update them, and was also just messy.
The reason it was done that way before was so that a few NixOS
options could be substituted in. Some problems with doing it this way
were that the _package_ changed depending on the values of the
settings, which is pretty strange, and also that it only allowed those
few settings to be set.
In the new model, mailman-web is a usable package without needing to
override, and I've implemented the NixOS options in a much more
flexible way. NixOS' mailman-web config file first reads the
mailman-web settings to use as defaults, but then it loads another
configuration file generated from the new services.mailman.webSettings
option, so _any_ mailman-web Django setting can be customised by the
user, rather than just the three that were supported before. I've
kept the old options, but there might not really be any good reason to
keep them.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
We already had python3Packages.mailman, but that's only really usable
as a library. The only other option was to create a whole Python
environment, which was undesirable to install as a system-wide
package.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This replaces all Mailman secrets with ones that are generated the
first time the service is run. This replaces the hyperkittyApiKey
option, which would lead to a secret in the world-readable store.
Even worse were the secrets hard-coded into mailman-web, which are not
just world-readable, but identical for all users!
services.mailman.hyperkittyApiKey has been removed, and so can no
longer be used to determine whether to enable Hyperkitty. In its
place, there is a new option, services.mailman.hyperkitty.enable. For
consistency, services.mailman.hyperkittyBaseUrl has been renamed to
services.mailman.hyperkitty.baseUrl.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Using a custom path in the Nix store meant that users of the module
couldn't add their own config files, which is a desirable feature. I
don't think avoiding /etc buys us anything.
|
| |_|/
|/| |
| | |
| | |
| | | |
Fixes critical vulnerability:
https://www.mail-archive.com/misc@opensmtpd.org/msg04850.html
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
The previously propagated build inputs are optional, and so are
included in checkInputs so the tests can run, but not propagated so
they aren't included if unneeded.
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
The actual upstream "mailman" name just refers to this, so we should
use the Nixpkgs convention of default.nix.
|