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
It doesn't seem like it is possible to use DFXML format hash files as input files for auditing. I was hoping this would be a solution to a couple filename issues I have noticed (on a Mac). 1) Commas in file names are not parsed properly (I see this is already noted as an issue) 2) Mac "Icon" files actually seem to have filenames like: "Icon^M", and the ^M screws up the parsing of the hash files for auditing.
The text was updated successfully, but these errors were encountered:
This would be really useful because the DFXML format saves file access / modification timestamps, and the DFXML schema also defines attributes for file modes (type and permissions), uid, gid and more. Being able to audit these metadata would alert you to things like an improperly performed backup (It's not fun restoring a website only to find that, although the data is fine, the permissions are all wrong. I've been there).
However, as there are innumerable filesystems each with their own extended attributes e.g. zfs, complex selinux permissions, etc.. Trying to save all possible file metadata could become a real headache. But basic POSIX stuff as supported by DFXML should be achievable and cover most use cases.
Converted from SourceForge issue 3485191, submitted by leekil
It doesn't seem like it is possible to use DFXML format hash files as input files for auditing. I was hoping this would be a solution to a couple filename issues I have noticed (on a Mac). 1) Commas in file names are not parsed properly (I see this is already noted as an issue) 2) Mac "Icon" files actually seem to have filenames like: "Icon^M", and the ^M screws up the parsing of the hash files for auditing.
The text was updated successfully, but these errors were encountered: