Originally Posted by quantumstate
Well, good point Eric, LOL. RGB's mission
is to bring people over to Linux, but it is also true that data sent to that-search-engine-everyone-uses is not being used as you intend. I've seen search histories pulled, and it is scary how completely a profile of someone can be drawn from their searches. In the EU they have strong privacy and data retention laws, which are absent here. Think about it; most ppl think nothing of turning over their searches, contacts, calendars, network of all their friends, their location at every moment, their texts, their voicemails, and in fact their very phone calls to the Greatest Data Mining Operation In The History Of The World. If you had any way of appreciating what a bonanza this for criminals, cops, hackers, intel agencies, detectives, etc, you would throw that Information Radiator in the toilet.
For the record, I have an Android phone, but I run hacked firmware, and I use a number of security tools on it.
FOSS is not about Free Speech
. It's about more, the freedom to do what you want. The freedom to maintain your privacy if you are so inclined and technically able. It's also about free software, and running the safest peer-reviewed applications possible.
Yes, since this thread was started, I've been over-the-top occasionally on the "mission" part
The Idea of the user/consumer owning/controlling their PC software and its operation is a powerful one. However, the Market demands profit and return on investment, which explains why given the opportunity to completely control your PC and maintain your computing freedom/privacy/etc with FOSS OS's, consumers choose otherwise. Rather, businesses (commercial interests) and investors choose otherwise.
This exercise in personal computing freedoms will go down in the history books as a Grand sociological experiment, .
Interesting to note that a Linux OS company RedHat (RHT) provided better returns to investors from 2009 through today vs MSFT. No, RHT is not a desktop OS company, but FOSS versions for the desktop are available (CentOS, Fedora, etc). I was hoping another company like Canonical might provide similar financial market success to the desktop, but commercial and investor returns appear elusive for anyone attempting a desktop/consumer OS based on linux. ChromeOS, future Android versions and/or the new Android-kernel Ubuntu (announced for phones/tablets) may be promising.
Chrome OS Remains Undefeated At Pwnium 3
Google has announced that its Chrome OS has managed to remain undefeated during the Pwnium 3 event that was held alongside Pwn2Own. Announced by Google on January 28, 2013 the Pwnium 3 event carried a prize money of $3.14 million. Researchers were asked to carry out attacks against a base Samsung Series 5 chromebook running the latest stable version of Chrome OS. It turns out security researchers were not able to come up with winning exploits even after the competition's deadline was extended. Google Chrome Team has revealed that partial exploit entries have been filled in but, no other details have been released.
But considering the fact that none of the browsers were able to withstand the attacks of crackers on the Windows platform at Pwn2Own, it is a safe bet to assume that Linux in general and Chrome OS in specific may be an ideal choice for security conscious users across the globe.
While not a candidate for a DIY HTPC (yet), ChromeOS does use the Linux kernel (as all other Linux distros used for HTPC's) and will likely become more desktop-OS-like moving forward. ChromiumOS is the FOSS counterpart-
Nice technical summary why ChromeOS is so secure-
A major theme here is "it doesn't run many apps, that's why it's secure". Yeah, that must be it - it probably has absolutely nothing to do with the way they've implemented Mandatory Access Controls in a rigorous fashion, and the way they isolate resources with heavy use of cgroups, and the read-only root filesystem and tmpfs /tmp, and how they've made every binary use ASLR and NX and DEP, and how they've rewritten several major typically-vulnerable daemons to not run as root, and how they've developed userland daemons to broker access to hardware, and how they don't allow any files in user home dirs to be executables, or how they've started to sandbox device drivers, or the way they implemented separate processing stacks for HTTP and HTTPS, or how they verify not just the boot record but the whole boot stack and partition table and nv ram on every boot and and and ...
Yeah, all those things probably don't matter. They probably don't play any role in exploits that work on Windows-based Chrome failing on Chrome OS. It's not more inherently secure than any other OS, riiiggghhhhhttttt ...