197568 2019-05-03 10:46:24 -0700 Investigate no longer resolving symlinks when creating a SandboxExtension 2019-05-17 10:18:25 -0700 1 1 1 Unclassified WebKit WebKit2 WebKit Nightly Build Unspecified Unspecified REOPENED https://bugs.webkit.org/show_bug.cgi?id=197389 InRadar P2 Normal --- 197389 1 bfulgham webkit-unassigned ap bfulgham darin mjs webkit-bug-importer oldest_to_newest 1532852 0 bfulgham 2019-05-03 10:46:24 -0700 When we originally wrote the SandboxExtension logic for handling files, we believed that they had to be defined in terms of the canonical paths on the file system. We added logic to resolve symlinks prior to issuing the extensions. We now know that this is unnecessary work, and could be avoided entirely. This is likely to improve performance of certain file operations, and should be investigated as a way to further improve performance. 1532854 1 bfulgham 2019-05-03 10:46:55 -0700 <rdar://problem/14062743> 1537143 2 bfulgham 2019-05-17 10:07:59 -0700 After discussing this with Sandbox experts, it is not true that we can avoid resolving symlinks. We should not pursue this idea. 1537144 3 bfulgham 2019-05-17 10:18:25 -0700 Whoops -- we need fully-resolved names in Sandbox profile rules. But I think we can pass a sandbox extension to a path containing symlinks, and it's usable.