Re:SSH client in Google Chrome
by comex on Thursday January 17, 2013 @04:10PM
(#5075239)
What if the attacker compromised the GPU process without compromising the entire sandbox? If hardware compositing is on, they could snoop on the SSH window contents. (Then again, they might be able to do that even with a separate application...)
[ Parent
| on HN ]
Re:SSH client in Google Chrome
by justinschuh on Friday January 18, 2013 @12:20AM
(#5077270)
Yeah, the GPU process can do this regardless due to the way Windows forces any accellerated GPU app to work. I'm not sure if you dug into this before, but the GPU does run as low-integrity for UIPI purposes on the interactive desktop (lower for other object access). Unfortunately, the desktop window, screen, and display state are still exposed at that level. We're digging into AppContainers to see if tighter restrictions are possible on Win8, but usage is still so low that it's not a priority.
Re:SSH client in Google Chrome
by justinschuh on Friday January 18, 2013 @10:16AM
(#5078999)
Sorry I focused solely on Windows, but to my knowledge all platforms we support have similar architectural niggles in terms of the GPU process being able to read anything that's displayed.