Linked by Thom Holwerda on Tue 23rd Sep 2008 15:38 UTC
"Since its release a few weeks ago, curious developers have been sniffing through the source code for Google's new Chrome web browser. Chrome's source is interesting for a variety of reasons: there's the new V8 JavaScript virtual machine with its boasts of near-native code performance, the WebKit rendering engine that does all the hard work of understanding and displaying web pages, and (last but not least), Chrome's secure sandbox designed to minimize the impact of any security flaws that might exist in both the browser and plugins alike. It is this secure sandbox that has piqued the curiosity of some observers, and for a reason that many may find surprising. From reading the source, it looks as though Google has reverse-engineered Windows, and that's explicitly prohibited by the Windows EULA."
Permalink for comment 331229
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Member since:
2005-07-06
Yes. But on the other hand, if there's something desirable that you can achieve only by using undocumented calls, it basically means that as an API provider you have failed the developers.
The security features implemented by chrome using undocumented calls are desirable. So maybe the calls won't work anymore in the future, but then again microsoft is at fault for not providing an official and documented api to access these features.