3 ms·
At a previous job they offered Linux laptops (yay!), but... - umask was not 022, so installing pretty much anything with `sudo make install` would fail, as wou
by MathMonkeyMan 1y ago
At a previous job they offered Linux laptops (yay!), but...
- umask was not 022, so installing pretty much anything with `sudo make install` would fail, as would some software.
- Running nmap caused an alert to phone home to IT, who would nag me on slack.
- Opening well-known ports to my LAN (like 22) caused an alert to IT.
- An "agent" program ran constantly, often using 100% of a CPU. The system overall had about 45 minutes of battery life.
- Various system settings were overridden by a sysctl.d/ file that was regenerated by the agent at boot. Fortunately I know how ASCII sorting works and could produce a file that overrode the overrides.
- Various capabilities (CAP_...) were disabled for my sudoer user.
It wasn't that bad, and IT was helpful, but it was a persistent annoyance. Maybe what happened is somebody googled "how to harden Linux" and then just made everything on the first page of results company policy.
- DmitryOlshansky 1y agoAt my work they would also disable ptrace in the kernel and require you to explain why need it