In preparation of blocking this service in the WebContent process, a sandbox extension should be issued if Safari's Develop menu is enabled.
<rdar://problem/71495287>
Created attachment 414359 [details] Patch
Comment on attachment 414359 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=414359&action=review r=me > Source/WebKit/UIProcess/Cocoa/WebProcessProxyCocoa.mm:209 > + if (!CFPreferencesGetAppIntegerValue(CFSTR("ShowDevelopMenu"), CFSTR("com.apple.Safari.SandboxBroker"), nullptr)) It's a shame we couldn't reuse WIRRemoteInspectorEnabledKey here (i.e., define this differently on non-IOS_FAMILY). > Tools/MiniBrowser/MiniBrowser.entitlements:29 > + <string>com.apple.Safari.SandboxBroker</string> Do we need this for WebKitTestRunner?
Created attachment 414589 [details] Patch
(In reply to Brent Fulgham from comment #3) > Comment on attachment 414359 [details] > Patch > > View in context: > https://bugs.webkit.org/attachment.cgi?id=414359&action=review > > r=me > > > Source/WebKit/UIProcess/Cocoa/WebProcessProxyCocoa.mm:209 > > + if (!CFPreferencesGetAppIntegerValue(CFSTR("ShowDevelopMenu"), CFSTR("com.apple.Safari.SandboxBroker"), nullptr)) > > It's a shame we couldn't reuse WIRRemoteInspectorEnabledKey here (i.e., > define this differently on non-IOS_FAMILY). > > > Tools/MiniBrowser/MiniBrowser.entitlements:29 > > + <string>com.apple.Safari.SandboxBroker</string> > > Do we need this for WebKitTestRunner? I don't believe so, since WebKitTestRunner is not sandboxed, AFAIK. Thanks for reviewing!
Committed r270035: <https://trac.webkit.org/changeset/270035> All reviewed patches have been landed. Closing bug and clearing flags on attachment 414589 [details].