identify missing calls from syscall() in libsr3shim #178
Labels
enhancement
New feature or request
wishlist
not a priority, but a long term wish...
worries
needs work to clarify status
The initial implementation has been fairly thoroughly investigated on redhat 8. We initially were only expecting to have the syscall() implementation active on redhat 8 and ubuntu 18, where there is a known very common case of syscall usage by a very common package (file-utils... aka mv.)
There should be some kind of audit script to warn that there is a syscall defined on the current system that isn't covered by what we do in libsr3shim.
The text was updated successfully, but these errors were encountered: