Comment 4 for bug 2020838

Revision history for this message
Seth Arnold (seth-arnold) wrote :

Awesome find! Probably for many users, that's a perfectly fine change, I suspect that auditing home directories isn't going to be a top priority for many people.

However, the sheer confusion of this issue is troubling: going from these error messages to "I have to remove a systemd configuration directive" is a big leap. At least now there's a bug report on the internet with both the error message and the solution, so the next person will have an easier time of it, but it probably will still only come after frustration.

But I'm leery of removing hardening options. Opinions from the wider world?

Thanks