Ideas for improving exozyme security #175

Closed
opened 2022-08-05 20:28:40 +00:00 by a · 0 comments
Owner

This is a huge list of ideas that @ersei and I came up with in #general:exozy.me for improving the server's security.

  • AppArmor

  • Give services CAP_NET_ADMIN and have them listen below port 1024 to prevent port hijacking like in #172

  • Uninstall cronie so boot-time cron jobs can't hijack ports

  • Isolate services using systemd sandboxing

  • Chroot/container isolation?

  • Per-user limits on number of processes, CPU, memory usage, similar to #38

  • Configure systemd-oomd to not kill important processes

  • Getting rid of the passwords still hashed with salted SHA1

  • #181

If you have any other ideas feel free to reply!

This is a huge list of ideas that @ersei and I came up with in #general:exozy.me for improving the server's security. - [ ] AppArmor - [ ] Give services CAP_NET_ADMIN and have them listen below port 1024 to prevent port hijacking like in #172 - [x] Uninstall cronie so boot-time cron jobs can't hijack ports - [ ] Isolate services using systemd sandboxing - [ ] Chroot/container isolation? - [ ] Per-user limits on number of processes, CPU, memory usage, similar to #38 - [ ] Configure systemd-oomd to not kill important processes - [ ] Getting rid of the passwords still hashed with salted SHA1 - [x] #181 If you have any other ideas feel free to reply!
a added this to the v9.0 milestone 2022-08-05 20:28:40 +00:00
a added the
enhancement
help wanted
security
labels 2022-08-05 20:28:40 +00:00
a added this to the (deleted) project 2022-08-05 20:28:40 +00:00
a closed this issue 2022-09-25 23:04:57 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference: exozyme/exozyme#175
No description provided.