From googleclient/chrome/chromium_gwsq/ipc/config.gwsq:
IPC: ort...@chromium.org
📎 It looks like you’re making a possibly security-sensitive change! 📎 IPC security review isn’t a rubberstamp, so your friendly security reviewer will need a fair amount of context to review your CL effectively. Please review your CL description and code comments to make sure they provide context for someone unfamiliar with your project/area. Pay special attention to where data comes from and which processes it flows between (and their privilege levels). Feel free to point your security reviewer at design docs, bugs, or other links if you can’t reasonably make a self-contained CL description. (Also see https://cbea.ms/git-commit/).
IPC reviewer(s): ort...@chromium.org
Reviewer source(s):
ort...@chromium.org is from context(googleclient/chrome/chromium_gwsq/ipc/config.gwsq)
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
content::ChildProcessId::FromUnsafeValue(Why do we use FromUnsafeValue here? Neither the comment on the method nor the bug really give much context.
I'm assuming a follow up change will change `service_worker_version_info.process_id` to use a ChildProcessId and then this won't be needed?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
content::ChildProcessId::FromUnsafeValue(Why do we use FromUnsafeValue here? Neither the comment on the method nor the bug really give much context.
I'm assuming a follow up change will change `service_worker_version_info.process_id` to use a ChildProcessId and then this won't be needed?
Correct, the end game for this patch set is in https://crrev.com/c/7621713, however that's rather large and so I've broken it up to get there slowly. I will be coming back to rectify this soon.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
content::ChildProcessId::FromUnsafeValue(Christopher StaiteWhy do we use FromUnsafeValue here? Neither the comment on the method nor the bug really give much context.
I'm assuming a follow up change will change `service_worker_version_info.process_id` to use a ChildProcessId and then this won't be needed?
Correct, the end game for this patch set is in https://crrev.com/c/7621713, however that's rather large and so I've broken it up to get there slowly. I will be coming back to rectify this soon.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
Sorry I missed this. extensions/browser/api/automation_internal LGTM
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Thank you. Could I get a CQ+2 pleasse?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Commit-Queue | +2 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
3 is the latest approved patch-set.
The change was submitted with unreviewed changes in the following files:
```
The name of the file: chrome/browser/extensions/chrome_content_browser_client_extensions_part_bindings.cc
Insertions: 2, Deletions: 4.
The diff is too large to show. Please review the diff.
```
Migrate AutomationEventRouter to ChildProcessId
Update `AutomationEventRouter` to use the strongly typed
`content::ChildProcessId` instead of raw integers for process IDs. This
change is part of a broader effort to replace unsafe integer process IDs
with strongly typed identifiers to improve type safety and reduce the
risk of ID mix-ups.
Since the function `RegisterListenerForOneTree` is unused, it was
removed rather than ported.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |