| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
| |
Before, new certs were requested at every rebuild.
This caused issues due to letsencrypt ratelimiting.
|
| |
|
|
|
|
| |
This reverts commit ecb274ba49042f1dfdf63b9c54ff6920f24a9a58.
It may be a security-risk, but I care much more about a running
mailserver for now.
|
| |
|
|
| |
The old one, could have exposed a weak hash.
|
| |
|
|
|
| |
The hardware settings are (somewhat) host specific, and putting them in
`system` just builds the wrong expectations.
|
| |
|
|
|
| |
The old values did work, but these should just make things a bit
clearer.
|
| | |
|
| |
|
|
|
| |
It is sort of standard to ignore connections over the unencrypted port
25, thus we are doing the same.
|
| | |
|
| |
|
|
| |
I just think this is easier to read.
|
| |
|
|
|
| |
This is something that just makes the file system easier to traverse, but
isn't really necessary.
|
| |
|
|
|
|
| |
As outlined in commit 19f0808, placing a password hash in the world
readable nix-store is perfectly safe as long as the hashing function is
not reversible, which should be a necessity for a password hash.
|
| |
|
|
|
| |
All users are in the wheel group, thus direct login as root is no longer
needed.
|
| | |
|
| |
|
|
|
|
| |
This is inherently unsafe because it requires an unencrypted handshake.
Considering that all protocols also work directly with TLS i.e., the
encrypted variant, disabling this shouldn't be a drawback.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
We used the domain name instead of the host name, which obviously
doesn't work for multiple host. In addition to that I changed some
directory to make importing easier and enabled the "nix-command" and
"flakes" experimental options, to make the `nix flake check` command
usable.
Refs: #15
|
|
|
Nix flakes make a lot of things very easy.
|
