nerf/defaultRoles #12
No reviewers
Labels
No labels
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Fachschaft/nixConfig#12
Loading…
Reference in a new issue
No description provided.
Delete branch "nerf/nixConfig:nerf/defaultRoles"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
default roles config that is shared across machines
resolves [#11]
@ -0,0 +5,4 @@
admins = {
nerf = {
hashedPassword =
"$y$j9T$SJcjUIcs3JYuM5oyxfEQa/$tUBQT07FK4cb9xm.A6ZKVnFIPNOYMOKC6Dt6hadCuJ7";
Why does this user get a password? We didn't do that on our Debian machines with individual user accounts.
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.
@ -0,0 +16,4 @@
{hashedPassword, keys}: {
"${name}" = {
isNormalUser = true;
createHome = true;
Why do they get a home directory? I would expect them to have about no personal data.
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
I don't really care.
@ -4,0 +39,4 @@
services = {
journald.extraConfig = "SystemMaxUse=5G";
nginx = {
Does this only set the defaults in case we enable some nginx or does this enable nginx (and why)?
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.@ -0,0 +1,16 @@
{...}: {
How does this file compare to the Xen-DomU config?
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?
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?
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)