[DeepGuard on macOS] Will lots of ancestry lookup rules make system slow?
Good day, dev team! I was trying to give full access for systemmigrationd and system_installd, also their child processes. After reading rules that come with the FSP, I found following rules meet my need:
allow path "any" "any ancestor /System/Library/PrivateFrameworks/SystemMigration.framework/Versions/A/Resources/systemmigrationd" rwc
allow path "any" "any ancestor /System/Library/PrivateFrameworks/PackageKit.framework/Versions/A/Resources/system_installd" rwc
However, related comments also mentioned that such rules require a large performance overhead:
; ancestry lookups are the most expensive, so they're put last
If I add a large number of ancestry lookup rules (like a hundred rules), will user experience a noticeable performance drop, especially in strict mode?