You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Like if the user has a seperate /home volume, we can't harden it with our custom systemd unit. I think the reason behind this is, systemd dynamically overrides our unit with the unit it auto generates from fstab on startup.
The dracut based implementation used to harden /home. There does not seem to be anything special with /home.
Otherwise the code would need some debugging. Write the output of findmnt --list to a file or output it to stdout so the systemd journal picks it up.
After the system completed booting, findmnt --list can be run again and the two different outputs can be compared. That would show if the initial mount hardening is failing or if indeed something else later reverts it.
Originally posted by @monsieuremre in #157 (comment)
The text was updated successfully, but these errors were encountered: