4 ms·
Great tactical advice, but what a sad situation to be in. "Run this command, then run this command, then run this command ..." There should be a single configu
by seagreen 10y ago
Great tactical advice, but what a sad situation to be in. "Run this command, then run this command, then run this command ..."
There should be a single configuration file (or set of files) that declaratively describes the whole state of the machine. That way the exact situation of the server can be reviewed by just looking at files, instead of trying to poke and prod at the machine to see what commands have been run over the last X weeks.
- benplumley 10y agoThere is a set of files that describes the state of the machine, it's called the filesystem. Anything less doesn't describe the whole machine. The 'poking and prodding' is just a convenient way of querying the very small parts of the filesystem that are relevant to that query. That said, a script that pokes and prods the right places and reports a machine's 'security factor' and prompts improvements would be cool (and probably already exists).
- rdrake 10y ago> That said, a script that pokes and prods the right places and reports a machine's 'security factor' and prompts improvements would be cool (and probably already exists). https://cisofy.com/lynis/ https://cisofy.com/lynis/