RESOLVED FIXED 206020
Remove AGXCompilerService access from the WebContent sandbox
https://bugs.webkit.org/show_bug.cgi?id=206020
Summary Remove AGXCompilerService access from the WebContent sandbox
Brent Fulgham
Reported 2020-01-09 11:44:12 PST
Now that we generate a dynamic extension for 'com.apple.AGXCompilerService', we should remove the blanket allow rule from the sandbox.
Attachments
Patch (1.65 KB, patch)
2020-01-09 12:09 PST, Brent Fulgham
no flags
Radar WebKit Bug Importer
Comment 1 2020-01-09 11:47:25 PST
Brent Fulgham
Comment 2 2020-01-09 12:09:45 PST
Per Arne Vollan
Comment 3 2020-01-09 13:21:48 PST
Should we also add a test case for this in fast/sandbox/ios/sandbox-mach-lookup.html?
Brent Fulgham
Comment 4 2020-01-09 14:06:05 PST
(In reply to Per Arne Vollan from comment #3) > Should we also add a test case for this in > fast/sandbox/ios/sandbox-mach-lookup.html? Since this is hardware specific, will we have too many test failures? Is there a way to skip on specific hardware? I think we only support version and platform (not 2017 iPad versus 2018 iPad, for example).
Per Arne Vollan
Comment 5 2020-01-09 14:11:28 PST
(In reply to Brent Fulgham from comment #4) > (In reply to Per Arne Vollan from comment #3) > > Should we also add a test case for this in > > fast/sandbox/ios/sandbox-mach-lookup.html? > > Since this is hardware specific, will we have too many test failures? > > Is there a way to skip on specific hardware? I think we only support version > and platform (not 2017 iPad versus 2018 iPad, for example). You're right, I don't think there is a way to skip specific hardware.
Per Arne Vollan
Comment 6 2020-01-09 14:12:01 PST
Comment on attachment 387251 [details] Patch Great! R=me.
WebKit Commit Bot
Comment 7 2020-01-09 15:18:12 PST
Comment on attachment 387251 [details] Patch Clearing flags on attachment: 387251 Committed r254306: <https://trac.webkit.org/changeset/254306>
WebKit Commit Bot
Comment 8 2020-01-09 15:18:14 PST
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.