mirror of https://github.com/OISF/suricata
threads: don't drop capabilities for packet threads
Remove the call to SCDropCaps for packet processing threads. This logic in this function is required to setup packet processing even when the thread is provided by a library user, in which case Suricata should not be touching is capabilities. As SCDropCaps is currently a no-op its clear this feature needs to be (re)designed properly, taking into consideration library users as well. Related ticket: https://redmine.openinfosecfoundation.org/issues/2375pull/11858/head
parent
976dec7f33
commit
3b6f709331
Loading…
Reference in New Issue