Surface IDs in Chrome are guessable and so a compromised renderer could potentially embed privileged content such as browser UI or the Chrome OS System UI. We should make sure that surface IDs are not guessable. SurfaceId should consist of two components:
1. 32-bit namespace (we have that now)
2. 64-bit process-local ID that is randomly generated: this needs to be introduced.
This change ensures that one renderer cannot guess surfaces of other clients.
Comment 1 by fsam...@chromium.org
, May 19 2016