Some of the code revisions at the Chromium site are pointing to the fact that Abode Flash is now going to be sandboxed. This will arrive in the Canary and Dev Channels soon.
When the integrated PDF reader was released for Chrome and was sandboxed, I was already under the impression that Flash was too. It appears that wasn’t the case until now.
Just as a quick review, sandboxing is a security method for running separate programs. It is a big part of Chrome and a feature that has been rolled out in other browsers since Google first introduced it.
Google has provided Chrome with a baked-in Flash component for some time. This is a security feature that allows Flash to be silently updated as needed with security fixes and other improvements. The company has taken a very different stance to Flash than that of Apple which bemoans, perhaps legitimately, about the performance and stability of Flash.
Flash is a perfect candidate for sandboxing, but to technically get it accomplished was much more of a challenge that it was for the PDF reader in Chrome. That’s because some of the functionality that Flash provides in specific applications such as local file access or uploads would be hindered by it being sandboxed.
It remains to be seen if it will be an issue, yet it’s surely been tested by Google. Although some of the elements of Flash that made it dangerous may now be under control there may be problems running it for a small minority of purposes.
Do you think there will be issues with Flash being sandboxed?