Google has begun work on the first step of rebuilding Chrome from the inside out on a more secure foundation called Native Client, CNET has learned.
That first step is the built-in Chrome module used to let Google's browser read PDF (Portable Document Format) files. Linus Upson, vice president of engineering for the Chrome team, revealed the plan in May at the Google I/O conference, and now evidence is emerging that the first step is under way.
References to the Native Client version of the PDF extension have begun cropping up on the Native Client's bug-tracking database. Programmers are encountering problems with scrollbar rendering, Gmail integration, loading PDF files, and displaying URLs when the mouse pointer hovers over a link
Some are tagged with a Chrome 14 completion schedule. That's not a commitment that the bugs will be fixed in time for the current version of Chrome under development, but it does indicate that the work is for a near-term project, not a distant idea.
Google initially pitched Native Client as a way to accelerate Web applications to native-app speeds. It demonstrated its use in processor-intensive operations such as photo manipulation and playing the game Quake. At Google I/O this year, though, CNET learned that. That would add an extra layer of security to the software and make it that much harder for someone to exploit the browser--or the Chrome OS operating system--as a vector for an attack.
For now, Native Client is a plug-in built into Chrome rather than the other way around. It uses a plug-in interface called Pepper. Note that NaCl is the chemical abbreviation for sodium chloride, better known as salt.
It's not clear exactly how long it will take to rebuild all of Chrome atop NaCl. Native Client itself isn't finished; for the present it's off by default, though people can experiment with it by enabling it by typing "about:flags" into the address bar.
The company is proceeding cautiously.
First, "we have to make sure Native Client proves its way,", said in a May interview.
"I'd say it's a dream more than a plan right now," added Brian Rakowski, director of product management, speaking of the effort to rebuild Chrome on NaCl.
Nevertheless, it shows the extent to which Google wants to make security a selling point for Chrome and Chrome OS. With Chrome, Google led the charge tothat silently replaces itself with new versions. That means Chrome--or built-in components such as Adobe's Flash Player--can rapidly be replaced to shut down a newly discovered vulnerability.
Of course, it also means software can change without its users getting a say-so, but Google believes the tradeoff is worth it. That's especially the case with Chrome OS, which functions as an operating system, not merely a Web browser.
"In the Windows ecosystem, you assume the user is taking care of all of this," Pichai said. Google believes online software distribution can put the responsibility back where it belongs, with the software's maker.
The company stands to directly benefit from greater browser security. For example, Gmail users were the target of at least two serious hacking attempts the company said originated in China, and an Iranian attack could have granted a malicious third party an ability to.
So now,so Gmail can only be used over a secure connection and so secure Google sites require an encryption certificate from a short list of trusted providers.
New security risks?
One of the big factors for Native Client is that it potentially opens new security vulnerabilities. It is, after all, a new interface for executing software that isn't available today.
, though. And Google got a modest endorsement from none other than John Carmack, the iD Software programmer who created Quake and Doom.
Carmack compared Native Client to WebGL, a new standard for building hardware-accelerated 3D graphics into the Web. WebGL has come under security scrutiny by Microsoft and others.