Didn't Google pay for a student to the naclssh port as part of the code of summer project?
Something tells me such limitations will be temporary...
"This allowed us to remove the expiration date and localhost security restrictions we had adopted in previous research-focused releases.
We are excited to see Native Client progressively evolve into a developer-ready technology. In the coming months we will be adding APIs for 3D graphics, local file storage, WebSockets, peer-to-peer networking, and more."
AFAIK the security limits are intentional and when they add new NaCl APIs they will have the same restrictions as the equivalent JS version of the API. NaClets that run within an "app" instead of a "page" may be able to bypass some restrictions, though.
Something tells me such limitations will be temporary...
"This allowed us to remove the expiration date and localhost security restrictions we had adopted in previous research-focused releases.
We are excited to see Native Client progressively evolve into a developer-ready technology. In the coming months we will be adding APIs for 3D graphics, local file storage, WebSockets, peer-to-peer networking, and more."