GitLab

https://chromium-review.googlesource.com/c/chromium/src/+/1773861
changed the top-level bundle name to end in .app, since .bundle names
are not supported by the accessibility prefpane. However, it didn't go
far enough, as although ChromeRemoteDesktopHost is the bundle named in
the permissions prompt, it is the nested bundle, RemoteAssistanceHost,
that needs to be whitelisted.

This CL fixes this by renaming both the remote assistance and remote
access native messaging components to end in .app (the latter is not
necessary to fix this bug, but it shouldn't cause any problems and it
makes them consistent).

Users who upgrade Chrome to M78 and attempt to use remote assistance
before installing this CRD update will end up in a broken state because
the system will fail to whitelist the old RemoteAssistanceHost.bundle,
but will remember prompting the user and so will not do so again when
it is renamed to RemoteAssistanceHost.app. To avoid this, this CL also
changes the signing identity for RemoteAssistanceHost.app, which will
cause the system to ask for approval again. The signing identity for
the remote access native messaging component is not changed, because it
doesn't do anything that would cause it to be put onto any permissions
list.

Bug: 996993
Change-Id: If11ad4d2559e5a40f2f2b8c5ee98b630a976ac02
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1776699
Auto-Submit: Jamie Walch <jamiewalch@chromium.org>
Reviewed-by: Lambros Lambrou <lambroslambrou@chromium.org>
Commit-Queue: Lambros Lambrou <lambroslambrou@chromium.org>
Cr-Commit-Position: refs/heads/master@{#691848}