5 ms·
Market share: Windows 90%, Mac 9%, Linux 1%. Where are virus writers going to put most of their effort? Windows being as secure as Mac wouldn't help make it s
by melling 16y ago
Market share: Windows 90%, Mac 9%, Linux 1%.
Where are virus writers going to put most of their effort?
Windows being as secure as Mac wouldn't help make it safer because a lot more implemented exploits are going to exist in the wild.
- yummyfajitas 16y agoWhile this move may prevent infection by FR33_PR0N.wmv.exe, I don't see how it will prevent being hacked by China (the major concern).
- jimbokun 16y agoI believe the Chinese government has Windows source code, and Google does not. The Darwin and BSD layers of Mac OS X are open source, so Google can at least study the code to understand the security implications of using OS X. In other words, with open source Google is on a more level playing field against potential attackers.
- microkid 16y agoNo offense, but level playing field is ridiculous. Think about what you're saying, you're saying Google is going to sit there and review all of the source code, and all patches and new releases to that source code. Really? Do you actually believe this... As per China having the source, do you really think it matters? If someone wants to break in, they're going to get in... (regardless if its Windows/Linux/Mac) why... because that's their job and they are going to spend every minute of every day until they figure it out, and that's what makes them better than you. Majority of the time the issue is not software itself, but the policies in place. Hell, why even break in technically, when I can probably call one of these 10,000 employees up and they'll give me their password. Duh. If you believe security is 1-dimensional, then you are bound to fail. History has shown this time and time again, just read a book / biography in regards to this topic.
- pook 16y agoMore importantly but less vociferously, by Google switching to an open source OS, it means anyone, anywhere, can fix vulnerabilities. Not just Google. Considering the difficulty of patching security holes in proprietary software versus patching holes in open software, Google indeed would hugely benefit by drastically reducing the difference between the cost of defense and the cost of cracking. It's not so much levelling the playing field, as removing Harrison Bergeron's buckshot-filled equality harness.
- jlmendezbonini 16y agoSwitching to an open source OS? OSX is a mix between open and closed source software where quite a bit of its open source code is not updated frequently. Google can't patch Preview, Quicktime, Safari or any other closed source program develop by Apple. Also, Apple is not famous for quickly patching OSX[1]. Quoting Charlie Miller[2,3]: "Mac OS X is like living in a farmhouse in the country with no locks, and Windows is living in a house with bars on the windows in the bad part of town."[4] [1] http://www.zdnet.com/blog/security/apple-fixes-old-java-for-mac-security-holes/6491 http://www.zdnet.com/blog/security/apple-fixes-old-java-for-... [2] http://www.dailytech.com/Charlie+Miller+to+Unveil+20+Zeroday+OS+X+Exploits+at+CanSecWest/article17934.htm http://www.dailytech.com/Charlie+Miller+to+Unveil+20+Zeroday... [3] http://en.wikipedia.org/wiki/Charlie_Miller_(security_researcher) http://en.wikipedia.org/wiki/Charlie_Miller_(security_resear... [4] http://www.forbes.com/forbes/2010/0412/technology-apple-hackers-charlie-miller.html http://www.forbes.com/forbes/2010/0412/technology-apple-hack...
- naz 16y agoGoogle employees probably won't be using Safari but it is 95% open source (WebKit). iTunes would be a better example.
- nailer 16y ago> you're saying Google is going to sit there and review all of the source code, and all patches and new releases to that source code. Really? Do you actually believe this... It's not crazy to pay someone on their security teams to review checkins to OSS apps they use. Saying 'OH MY GOD' loudly and repetitively doesn't consitute an argument and is rude to the parent poster. Be civil.
- pmjordan 16y agoI'd be extremely surprised if Google didn't have access to the Windows source via Microsoft's shared source programme.
- tptacek 16y agoThe source code to Windows, while not public, is some of the best studied in the world both inside and out of Microsoft. Even though MSFT doesn't publish it, they do release complete debug symbols for most of the operating system; there isn't a pro vulnerability researcher on the Internet that can't navigate Windows with a copy of IDA Pro and a couple of PDBs. The openness of the Windows source code is a red herring. Meanwhile, most bugs aren't discovered in careful source code review or by static analysis tools. Instead, we write programs to exercise the code, either by sending random dumb buffers to the target or by working out the expected format and varying messages until we cover every basic block in the target. You can do this with or without any source code. I think you would have a hard time finding a professional to say that they trust Mac OS X dramatically more than they trust WinAPI in 2010, and I say this as a full-time Mac user.
- butterfi 16y agoI, for one, am pretty bored by the market share defense. There are millions of macs out there, owned by people who could drop a little coin on their hardware, and that make them less of a target? There's not one virus writer out there who doesn't want the cred and the potential gain of a new audience of victims, many of whom are probably pretty complacent about security because they've never had to worry about it? There aren't many mansions where I live, yet they seem to need the most security.
- spicyj 16y agoWhile you might liken the rarity and the glamour of owning a Mac to that of owning a mansion, a thief has much more to gain by targeting a large house that's more likely to be filled with expensive electronics and jewels. On the other hand, I doubt that Macs are significantly more likely to contain data that a hacker would be looking for.
- malkia 16y agoBad analogy. Software != hardware literally.
- robin_reala 16y agoHackers don’t want to sift your personal data for the most part (unless the sifting can be automated). It’s botnets that make them money.
- julio_the_squid 16y agoIt depends what you're up to, I suppose. If you were seeking to install keyloggers to record financial authentication details, why not target people whose choice of computer hardware indicates they have more money than average?
- tptacek 16y agoBecause Windows vs. Mac is an exceedingly weak financial signal, and because no matter what the signal is, having 20-30 accounts is better than having just 1 account?
- beagle3 16y agoAnd yet, when you looked at e.g. the web server data back in the early 2000's, you had 70% apache 25% IIS -- and yet about 20 times as many exploits (and much more effective at that) for IIS. The reason was, to put it bluntly, that IIS was designed without any regard to real security, whereas Apache had _some_ regard to security. That's also the case for Windows through its history; it has been making leaps recently, but doing things more securely requires it to become less convenient / not backwards compatible, and therefore it is still, relatively speaking, way more vulnerable when used by your average user. I'm not up-to-date, but up until 2007 or so, a significant number of web browser vulnerabilities were directly or indirectly a result of Windows and Explorer's love of executing files after wrongly identifying them as e.g. wav or doc files. The single Unix design decision that a file must have an executable flag out-of-band, and the convention that by default this flag is off, both of which date back to 1970, have kept Unix safe from these kinds of bugs. Sane default permissions on system directories are another decision; the latter has been adopted by Windows in XP SP2 IIRC, the former still hasn't.
- tptacek 16y agoI would like to hear the specific ways in which you think that Apache was designed for security in ways that IIS wasn't, and how those things persist into modern IIS.
- adolph 16y agoNot a serious reply: Well, for one, IIS was designed to run on Windows servers rather than *nix.
- tptacek 16y agoRejoinder in equivalent tone: you mean, the servers that ran rexd, the "run any command for me without credentials" RPC service? Or the servers that had remote calendar managers that would run commands for anyone who knew what the semicolon character meant to the shell? Or the ones that got confused if you sent FTP commands in the wrong order and too fast and would accidentally upgrade you to root instead of logging you off?