WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED INVALID
217336
[macOS] Add XPC endpoint entitlement for the WebContent development process
https://bugs.webkit.org/show_bug.cgi?id=217336
Summary
[macOS] Add XPC endpoint entitlement for the WebContent development process
Per Arne Vollan
Reported
2020-10-05 14:00:02 PDT
The WebContent process has the entitlement 'com.apple.private.webkit.use-xpc-endpoint', which is not present in the development version.
Attachments
Patch
(1.55 KB, patch)
2020-10-05 14:04 PDT
,
Per Arne Vollan
no flags
Details
Formatted Diff
Diff
Patch
(1.66 KB, patch)
2020-10-05 14:42 PDT
,
Per Arne Vollan
darin
: review+
Details
Formatted Diff
Diff
Show Obsolete
(1)
View All
Add attachment
proposed patch, testcase, etc.
Per Arne Vollan
Comment 1
2020-10-05 14:04:13 PDT
Created
attachment 410553
[details]
Patch
Per Arne Vollan
Comment 2
2020-10-05 14:41:46 PDT
<
rdar://problem/68585497
>
Per Arne Vollan
Comment 3
2020-10-05 14:42:38 PDT
Created
attachment 410564
[details]
Patch
Darin Adler
Comment 4
2020-10-18 15:36:45 PDT
Comment on
attachment 410564
[details]
Patch View in context:
https://bugs.webkit.org/attachment.cgi?id=410564&action=review
> Source/WebKit/ChangeLog:10 > + The WebContent process has the entitlement 'com.apple.private.webkit.use-xpc-endpoint', > + which is not present in the development version.
I’ll take your word for it that this is a good change. But I don’t understand what you are saying here with that sentence. You say the process "has the entitlement", but how does it get it? You say it "is not present in the development version". Is that a statement of what’s wrong and what you are fixing, and hence no longer true? Or does it mean something else. What I see in the patch is two changes: 1) Only add use-xpc-endpoint for macOS 11.0 and newer. 2) Add use-xpc-endpoint even when WK_USE_RESTRICTED_ENTITLEMENTS is NO. I can’t make the connection between this and "the development version" and "has the entitlement" comment above.
Per Arne Vollan
Comment 5
2020-10-20 09:04:49 PDT
(In reply to Darin Adler from
comment #4
)
> Comment on
attachment 410564
[details]
> Patch > > View in context: >
https://bugs.webkit.org/attachment.cgi?id=410564&action=review
> > > Source/WebKit/ChangeLog:10 > > + The WebContent process has the entitlement 'com.apple.private.webkit.use-xpc-endpoint', > > + which is not present in the development version. > > I’ll take your word for it that this is a good change. > > But I don’t understand what you are saying here with that sentence. You say > the process "has the entitlement", but how does it get it? You say it "is > not present in the development version". Is that a statement of what’s wrong > and what you are fixing, and hence no longer true? Or does it mean something > else. > > What I see in the patch is two changes: > > 1) Only add use-xpc-endpoint for macOS 11.0 and newer. > 2) Add use-xpc-endpoint even when WK_USE_RESTRICTED_ENTITLEMENTS is NO. > > I can’t make the connection between this and "the development version" and > "has the entitlement" comment above.
Yes, the description in the change log was too short. The required entitlement 'com.apple.private.webkit.use-xpc-endpoint' is already present in com.apple.WebKit.WebContent.xpc, but not in the development XPC service, com.apple.WebKit.WebContent.Development.xpc. The intention of this patch was to add the entitlement also for the development XPC service, but I have later learned that the system WebKit development XPC service cannot have private entitlements, so this patch is now invalid. Thanks for reviewing!
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug