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
Some example Policies are using wildcards in places, where it's not documented, e.g.: https://docs.kubearmor.io/kubearmor/use-cases/hardening#logs-delete in path within file.matchPaths. I have tested that with BPF-LSM and wildcard character (*) is not evaluated, it's considered as a part of path.
Not sure if this should work at least with AppArmor, but maybe documentation should be more specific about it.
I see an old unresolved discussion about globbing with eBPF (#448)...
The text was updated successfully, but these errors were encountered:
Bug Report
Some example Policies are using wildcards in places, where it's not documented, e.g.: https://docs.kubearmor.io/kubearmor/use-cases/hardening#logs-delete in
path
withinfile.matchPaths
. I have tested that with BPF-LSM and wildcard character (*
) is not evaluated, it's considered as a part of path.Not sure if this should work at least with AppArmor, but maybe documentation should be more specific about it.
I see an old unresolved discussion about globbing with eBPF (#448)...
The text was updated successfully, but these errors were encountered: