nerf/defaultRoles #12

Merged
nerf merged 10 commits from nerf/nixConfig:nerf/defaultRoles into main 2023-10-05 21:15:32 +00:00
Owner

default roles config that is shared across machines
resolves [#11]

default roles config that is shared across machines resolves [#11]
nerf added 9 commits 2023-09-30 15:35:26 +00:00
nerf added the
Kind/Feature
label 2023-09-30 21:15:44 +00:00
Gonne reviewed 2023-10-02 06:08:44 +00:00
@ -0,0 +5,4 @@
admins = {
nerf = {
hashedPassword =
"$y$j9T$SJcjUIcs3JYuM5oyxfEQa/$tUBQT07FK4cb9xm.A6ZKVnFIPNOYMOKC6Dt6hadCuJ7";
Owner

Why does this user get a password? We didn't do that on our Debian machines with individual user accounts.

Why does this user get a password? We didn't do that on our Debian machines with individual user accounts.
Author
Owner

Basically my paranoia, makes privilege escalation on that machine harder.

It also makes sane user based console log ins possible. You might have noticed I disabled root
console (technically password) login.

Basically my paranoia, makes privilege escalation on that machine harder. It also makes sane user based console log ins possible. You might have noticed I disabled root console (technically password) login.
Gonne marked this conversation as resolved
@ -0,0 +16,4 @@
{hashedPassword, keys}: {
"${name}" = {
isNormalUser = true;
createHome = true;
Owner

Why do they get a home directory? I would expect them to have about no personal data.

Why do they get a home directory? I would expect them to have about no personal data.
Author
Owner

The home directory is not persistent anyway, but it will give a lot of programs that you might use a safe to throw their stuff.
For example bash starts to write things to disk the moment you use it. All in all I think it is convenient and not persistent anyway.
But I also don't think it matters too much. So I can change it if you think that is blocking

The home directory is not persistent anyway, but it will give a lot of programs that you might use a safe to throw their stuff. For example bash starts to write things to disk the moment you use it. All in all I think it is convenient and not persistent anyway. But I also don't think it matters too much. So I can change it if you think that is blocking
Owner

I don't really care.

I don't really care.
Gonne marked this conversation as resolved
@ -4,0 +39,4 @@
services = {
journald.extraConfig = "SystemMaxUse=5G";
nginx = {
Owner

Does this only set the defaults in case we enable some nginx or does this enable nginx (and why)?

Does this only set the defaults in case we enable some nginx or does this enable nginx (and why)?
Author
Owner

This does not enable ngingx, but it will set these if you load ngingx (for that there is services.nginx.enable). And it isn't nginx default behavior but it kind of should be.

This does not enable ngingx, but it will set these if you load ngingx (for that there is `services.nginx.enable`). And it isn't nginx default behavior but it kind of should be.
Gonne marked this conversation as resolved
@ -0,0 +1,16 @@
{...}: {
Owner

How does this file compare to the Xen-DomU config?

How does this file compare to the [Xen-DomU](https://github.com/NixOS/nixpkgs/blob/nixos-unstable/nixos/modules/virtualisation/xen-domU.nix) config?
Author
Owner

Ahh I was not aware of that, it is probably better to just load that file (even if we don't need some of the kernel modules that early).
(It doesn't really hurt).

But it does change logging behavior in a (I think) sensible way. But I'm unsure if we are prepared for that. Do we do anything
with the Xen console logs?

Ahh I was not aware of that, it is probably better to just load that file (even if we don't need some of the kernel modules that early). (It doesn't really hurt). But it does change logging behavior in a (I think) sensible way. But I'm unsure if we are prepared for that. Do we do anything with the Xen console logs?
Owner

We currently don't log Xen console logs as far as I know, but I'd like to be closer to this file. Maybe log both to console and to disk until we collect the console log?

We currently don't log Xen console logs as far as I know, but I'd like to be closer to this file. Maybe log both to console and to disk until we collect the console log?
Author
Owner

Ahh that probably doesn't even change anything because we log on that machines using journald and not syslogd. (We could, and journald has an option to forward logs to syslog). But for now it doesn't change anything (it would though the moment we decide to you syslog)

Ahh that probably doesn't even change anything because we log on that machines using journald and not syslogd. (We could, and journald has an option to forward logs to syslog). But for now it doesn't change anything (it would though the moment we decide to you syslog)
Gonne marked this conversation as resolved
nerf added 1 commit 2023-10-04 22:16:39 +00:00
Gonne approved these changes 2023-10-05 07:53:32 +00:00
nerf merged commit 33519a678a into main 2023-10-05 21:15:32 +00:00
nerf deleted branch nerf/defaultRoles 2023-10-05 21:15:32 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Fachschaft/nixConfig#12
No description provided.