Linked by Thom Holwerda on Tue 24th Nov 2009 17:28 UTC, submitted by waid0004
Google has put up a very interesting document explaining the security features underlying its Chrome OS. The document also details the underlying guiding principles of Chrome OS' security features.
Thread beginning with comment 396175
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:2005-06-29
To put it bluntly, their notion of security is to make the OS a black box that the user cannot alter - that isn't of much use if you actual intend to let users run anything native on it...
It's completely open source. As such, your statement is rather incorrect, as anyone will be able to run whatever he wants on Chrome OS - you'll just need the proper skills.
Calling it a black box makes it seem as if it is closed source - which it isn't.
RE[3]: SRWare Iron OS
by Bill Shooter of Bul on Tue 24th Nov 2009 20:55
in reply to "RE[2]: SRWare Iron OS"
Member since:2006-07-14
I'm willing to be that chances are pretty good that google's hardware partners may "Tivo" the heck out of the hardware devices that run it. Especially, if its subsidized by 3G internet providers that are getting a share of the ad revenue. So it may be open source, but it might be non changeable on your hardware. Jail breaking (if it proves to be necessary) is going to be a bitch, with all of the security set up
Member since:2006-01-25
It's completely open source. As such, your statement is rather incorrect, as anyone will be able to run whatever he wants on Chrome OS - you'll just need the proper skills.
Calling it a black box makes it seem as if it is closed source - which it isn't.
Calling it a black box makes it seem as if it is closed source - which it isn't.
The fact that it is open source isn't really relevant to my point. Some one else beat me to it the Tivo analogy, but its a good one. Actually I expect the official hardware will probably be harder to hack than a Tivo, custom BIOS and all that. Come to think of it, is the BIOS work they are doing actually open source? I have heard nothing to that effect myself.
Anyways, you could probably run a fork of Chrome OS on your own (not blessed by Google) hardware... It may even be a useful thing to do. But that doesn't change the fact that Google doesn't much care about the capabilities of the underlying OS beyond their own purposes - they are not going to roll changes into Chrome OS that involve running user binaries or adding features that do not meet their internal needs. People should really take them at their word when they say it is for running web apps - that is ALL it is for.
So yes, Chromium OS may end up being useful to the community at large (although I doubt it), but Chrome OS never will be. This is much the same as Chromium vs Chrome (browsers) now - there are a lot of features in the multitude of community builds of Chromium that have not and will never find their way into Chrome itself.
News
Linked by Thom Holwerda on 05/21/13 15:53 UTC
The new WebKit Opera for Android has been released. "Opera 14 for Android is built on top of Chromium 26, with a total overhaul of the UI in native code, making it fit well with the latest Android design guidelines. Go get the build from Google Play or point your browser to m.opera.com, and give it a spin!"
Linked by Thom Holwerda on 05/20/13 22:43 UTC
The Verge pointed me to a blog post by Leap Motion - which reveals how their Kinect-like motion control works with Windows 8. "From the second you plug in your Leap Motion Controller, you'll be able to browse the web and interact with your computer just by moving your hands and fingers in the air. With Leap Motion technology and Windows, you can do everything that's possible with multi-touch inputs - without actually touching anything. This also means that existing applications in Windows 7 and 8 will respond to your natural hand and finger movements. Soon, we'll show you how Leap Motion will work with Mac OS X." Quite cool.
Linked by Thom Holwerda on 05/20/13 21:50 UTC
PocketNow interviews Marc Dillon, and there's an interesting note about why Jolla is keeping the display properties under wraps: "We're leaving some of those details out because we do understand that there are a lot of really big players in the market and they tend to take certain components in the market and dominate them. We created the ability to actually be able to run Sailfish on multiple hardware displays and be able to swap components, so this is part of the demand and supply planning phase. We are committed to this industrial design which is a 4.5-inch display, an 8 megapixel camera on the back and a front-facing camera at the front, and the exact specs of the display we'll provide when we're close to delivery." Something you rarely hear anything about.
Linked by Thom Holwerda on 05/19/13 23:15 UTC
"This is my NeXTstation Turbo Color booting the Mac System 7.1 Operating System using a hardware add-on called 'Daydream'. The Daydream has a Mac ROM and a few custom ICs in it and hooked up to the NeXTs DSP port. Turns your NeXT into a full fledged 68k powered Mac." So cool.
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
"The NetBSD Project is pleased to announce NetBSD 6.1, the first feature update of the NetBSD 6 release branch. It represents a selected subset of fixes deemed important for security or stability reasons, as well as new features and enhancements. Please note that all fixes in the prior security/bugfix updates (NetBSD 6.0.1 and 6.0.2) are also in 6.1."
Linked by Thom Holwerda on 05/18/13 21:06 UTC
"At the end of a week in which Electronic Arts confirmed it wasn't developing a thing for the Wii U, one of the software engineers in EA Sports' Canada studio, in a series of since-deleted tweets, disparaged the console as 'crap' and suggested Nintendo should give up on hardware altogether. 'The Wii U is crap. Less powerful than an Xbox 360. Poor online/store. Weird tablet', tweeted Bob Summerwill, listed as a senior software engineer at EA Canada, in a reply to a tweet posting a link about EA's no-Wii U news. 'Nintendo are walking dead at this point'." The Wii U is turning into the 21st century's Virtual Boy.
Linked by Thom Holwerda on 05/18/13 7:37 UTC
"In NixOS, the entire operating system - the kernel, applications, system packages, configuration files, and so on - is built by the Nix package manager from a description in a purely functional build language. The fact that it's purely functional essentially means that building a new configuration cannot overwrite previous configurations. Most of the other features follow from this." Interesting approach. A Linux distribution, sure, but with some very refreshing ideas about system configuration.
Linked by fran on 05/18/13 1:38 UTC
Appfour added, among other features, C/C++ support to its new version of AIDE. From Android-IDE, "Now you can write parts of your app or your whole app in C/C++ on your device. AIDE supports the Standard Android NDK toolchain (GCC 4.6 + Bionic, STL, ...). No changes are necessary if you want to build an app developed on a PC with Eclipse. C/C++ development is fully integrated: Build errors appear in the error list and files can easily be navigated to with Go to file. The editor supports C/C++ syntax highlighting."
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Ars nails it: "The answer is that Google did announce what amounts to a fairly substantial Android update yesterday. They simply did it without adding to the update fragmentation problems that continue to plague the platform. By focusing on these changes and not the apparently-waiting-in-the-wings update to the core software, Google is showing us one of the ways in which it's trying to fix the update problem."
Linked by MOS6510 on 05/17/13 22:22 UTC
"It is good for programmers to understand what goes on inside a processor. The CPU is at the heart of our career. What goes on inside the CPU? How long does it take for one instruction to run? What does it mean when a new CPU has a 12-stage pipeline, or 18-stage pipeline, or even a 'deep' 31-stage pipeline? Programs generally treat the CPU as a black box. Instructions go into the box in order, instructions come out of the box in order, and some processing magic happens inside. As a programmer, it is useful to learn what happens inside the box. This is especially true if you will be working on tasks like program optimization. If you don't know what is going on inside the CPU, how can you optimize for it? This article is about what goes on inside the x86 processor's deep pipeline."More News »
Sponsored Links
Member since:
2006-01-25
Google has no business interest in conventional OS development. Chrome OS is an engine for running a browser. Ive pointed this out before, and it doesn't seem to be a very popular opinion, but all Google wants in the end is a shim to but a browser on top of some hardware - the OS is the shim, and that is all it needs to be.
The fact that it has started out as essentially equivalent to a full Linux distribution is just for convenience to get the ball rolling. It won't be long before it gets whittled down to the bare minimum needed to run Chrome and thats about it. The point is that Google's goals do not at all coincide with Haiku's or even the goals of Linux for that matter - they are only interested in the OS to the point of enabling them to run their browser on as little hardware as possible.
Thats not to say they couldn't for instance use Haiku (instead of Linux) as their "OS" for running Chrome. Hell, that might even be a good idea. But would the Haiku project benefit much from that? To put it bluntly, their notion of security is to make the OS a black box that the user cannot alter - that isn't of much use if you actual intend to let users run anything native on it...