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
The auditd fileset has no paths defined for macOS. Unfortunately, because all filesets are enabled by default, it means that the system module doesn't work on macOS.
This is the relevant portion of the manifest file:
An easy solution would be to replace os.darwin: [] with os.darwin: [""], which would mean that the fileset is silently ignored on macOS, but I see that and auditd daemon does seem to exist on macOS as well.
@andrewkroh Would it make sense to support the macOS' auditd?
The text was updated successfully, but these errors were encountered:
It would make sense to have this work on macOS. But I don't know much about auditing on macOS, in fact I don't even know where the logs are (checked /var/log/audit but it does not exists for me). I thought they were written using Apple's Unified Logging framework meaning the logs are in binary somewhere, but I can't even find them in Console.
The auditd fileset has no paths defined for macOS. Unfortunately, because all filesets are enabled by default, it means that the system module doesn't work on macOS.
This is the relevant portion of the manifest file:
An easy solution would be to replace
os.darwin: []
withos.darwin: [""]
, which would mean that the fileset is silently ignored on macOS, but I see that andauditd
daemon does seem to exist on macOS as well.@andrewkroh Would it make sense to support the macOS'
auditd
?The text was updated successfully, but these errors were encountered: