Slashdot Mirror


Mac OS X Security Criticisms Countered

Paradox writes "In response to the recent PC Magazine story criticizing Mac OS X security, technologist/author Richard Forno has written a rebuttal criticizing the author and raising some good points about the fundamental differences between Windows and Mac OS X. Considering Lance Ulanoff's tone during his article, a rebuttal from the Mac OS X community was inevitable." Forno's conclusion: "Trustworthy computing must be more than a catchy marketing phrase. Ironically, despite a few hiccups along the way, it's becoming clear that Mac OS, not Windows, epitomizes Microsoft's new mantra of 'secure by design, default, and deployment'."

464 comments

  1. Slow site by Anonymous Coward · · Score: 5, Informative
    article text, reprinted as permitted by author. Enjoyez-vous.

    Muckraking, the PC Way
    Richard Forno
    12 Dec 03
    Copyright (c) 2003 by Author. Permission granted to reproduce in entirety with credit given.


    Richard Forno is a security technologist, author, and the former Chief Security Officer at Network Solutions.


    Since Apple released Mac OS X, even the PC industry trade publications have raved about its quality, design, and features. PC Magazine even gave Mac OS X "Panther" a 5-star rating in October 2003. Perhaps it was because Macs could now seamlessly fit into the Windows- dominated marketplace and satisfy Mac users refusing to relinquish their trusty systems and corporate IT staffs wanting to cut down on tech support calls. Whatever the reason, Mac OS X has proven itself as a worthy operating system for both consumers and business alike.

    Of course, as with all operating systems, Mac OS X has had its share of technical problems and even a few major security vulnerabilities. Nearly all were quickly resolved by Apple via a downloaded patch or OS update. But in general, Mac OS X is solid, secure, and perhaps the most trustworthy mainstream computing environment available today. As a result, Mac users are generally immune to the incessant security problems plaguing their Windows counterparts, and that somehow bothers PC Magazine columnist Lance Ulanoff.

    In a December 11 column [1] that epitomizes the concept of yellow journalism, he's "happy" that Mac OS X is vulnerable to a new and quite significant security vulnerability. The article was based on a security advisory by researcher Bill Carrel regarding a DHCP vulnerability in Mac OS X. Carrel reported the vulnerability to Apple in mid-October and, through responsible disclosure practices, waited for a prolonged period before releasing the exploit information publicly since Apple was slow in responding to Carrel's report (a common problem with all big software vendors.) Accordingly, Lance took this as a green light to launch into a snide tirade about how "Mac OS is just as vulnerable as Microsoft Windows" while penning paragraph after paragraph saying "I told you so" and calling anyone who disagrees with him a "Mac zealot."

    In other words, you're either with him or with the "zealots." Where have we seen this narrow-minded extremist view before?

    More to the point, his article is replete with factual errors. Had he done his homework instead of rushing to smear the Mac security community and fuel his Windows-based envy, he'd have known that not only did Apple tell Carrel on November 19 that a technical fix for the problem would be released in its December Mac OS X update, but that Apple released easy-to-read guidance (complete with screenshots) for users to mitigate this problem on November 26. Somehow he missed that.

    Since he's obviously neither a technologist (despite writing for a technology magazine) nor a security expert, let's examine a few differences between Mac and Windows to see why Macintosh systems are, despite his crowing, whining, and wishing, inherently more secure than Windows systems.

    The real security wisdom of Mac OS lies in its internal architecture and how the operating system works and interacts with applications. Its also something Microsoft unfortunately cant accomplish without a complete re-write of the Windows software -- starting with ripping out the bug-riddled Internet Explorer that serves as the Windows version of "Finder." (That alone would seriously improve Windows security, methinks.)

    At the very least, from the all-important network perspective, unlike Windows, Mac OS X ships with nearly all internet services turned off by default. Place an out-of-the-box Mac OS X installation on a network, and an attacker doesnt have much to target in trying to compromise your system. A default installation of Windows, on the other hand, shows up like a big red bulls-eye on a network with numerous network services enabled and running. And, unlike Win

    1. Re:Slow site by Anonymous Coward · · Score: 0

      STFU troll.

      Besides, like most people here I doubt you would pay for anything.

    2. Re:Slow site by palad1 · · Score: 2, Insightful

      Enjoyez-vous.

      Ah nom de dieu c'est fou ce que je m'enjoie la, thanks dude, best cyber ever :)

      Side note: Did any euro mac /.er out there take advantage of the euro / dollar exchange rate to buy an us mac? A 2000 dollars powerbook costs 3000 in France, given the exchange rate that's, well, a sweet commission for apple store france!

    3. Re:Slow site by Anonymous Coward · · Score: 0

      Take his points one by one:

      1. Default services turned off - Right on with this one. One of the basics of security. Turn off what is not needed. OS X's default configuration was well thought out from a security perspective.

      However I would counter that Microsoft, due to backward compatibility, has to have some things enabled. Otherwise it would disrupt users. Apple was lucky with OS X in that they didn't have to maintain backwards compatibility.

      2. DLL Hell - Not sure why this is a security issue.

      3. Patches that add DRM - While not what I want to see I'm not certain what this has to do with security (aside from you can't patch your system unless you accept the new technology).

      4. Administrative password - This is enforced by the installer when installing applications. One can simply copy files into the /Applications directory if they're a member of the administrators group. This is a big misconception about OS X's security. The installer, not the OS, asks for the password. Do not trust in this.

      5. Scripting is not required in order to enable a trojan to spread. If it's written in the systems native language it can execute.

      6. Market size - Like it or not malicious code development, just like non-malicous applications, is going to be significantly lower than on the Windows platform. This is just common sense. Anyone who argues otherwise is just burying their head in the sand.

      Richard's counter arguments were not that convincing.

    4. Re:Slow site by Anonymous Coward · · Score: 0
      4. Administrative password - This is enforced by the installer when installing applications. One can simply copy files into the /Applications directory if they're a member of the administrators group. This is a big misconception about OS X's security. The installer, not the OS, asks for the password. Do not trust in this.

      Why do you talk about things you know nothing about? The installer asks for an administrator password if the permissions on the /Applications dir are such that the user needs more privs to install there. Retard.

    5. Re:Slow site by Anonymous Coward · · Score: 0

      Why do you talk about things you know nothing about? The installer asks for an administrator password if the permissions on the /Applications dir are such that the user needs more privs to install there. Retard.

      The permissions are such that anyone in the "admin" group has full access to the "/Applications" directory. The OS is not enforcing a requirement of asking for a password in order to write to the "/Applications" directory...the installer is. Thus a trojan could easily install itself by not using the installer...it can provide its own method (such as simply copying itself) to install itself into the "/Applications" directory.

      If you don't believe me you're welcome to perform the following:

      1. Open a command prompt (Terminal program located in the /Applications/Utilities folder) from a user account that is an administrator (not a root account).

      2. Type the following command: "rm -rf /Applications"

      Let me know if you were prompted for a password prior to erasing most of the "/Applications" directory.

      Now a word to the wise: If you're going to call someone a retard and accuse them of not knowing what they're talking about then you better damn well be certain that you know what you're talking about. Because, as you just did, you'll only look like a retard yourself.
    6. Re:Slow site by TechniMyoko · · Score: 1

      re: Richard's counter arguments were not that convincing. I agree, it seemed like he was just lashing out like one of those zealots in the other article. His statements were irrelivant

    7. Re:Slow site by Anonymous Coward · · Score: 0
      2. DLL Hell - Not sure why this is a security issue.

      Firstly, if your "Not sure", then why the hell do you even reply?

      DLL Hell involve the DLL files which are used by programs, including the MS OS itself.

      What happens is a program (or trojan) is "allowed" to replace an important DLL file with it's own. Since a DLL file can contain any code the author of the DLL wishes ... have a guess at why it is a MAJOR SECURITY PROBLEM.

    8. Re:Slow site by Anonymous Coward · · Score: 0

      Actually it made a hell of a lot more arguments for MacOSX than you realize.

      If you read the article, which it appears you haven't. Richard has given MANY valid points on why you shouldn't use MS software at all.

      It took a MS application to provide a [macro] vulnerability in MacOSX, but this vulnerability can not ruin the OS like it can to MS Windows.

      Wake up ffs. If you ever have your own business and a computer malfunction can ruin your life, don't even think of MS software. There are many alternatives such as Sun Solaris which provides a secure version. The hardware is expensive, but if "a computer malfunction can ruin your life" ...

    9. Re:Slow site by Anonymous Coward · · Score: 0

      Apple HAS backwards compatibility. Still, Appletalk is off by default. Go and give yourself a password and then check the "Enable" checkbox, and you're set.

    10. Re:Slow site by Anonymous Coward · · Score: 0

      I have a cousin who will visit Europe to "smell" the joys of Amsterdam, and he has his suitcase full with nice hardware. With these Euro/Dollar exchange-rates, and the low taxes in the US (and our high taxes overhere being 19%), Bestbuy.com looks like a friggin candy-store. ;-)

    11. Re:Slow site by davesag · · Score: 1
      Side note: Did any euro mac /.er out there take advantage of the euro / dollar exchange rate to buy an us mac? A 2000 dollars powerbook costs 3000 in France, given the exchange rate that's, well, a sweet commission for apple store france!

      sure did. i flew to the usa, bought a tibook and after paying for flights for my and my gf, still came out well ahead.

      I just started a new job in holland and they asked me to spec out the development machine i wanted. i specced out a dual g5 and the price diff in holland vs the us is well over 2k euro. unfortunately you can't just fly the us and stick a g5 + cinema display in your backpack like a tibook, or that's what I would have done and spent the difference on 8GB ram!

      --
      I used to have a better sig than this, but I got tired of it
    12. Re:Slow site by Anonymous Coward · · Score: 0

      2. DLL Hell - Not sure why this is a security issue.

      Firstly, if your "Not sure", then why the hell do you even reply?

      DLL Hell involve the DLL files which are used by programs, including the MS OS itself.

      What happens is a program (or trojan) is "allowed" to replace an important DLL file with it's own. Since a DLL file can contain any code the author of the DLL wishes ... have a guess at why it is a MAJOR SECURITY PROBLEM.

      I cannot see the connection between managing DLL's and security. Keeping an open mind I made the statement "Not sure why this is a security issue." in the hope that someone may show me the connection. Your explaination doesn't do it. The same could be said of library files in OS X.

      There's a difference between replacing files and the proper management of DLL's/library files. Please do try an learn a little more about what you speak before speaking.
  2. ok.. by junkymailbox · · Score: 5, Funny

    not much comparison when you start comparing your security to windows security.

  3. Attacking the author by goldspider · · Score: 5, Insightful
    I did RTFA, and it would seem to me that the rebuttal would have sufficiently stood on the merit of the facts, without all the sniping at Ulanoff.

    Tho Forno is mostly correct in his assertions, I would take him MUCH more seriously if his argument wasn't riddled with immature name-calling.

    --
    "Ask not what your country can do for you." --John F. Kennedy
    1. Re:Attacking the author by palutke · · Score: 4, Interesting

      As a rule, I treat everything that a 'technologist/author' says as worthless until they prove otherwise. It seems that 'technologist' is one of those titles that people attach to themselves when they don't posess any useful skills (to me, anyway).

      As the parent said, this guys facts seem solid, but his attitude makes it difficult to take him seriously.

      --
      'I ain't a liar, baby, and I ain't proud I just want what I'm not allowed.' -- Violent Femmes, 36-24-36
    2. Re:Attacking the author by Bill,+Shooter+of+Bul · · Score: 4, Insightful

      Exactly. The original article may have been flaimbait, but it really didn't require another article to point out all of the obvious flaws. Even if it did, this author could have avoided sinking to his level.

      --
      Well.. maybe. Or Maybe not. But Definitely not sort of.
    3. Re:Attacking the author by Oculus+Habent · · Score: 5, Insightful

      Every work day, I use Mac OS X 10.3, Windows XP Pro, 2k Pro, NT 4, and 98 - sometimes 95, too. I like my Mac. I could go into why, but no one asked me, so I won't. How the original story managed to make some sort of grade for acceptability at PC Magazine makes me less interested in the publication.

      I concur will your view - the correct answer, said rudely, still isn't right.

      --
      That what was all this school was for... to teach us how to solve our own problems. -- janeowit
    4. Re:Attacking the author by Anonymous Coward · · Score: 0

      you're too right.

      a *mostly* well written article brought down by the author straying from a factual rebuttal into a mud slinging competition.

      dreadz
    5. Re:Attacking the author by On+Lawn · · Score: 4, Funny

      So in short,

      Technologist is to technology what Waitress is to acting?

    6. Re:Attacking the author by Anonymous Coward · · Score: 0

      I RTFA, too, and I didn't see any name calling. Forno attacked the argument and not the man -- which is well within the bounds of a good debate.

      What really surprised me is Forno's credentials. Former Chief Security Officer at Network Solutions? As I recall, their security has always been fairly worthless -- at least when it comes to protecting the domain names.

      Beyond that, I've got no gripes with his rebuttal. It was well composed.

    7. Re:Attacking the author by ThosLives · · Score: 1
      he correct answer, said rudely, still isn't right.

      Um... please help me understand this one. Does this mean if you say a truth meanly, it's not true? I think you need to clarify that it is the rudeness, not the factuality, which is in question. The ambiguity of the English language leaves too much room for such things, and often just gets people mad at each other.

      Say what you mean, and mean what you say.

      --
      "There are a dozen opinions on a matter until you know the truth. Then there is only one." - CS Lewis (paraprhase)
    8. Re:Attacking the author by killmeplease · · Score: 1

      If you read the first article you would agree that there are no mentions of the underlying UNIX architecture that has withstood 30 years of limited security breaches and the Windows platform that is 10 years old and has a mrket niche of software engineers working on blocking viruses that any 15 year old kid can make and practically deisable a Windows machine. I can't say the same for Mac OS X. It seems appropriate to me that the author of the rebuttal put the author of the first article in his place and mention that he does not have much knowledge of the bigger issues that make Macs superior

      --
      - Kill Yourself, spare us all! -
    9. Re:Attacking the author by Anonymous Coward · · Score: 0

      *golf clap*

      Nice.

    10. Re:Attacking the author by mikewolf · · Score: 1

      um, i think its a quip...

      correct vs. right i think implies factual correctness vs. moral justness...

      you're correct though, it is a little ambiguous (but wait, are you right?)

    11. Re:Attacking the author by MikeMc · · Score: 1


      A Technologist is to technology what a gynocologist is to women.

      --
      Marco...that was Portugese.
    12. Re:Attacking the author by The+Infamous+Grimace · · Score: 1

      "...dragged him behind a '47 ford pickup down a gravel covered southern road myself:)..."

      -1, Tasteless

      --
      Ignorance and prejudice and fear
      Walk hand in hand
    13. Re:Attacking the author by Anonymous Coward · · Score: 0

      I'd agree except that it doesn't help in the marketplace. If the rebuttal was quiet and concise, no one would discuss it so both the facts and OS X would be easily swept under the rug. Since it was less refined (an understatement to be sure) it will keep things lively and the Windows readers WILL know the other side even if they don't believe it. It's just a 'society thang' IMHO..

    14. Re:Attacking the author by vantango · · Score: 1

      Sure it did! Such an obvious attack on the Mac community needed an equally responsive reply to the author. Lance Ulanoff needed to be put back in his place. Richard Forno's rebuttal dissected the article and couldn't ignore the flamebait. At no stage did the rebuttal sink to the blatant taunting of the original.

    15. Re:Attacking the author by Bill,+Shooter+of+Bul · · Score: 1

      read my reply to the first reply to my original post here

      It addresses your concerns.

      --
      Well.. maybe. Or Maybe not. But Definitely not sort of.
    16. Re:Attacking the author by Anonymous Coward · · Score: 0

      Aren't you late for your Klan meeting, Mr. Thurmond?

    17. Re:Attacking the author by poot_rootbeer · · Score: 1

      The original article may have been flaimbait, but it really didn't require another article to point out all of the obvious flaws.

      Maybe to the Slashdot crowd no rebuttal was necessary to the original article's "obvious flaimbait". But what about PHBs?

      If they read one article titled "MacOS = teh suXor", they might come to the conclusion that MacOS is The Suxor. But if they read a second article, title "No, Windows = teh suXor", they would instead come to the conclusion that BOTH platforms are The Suxor -- or at least, that they need more information before they can make a decision.

    18. Re:Attacking the author by Negativeions101 · · Score: 0, Flamebait

      Shut the fuck up... he deserved to be attacked for his stupidity... oh, now it's flamebait. Great, let us all flame him. He deserves it. Besides, the seemingly "obvious" truth about how shitty Windows is never be stated too many times. If not for slashdotters, then anyone who happens to come across the write-up.

      --

      I'm not anti-microsoft. I'm anti-bullshit. Which means I'm anti-microsoft.
    19. Re:Attacking the author by Onan · · Score: 2

      Yeah, or put him in a camp with a bunch of his buddies, and slowly gas them all to death! Or torture him until he confesses to being a witch, and burn him alive! Or nail him to some planks and let him hang there until he dies of exposure!

      Um. Glorifying the horrible things that've been done to other people by suggesting them as appropriate consequences for writing a dumbass article seems like a little uncouth, eh?

    20. Re:Attacking the author by MrLint · · Score: 0, Offtopic

      Sir,
      Your point does not go unnoticed. However I am sick to death of listening to the BS of trolls be regurgitated by (and i dont know how nature allows this) the more ignorant and more stupid.

    21. Re:Attacking the author by Inuchance · · Score: 1

      To borrow a quote from bash.org, "Never argue with an idiot. They'll bring you down to their level and beat you with experience."

    22. Re:Attacking the author by Anonymous Coward · · Score: 0

      The original article was asking for a rebuttal. Read the last sentence of the article. Only Lance did not give any avenue for a response (coward). Facts are facts & to be as irresponsible as Lance was to right this article he deserved to be called on it. This article was also posted on the ABC news' website. It was childish & factually incorrect. This guy is giving his "expert" opinion to people who may not be as knowlegdable as some in this forum. A normal person reading this article may form a false opinion about Apple & Mac OSX. This may effect their purchasing decision. That is just plain sleazy. I thought that Mr. Forno showed great restraint. I did not see any name calling. I little attitude, but Lance deserved it. Flamebait? A so called "professional" should not have to resort to such tactics. A lie is a lie, bullshit is bullshit. People should be called on it.

    23. Re:Attacking the author by Anonymous Coward · · Score: 0

      If you were familiar with WHO Richard Forno is, you would not be so flippant about his rebuttal to Lance Ulanoff's article. Forno is the former CSO (Chief Security Officer) of Network Solutions Corporation -- and if you don't know what company that is, then your ignorance is even worse than I feared. Let's just say that Forno has a lot of cred in the IT security world, and Ulanoff has NONE. I already e-mailed Ulanoff, and he read my note. I told Ulanoff that he was ignorant and juvenile, which pretty much describes the vast majority of those who post to Slashdot.

    24. Re:Attacking the author by MacDork · · Score: 2, Insightful

      this guys facts seem solid, but his attitude makes it difficult to take him seriously.

      I took him a lot more seriously than Lance. Wanna know why? It's not because I am biased toward the Mac (Which I freely admit), but because his page is devoid of advertising.

      That's right, he's not trying to sell me something through a banner ad. His writing is personal conviction, not whoring for ad money. The PCMag article is surrounded by hundreds of links trying to sell you something, various banners and a flash ad. The intention is simple, piss off a bunch of mac users to get them to stop by and maybe buy something on their way out.

      BTW, his attitude is very tame compared to what you'll get back from most die-hard mac users.

    25. Re:Attacking the author by ahknight · · Score: 1

      This is when you look at one of the other rebuttals:

      codepoetry
      MacObserver

  4. trust by rwven · · Score: 4, Interesting

    the bottom line is which are you going to trust anyway? the only computer that i would fully trust to protect my stuff would be a gentoo linux box custom made for a specific purpose. Self patching and very few applications installed for a person to take advantage of. the bottom line is though XP and Mac OSX may be "secure" they're not secure enough for anything important. (in my humble opinion.) I also work at a place where security is EVERYTHING so i guess i see it different... This pointless blathering about security shoudl convince no one of anything, especially when zealots are concerned.... I say use whatever works best for what you are doing. if you want REAL security, you shouldnt use either of those OS's

    1. Re:trust by the_consumer · · Score: 0

      Try BSD.

      --
      "If you're thinking what I'm thinking, you're right." -
    2. Re:trust by EnormousTooth · · Score: 1

      Agreed, but right now emerge -u world can break your system very badly.
      I've heard they're going to put a emerge --security in portage, so that'll help a little.
      Right now Hardened Gentoo seems rock-solid and pretty much impervious to buffer overflows.
      */me waits for the Gentoo flames to come...*

      --
      I don't use Emacs; it uses me.
    3. Re:trust by NMerriam · · Score: 1

      I say use whatever works best for what you are doing. if you want REAL security, you shouldnt use either of those OS's

      Although it should be noted that anyone can download source and build the Darwin OS themselves http://developer.apple.com/darwin/ (Mac OS X is built on Darwin, which is built on BSD).

      --
      Recursive: Adj. See Recursive.
    4. Re:trust by Anonymous Coward · · Score: 1, Funny

      The only OS I would trust to be completely secure is the one that runs on abacus.

    5. Re:trust by molnarcs · · Score: 1

      "This pointless blathering about security shoudl convince no one of anything, especially, when zealots are concerned...."

      And yet...

      the only computer that i would fully trust to protect my stuff would be a gentoo linux box custom made for a specific purpose

      not that I have anything against gentoo zea..., ehmm... I mean folks putting in a good word for gentoo, even if it is unrelated to the article :-p

    6. Re:trust by cayenne8 · · Score: 1
      I dunno, years back I tried putting Win 95 on an abacus...damned near broke a finger.

      However, I'm thinking of trying Gentoo on one now that I'm older and more nimble of finger....

      :-)

      --
      Light travels faster than sound. This is why some people appear bright until you hear them speak.........
    7. Re:trust by Hungus · · Score: 1

      Actually its built on NeXT with BSD userland.

      --
      Bad Panda! No Bamboo for you! In matters of importance ACs will not be responded to. Want to say something critical,OK
    8. Re:trust by PygmySurfer · · Score: 1

      Although it should be noted that anyone can download source and build the Darwin OS themselves http://developer.apple.com/darwin/ (Mac OS X is built on Darwin, which is built on BSD).

      Technically, Mac OS X is built on Darwin, which was derived from NeXTStep/OpenStep. Only the userland stuff is really BSD.

    9. Re:trust by Anonymous Coward · · Score: 0

      BSD, like Mac OS X? ;-)

    10. Re:trust by telbij · · Score: 3, Informative

      So you're saying there's no middle ground... either you need security and run Gentoo or you need to do some real work and then take your pick?

      In the real world where a person may need to run various applications and perform unforeseen tasks, security is still a consideration. I myself run OS X because (among other reasons) I don't like having system performance degrade over time, or worry about opening emails. Is having my system hacked the end of the world? No, but I'll take the better odds any day.

    11. Re:trust by ducomputergeek · · Score: 5, Interesting
      Security was everything at one of the places I worked. We had a special lead incased steel room with computer monitors and armed gaurds to get in and out with at least three different methods of Identity conformation. Those units in that room were not networked and media could go in, but not out. When it was time for something to go, the nice distructo matic guys came in, busted the monitors, all the hardware and ran magnates over everything just to make sure. Granted that was a DoD contractor and much of the work in those rooms were even above my security clearance. That's about as secure as you can get, and yes some of the computers ran windows.

      As far as that goes, no operating system is 100% secure. The only way its secure is if its off. If you require a password to log on, its vunerable. If to nothing else, someone else on the inside figuring out that password. 80% of all the breaches we see are inside jobs. Either disgruntaled employee, sys admins don't remove passwords of terminated or former employees, or a hacker goes calls on the phone saying, "I'm joe from department x or branch y, and I forgot my password".

      Even now, we have an internal network of 3 computers linked to a server that manages our accounting data. None of those boxes are connected to the Internet. That only leaves the possiblity of a breach from within or a unit being stolen physically from our office.

      We do a lot of IT consulting and expaning into security, and the one question we always have to ask ourselves and clients, "Okay, nothing is going to be 100% secure, where do you draw the line?" Granted, most of our clients have 20 or fewer employees and aren't doing a lot that needs governmental levels of security. Usually Zone Alarm Pro and Norton is about the best defense these people are going to get for the money. Some larger companies elect on having a dedicated hardware firewall installed or an *BSD box configured as a firewall too.

      Now on the desk of an average employee sets either a PowerMac G4 of various speeds, an iMac, iBook (yeah, I'm the President and I have an iBook), or a powerbook all running OS X.2 with my business partner's Powerbook the only 10.3 at the moment. We don't worry about the worm of the week on our machines.

      At the end of the day, the way in which Windows is built and the intergration of IE, MP, etc. there is only so much you can do, and saying "Switch to Linux" often isn't the answer as well, at least to our small business clients. And I will defend that position with one word: Quickbooks. At least with Macintosh, they can have their Office, QuickBooks, Email, and Internet with a system they can understand, and provides more security than windows out of the box. Perfect, no, practical, yes.

      --
      "The problem with socialism is eventually you run out of other people's money" - Thatcher.
    12. Re:trust by rwven · · Score: 1

      i whole heartedly agree. i have never had a gentoo system cracked that i built. when you build them right they are all but impervious... (of course there's always gonna be en exception some time but you get the picture...)

    13. Re:trust by rwven · · Score: 1

      i dont follow your "point" i'm not a zealot as i said: use whatever is best for what you want. if you find something that works better for you, then use it. in my experiences gentoo has provided the best security that i have seen yet... no it's not perfect but what is? if i'm doing video rendering or something, i would probably NOT want to use gentoo... i think you interpreted my gentoo example as a zealous remark... but whining over whether OSX or XP are better in the security area is kinda pointless. the bottom line is that neither of them are GOOD. they're just decent enough to get by in the user end of the spectrum.

    14. Re:trust by rwven · · Score: 1

      who gets system degredation? if you were getting this with other OS's then it may be a problem with something YOU are doing. my personal box is running XP and i've kept it up for two months using it every day and it's just like i rebooted it. this is that blathering i was talking about.

      if you know anything about gentoo then you'd know that everything you run on it is compiled for YOUR SPECIFIC CPU which means that you get a 5-10% increase in speed on just about everthing you do. (i've even heard of web servers serving 25% more pages per minute and 10% more sql transactions because of it.) now do you still want to talk about "doing some real work?"

    15. Re:trust by rwven · · Score: 1

      well put :-) as i said, whatever does the best job for what you need done. I'm not totally hardcore linux but for some tasks ther ejust isnt anything better. same goes for windows, and mac, as well as just about any other OS out there...

    16. Re:trust by molnarcs · · Score: 1

      Ok, sorry. My roommate uses gentoo btw - portage seems to be fun, but compilation/dependency-checking is fully automated, so you don't have that much control over what goes into your system... Just like in *BSD. Of course, you can look into the source code, or check the makefiles, but that's true of most open-source systems.

      If I wasn't using FreeBSD, I think I would try out gentoo myself :) (I'm going to install a linux, probably slack, cause I don't want to duplicate the time I wait for a port to build). My only gripe with gentoo is its nightmarish sysv init system. If they used BSD (and Slackware's) much much simpler init, gentoo would be the linux distro of my dreams ... but still, because of portage, it seems to be the distro that is the most fun to use. But it is certainly not the most secure, just because it compiles progs locally, and you can custom build it!!!

    17. Re:trust by rwven · · Score: 1

      oh totally. i LOVE building gentoo boxes. it's downright fun to do. I think there are a lot of portage ports to other *nix distro's and OS's so you never know, there might be a port to freebsd. check into it. heck, if there isnt and you're a coder, make one. lots of people would love you...

    18. Re:trust by telbij · · Score: 1

      Yes, something I do DOES cause system degradation (on Win 2000, dunno about XP), it's called installing software. Sometimes I need an FTP an SSH client. How do I know what is safe to install on a PC? The answer is, you just have to know what has spyware in it, or run some anti-spyware software however that works. Sure on a Mac, an installer could ask for the admin password and install spyware, but it hasn't happened to me yet. Plus I need less software to begin with (ssh and ftp built in), and I haven't run into any problems with the few things I have installed.

      And what does a 25% increase in speed have to do with doing work? I am not a system administrator, so my work does not involve setting up boxes for efficiency. I run a 400mhz G4 and have no need for higher performance. I'm a web designer and developer. I need Apache, PHP, Perl, MySQL, as well as Illustrator, Photoshop, and InDesign. I don't work in a tech department either, so I need to communicate with the other employees running MS Office and Visio. I could be asked to drop any kind of new media on the site at any time, so I need the ability to install software and figure stuff out quick. So sadly 'knowing about gentoo' doesn't really do much for me. I keep a PC around to test in Internet Explorer and it works great because I don't have to install any software on it.

    19. Re:trust by rwven · · Score: 1

      if you're worried about adware or spyware then get a clue and get ad-aware or spybot to get rid of it. who cares if you know if it has any with it. all you have to do is run these apps after installing a program and it kills them. as i said it's YOUR fault if you're getting degredation.

      And again you prove my point that you should, at the bottom line, use whatever works for you best in what you need to do. however just because windows doesnt meet your needs for your current function doesnt mean you have to trash it and make up rediculous claims about it. THAT is the blathering zealous remarks i was referring to...

    20. Re:trust by BeProf · · Score: 1
      As far as that goes, no operating system is 100% secure.
      Obviously you've never used VMS.
      --
      You are attempting to read sigs. Cancel or Allow?
    21. Re:trust by drsmithy · · Score: 1
      Sure on a Mac, an installer could ask for the admin password and install spyware, but it hasn't happened to me yet.

      An installer hardly needs an admin password to install spyware.

    22. Re:trust by Anonymous Coward · · Score: 0

      How do you fully trust a gentoo linux box which get's it's build data and source from 3rd parties.. Be realistic. As someone else said, you trust no one. Audit.

    23. Re:trust by mattdm · · Score: 4, Funny

      When it was time for something to go, the nice distructo matic guys came in, busted the monitors, all the hardware and ran magnates over everything just to make sure.

      What, like, Andrew Carnegie and John D. Rockefeller had to jog on the broken computers? How does that help? Man, I just don't understand security these days.

    24. Re:trust by E-Rock · · Score: 1

      Why should a non-admin run their window box as an admin? That would prevent e-mail born *anything* from installing. If you switch over to admin mode to install on your Mac, it can install spyware right along with it, same for unix. No differences there.
      Don't like people smearing your OS of choice, stop making stupid ass comments about others.

    25. Re:trust by jceaser · · Score: 1

      It does if it is going in the /System folder and thus be able to spy on all users. Granted, a program could install in ~/Library and spy on that user with no password, but the system has stoped the problem at one user and not all users.

    26. Re:trust by telbij · · Score: 1

      Look that's great if you're informed. My point is just that I've had so many headaches trying to get my work done on Windows that I switched to OS X, and guess what... no problems. Yes it's anecdotal, but it's not blather.

    27. Re:trust by drsmithy · · Score: 1
      It does if it is going in the /System folder and thus be able to spy on all users. Granted, a program could install in ~/Library and spy on that user with no password, but the system has stoped the problem at one user and not all users.

      Most systems are single user. Even for those that aren't, chances are high any software installation will be done for "All Users" by defult. Anyone who thinks a spyware writer isn't going to try and get spyware onto their system because they might not be able to spy on a tiny number of users is being a bit silly.

      Yes, the system gives a modicum of extra protection, however, it's not significant and certainly not absolute.

    28. Re:trust by Anonymous Coward · · Score: 0

      yah i was going to point that one out as well but I was going to say OS/400. Or pick any mainframe OS like z/OS. But I guess we're talking about desktop OSes...

    29. Re:trust by Matty_ · · Score: 1

      I'm not sure what "real" security means. I think most servers are as secure as the person managing the system.

      As someone who manages Windows and FreeBSD servers at work, and uses Mac OS X at home, I thing arguing over the security of an operating system is utterly pointless and moot, in my humble opinion. In the end, you still have to lock down the server, keep up with patches, and properly firewall the network.

    30. Re:trust by ShinySteelRobot · · Score: 2, Interesting
      the only computer that i would fully trust to protect my stuff would be a gentoo linux box custom made for a specific purpose.

      Why would you trust Gentoo more than OpenBSD? After all, OpenBSD is written and audited to be the most secure OS around.

    31. Re:trust by Anonymous Coward · · Score: 0

      Normally I don't go in for the, "d00d that was so FUNNY!!!!!11!!!" posts, but that's really one of the wittiest things I've read in a long time.

      Thanks.

    32. Re:trust by Anonymous Coward · · Score: 0

      Sounds like you are a "gentoo linux zealot." why would you trust a "Self patching" system. If you work for a security company, you should know better not to trust an "Self patching" system in the first place. Just because you work for security company, dosent mean you know about security... you could be a secretary or a janitor for heavens sake.

    33. Re:trust by Anonymous Coward · · Score: 0

      The fact you even need 'spyware removers' is a joke.

    34. Re:trust by rwven · · Score: 1

      maybe, but so is the fact that you need anti-viral software

    35. Re:trust by rwven · · Score: 1

      maybe you should try reading the post next time moron....i said use whatever is best for what you are doing....

    36. Re:trust by molnarcs · · Score: 1

      portage port to freebsd? freebsd has a ports system:

      portinstall mplayer

      ... and watch it download, compile and install mplayer with all the dependencies. I read about portage on genntoo's website when looking for help while my friend's puter was offline - its almost the same as FreeBSD's ports system. We have prebuilt packages as well, which work like debian's apt-get: "pkg_add -r kdebase" and watch it fly! :)) Also the portinstall/upgrade system and package management work hand in hand. What u installed from ports by either typing in "portinstall whatever" or cd-ing into the directory (/usr/ports/multimedia/mplayer for instance) and typing "make install clean" can be removed via the package management as well (pkg_deinstall -d mplayer will remove it). It is easier to configure it too (no freaking XFree86 dependency for 'emerge mc') - yet it is as powerful. :)

    37. Re:trust by Anonymous Coward · · Score: 0

      The vast majority of OS X programs don't even have installers. You just drag a program file from the disk image into the applications folder. For something like that to install spyware that's as evil as the average windows spyware would be sort of tricky...

    38. Re:trust by Anonymous Coward · · Score: 0

      As far as that goes, no operating system is 100% secure.

      Man, I'm getting tired of all the nonsense that people try to build on this observation. The next assertion is always something like, "therefore, technique X is good enough," usually supported by some dubious anecdote.

      This kind of preamble simply does not absolve the writer of the need to reason meaningfully when drawing comparisons among different security paradigms. It's like saying, "We're all going to die eventually, therefore it's ethical for me to kill you for reasons of personal convenience."

      Try saying instead, "I believe that security technique X is effective under condition Y, based on the following reasoning."

      It's not so hard once you try it once or twice.

    39. Re:trust by Anonymous Coward · · Score: 0

      Errr. I seem to remember VMS systems getting hacked back in the day, whether by lame password or not. We didn't know what the hell to do once we got on tho. one of the LoD or Mod guys was a VMS specialist iirc. a quick google search of
      hacking vms returns 19000 or so results.

      Were you being sarcastic?

    40. Re:trust by BeProf · · Score: 1

      I was being sarcastic.

      I remember my old sysadmin telling me that VMS is hack-proof (which is true if you have a good sysadmin). He told me this right after he gave me, a lowly operator, SYSPRIV.

      Foolproof = better fools.

      --
      You are attempting to read sigs. Cancel or Allow?
    41. Re:trust by ealar+dlanvuli · · Score: 1

      Why would you trust gentoo linux? That is silly. That means you trust the entire gentoo development team which is just dumb.

      I would only trust an operating system written by myself on hardware bult by myself from parts that are easily verified to be accurate (you can probably use simple pre-fabed chips, but things like pre-built p4's would be out of the question).

      Be careful how you define trust, and make sure your expectations of trust are realistic.

      --
      I live in a giant bucket.
    42. Re:trust by rwven · · Score: 1

      it's all relative. i trust it more than anything else out there that i personally have tried to achieve the same goal with. you cant fully trust ANY software when it comes down to it...

  5. I'll take Zealots for 500, Alex by TimTheFoolMan · · Score: 4, Insightful

    'In other words, you're either with him [Lance Ulanoff] or with the "zealots."'

    If I have to choose sides, I'll go with the Zealots on this one. Apple's security and responses to breaches (so far) have been light years ahead of what I've dealt with from MS.

    Tim

  6. Cockiness by fiannaFailMan · · Score: 5, Funny
    From the original article:
    How cocky are you feeling now, Mac elite?
    As cocky as ever, thank you very much.
    --
    Drill baby drill - on Mars
  7. *sigh* by Oculus+Habent · · Score: 5, Insightful

    The PC Magazine story was just about that - a story.

    It wasn't a report. It wasn't an account. It wasn't an investigation. It wasn't supported by facts. It wasn't supported by logic. It was an opinion piece that, from my view, wasn't well thought or well written.

    It's unfortunate that people need to write rebuttals to this sort of journalism, but some naive readers out there will simply take it at face value because it's in print, so it must be true.

    --
    That what was all this school was for... to teach us how to solve our own problems. -- janeowit
    1. Re:*sigh* by ack154 · · Score: 5, Insightful

      But what if many people read that and don't see it as just a "story"? What if people take it for what he wrote? (Essentially saying Mac is "as bad as" Windows based on this one vulnerability he mentioned).

      While this new article does take maybe too much aim at the original author, it should at least help clarify what is really going on.

      I'm far from a security expert or anything, but I would be far more apt to trust Mac OS security out of the box than Windows security...

    2. Re:*sigh* by Ringel · · Score: 5, Insightful

      It wasn't a report. It wasn't an account. It wasn't an investigation. It wasn't supported by facts. It wasn't supported by logic. It was an opinion piece that, from my view, wasn't well thought or well written.

      Unfortunately, it is exactly that type of disingenuousness that is the hallmark of yellow journalism. You don't get to ex post facto decide whether something is a story or journalism. I assure you that there is no field for "story" or "journalism" in any standard bibliographic form. This is how people like Ann Coulter get away with slander, and then take a "ha ha only kidding just my opinion" stance to defend themselves.

      As soon as a story is referenced, it becomes a reference, regardless of what the original motivations were.

    3. Re:*sigh* by Oculus+Habent · · Score: 4, Insightful

      The original article was poor. It shouldn't have made it to publication. There should have been an alarm in the mind of some editor, reviewer... someone.

      The basis for a rebuttal is valid and appropriate. A correction by the author would be better, but we tend towards sensational announcements and very, very quiet retractions.

      --
      That what was all this school was for... to teach us how to solve our own problems. -- janeowit
    4. Re:*sigh* by hellfire · · Score: 5, Insightful

      I disagree with you for several reasons:

      1) If Lance can post something regarding his opinion of an operating system, then Richard can post his opinion of Lance's article.

      2) Everyone's entitled to an opinion, but not all opinions are equally valid. This is a fundamental point of epistomology. Lance is spreading FUD. What his motivation is, is unclear. But that doesn't give Lance the right to be spreading false accusations. Someone has to stand up and say so. If I were as good a writer as Richard I might have done it.

      3) Lance KNOWS what he's doing, and either he know he's wrong or he's so blinded by his opinion that he can't reason properly. However, some people are going to think he's right. That's not fair to anyone who enjoys using Apple products or is one of these "mac zealots" who want to expand the user base.

      4) This isn't in the same degree as some gross mischaracterizations that the media is known for (such as overblowing safety warnings or terrorism alerts, or incorrectly running news stories on urban legends and hoaxes which aren't true; yes that has happened before and continues to do so!), but every article, factual or opinionated, that contains false facts must be refuted. The journalism industry is taken for granted, at least in America, and when one of them screws up in order to get more money or get a promotion or because someone ordered them to, or some other sleazy means, then better journalists, or the public in general, should stand up and say the media is dead wrong.

      --

      "All great wisdom is contained in .signature files"

    5. Re:*sigh* by overbom · · Score: 1

      For the epistemologically curious, Lance's position happens to be valid but not sound, an important distinction.

    6. Re:*sigh* by Rodaddy · · Score: 1

      It has nothing to do with the article being true. The rebuttal was written (well I might add) because most people believe what they read. Its human nature, it's easy, and well... comparatively thinking is hard. So when someone comes out with an article that is semi factual, most tend to believe it as the truth. If people that do think on there own don't do something to set it straight, or at bare min explain away the mistruths. These feeble rumors become fact. "Fear causes hesitation.... ...and hesitation causes your worst fears to come true"

    7. Re:*sigh* by Anonymous Coward · · Score: 0

      Great points.

    8. Re:*sigh* by mcdesign · · Score: 1

      Yes it was only an opinion piece but unfortunately opinion pieces have far more influence than they deserve. Opinion columns are often the most read articles in a magazine and they can heavily influence the opinion of others. The average reader of the article would conclude that OS X = bad security.

      Any formal discussion of this particular OS X security lapse involves talk about subnets, networking protocols, etc etc. Now I know what they are but to be honest I find the ins and outs of networking to be rather boring. I suspect many PC magazines readers do as well. So rather than an article that many people won't read, especially as it applies to only a few percent of the audience using OS X anyway, we get an opinion piece.

      Now this OK, the magazine does need to sell. However in this case the opinion piece was a particularly bad example of one. A few minutes web searching shows that the article was full of misconceptions and half truths. It sort of implied that this was a major breach that applied to all OS X users. In reality it only applies to a few people with hostile servers on their own subnet. In which case they have far bigger things to be worrying about! It seems then that the author was deliberately attempting to misinform.

      While every one is entitled to an opinion such poor examples of journalism really do deserve a rebuttal.

    9. Re:*sigh* by E-Rock · · Score: 1

      But the asshole tone of the reply wasn't, and brings to mind the foolish mac zealot we've all heard about.

    10. Re:*sigh* by Anonymous Coward · · Score: 1, Insightful

      I haven't read anything Ann Coulter has written. Have you? Has the stupid slashdotter who gave you five points read anything of hers? I have seen her on TV a couple of times, but I've never heard her laughing anything off. Yeah, y'all are real concerned about people who slander all right. Let me give you a piece of advice. You can't do anything about Ann Coulter, but you can do something about yourself.

    11. Re:*sigh* by Anonymous Coward · · Score: 0

      The 'asshole tone' was nothing compared to that of the original article. Yet he doesn't get dismissed as a mindless PC zealot... oh wait, actually he did. Nevermind.

    12. Re:*sigh* by Anonymous Coward · · Score: 0

      Thanks Yoda

    13. Re:*sigh* by vantango · · Score: 1

      So why was it on /. days before the resulting rebuttal article? Oh, nevermind...

    14. Re:*sigh* by E-Rock · · Score: 1

      Yea he did, and we all quickly forgot about the foolish comments he made, until now.

    15. Re:*sigh* by Anonymous Coward · · Score: 0

      Or you could blow it out your ass.

    16. Re:*sigh* by JClark-IdleME · · Score: 1
      Actually, it's Michael Moore who tends to laugh things off, claiming that it's comedy so there's no standard of accuracy to follow.

      Ann Coulter is, however, a liar. And a mean one at that. She's got a definate political agenda, and she won't let the truth get in the way of that. Her tactic, when confronted with her lies, is generally to claim she was misunderstood, or to claim it's all a tactic by the "liberal media" to discredit her.

      Spinsanity.org has several many good articles about these things, in case you want to make sure we're not slandering her or anything.

  8. Interesting Article by voodoo_bluesman · · Score: 2, Informative

    That is a great article, but for some reason it feels like he didn't really do that much research. For instance, his reference to DLL Hell is outdated - Windows XP doesn't suffer from that issue.

    Saying that, I have to make the statement that I am an OS X user, and I love it. The simple fact that is asks for my username and password when I try to install applications is a wonder in itself.

    1. Re:Interesting Article by AKAImBatman · · Score: 2, Insightful

      For instance, his reference to DLL Hell is outdated - Windows XP doesn't suffer from that issue.

      Excuse me? Why not? If XP uses (or even supports) the same DLL system as previous versions of windows, I don't see any way you could avoid DLL hell other than careful control of where and how software is installed.

    2. Re:Interesting Article by flex941 · · Score: 1

      > Windows XP doesn't suffer from that issue.

      And how's that? Please enlighten me.

    3. Re:Interesting Article by Anonymous Coward · · Score: 0

      He also ignored the fact that you can deactivate.. aaaarrrghhhh....

    4. Re:Interesting Article by voodoo_bluesman · · Score: 2, Informative

      Take a look here for a brief overview. I'm not saying that this is perfect, but by being able to run multiple versions in memeory does help alleviate the pontential for DLL conflicts.

    5. Re:Interesting Article by PPGMD · · Score: 1
      I agree descent article, but like the authour of the article that he is rebutting, I believe that he also did very little research.

      DLL Hell is pretty much gone, DRM issues with WM9, what about the DRM in the AAC's? You can run a different media player.

      Overall it's a couple of Zealots fighting it out, I say we tape razorblades to their feet and start taking bets.

    6. Re:Interesting Article by Firehawke · · Score: 1

      I believe the information you seek can be found right here

    7. Re:Interesting Article by voodoo_bluesman · · Score: 1

      Here's a brief overview. It's not too technical, but by running multiple DLL's in memory, the system escapes from (or at least tries) DLL Hell.

      It's not full proof, but since I've upgraded several of my clients to XP (please don't flame me for that), a lot of their previous upgrade issues have gone away.

    8. Re:Interesting Article by TimTheFoolMan · · Score: 1

      Fortunately, the TechNet article doesn't absolutely drip with pro-MS bias...

      Tim

    9. Re:Interesting Article by Anonymous Coward · · Score: 1, Funny

      Saying that, I have to make the statement that I am an OS X user, and I love it. The simple fact that is asks for my username and password when I try to install applications is a wonder in itself.

      So in the words, you download programs from the internet, execute them, and then type in your password when prompted... Can you say the word 'Trojan' ?

    10. Re:Interesting Article by voodoo_bluesman · · Score: 1

      Weird - I just posted the same exact link. I hope our friends here on slashdot don't think we're microsoft PR! ;-)

    11. Re:Interesting Article by voodoo_bluesman · · Score: 1

      I see your point - I was just refering to the fact that the system makes me aware that changes are taking place, and that I have to authorize it to do so.

      I can see potential abuse for a trojan, but I meant to compliment Apple's seamingly proactive take on security.

    12. Re:Interesting Article by EvilFrog · · Score: 1

      The big difference between DRM in WM9 and iTunes is that iTunes only uses DRM on songs you buy in the iTunes store- if you rip it yourself, there is no DRM.

    13. Re:Interesting Article by AKAImBatman · · Score: 2, Interesting

      Umm... no. The problem of DLL hell is because programs (including Windows) all throw their DLLs into the winnt\system folder. New versions of DLLs overwrite old versions, files get left behind during uninstalls, etc. All this contributes to the long-standing problem of "DLL hell". Simply allowing multiple/separate copies in memory is something that all OSes (including Windows) have been able to do for many, many, many years.

      Sorry bub, but it seems Microsoft pulled a fast one on you.

    14. Re:Interesting Article by PPGMD · · Score: 1

      Same thing for me. If I rip my songs myself there is no DRM either, at least with CDex, never tried it with WM9 because I have an iPod and need MP3's.

    15. Re:Interesting Article by Firehawke · · Score: 1

      Yeah, ironic that we got the same link at nearly the same time. I found it going down Google; it was only the fourth or so entry on the list. I'd remembered reading a LOT about the "Anti-DLL Hell" changes right around XP's launch, as it was supposed to be THE big thing.

      All in all, it's a big step forward, but we can hope for further steps forward. Security and stability are a never-ending series of steps forward..

      I remember Windows 3.1 clearly when I consider the stability of current OSes. Microsoft has improved, but we'll see how they are in another 10 years.

    16. Re:Interesting Article by EvilFrog · · Score: 1

      ...

      Considering we were comparing the existance of DRM in WM9 and iTunes, whether CDex has DRM or not is quite frankly irrelevant. My point is, while both have DRM, their implementation is very different. iTunes doesn't apply DRM to any CDs you rip yourself, but rather only uses it on songs you buy from the iTunes Music Store.

    17. Re:Interesting Article by PPGMD · · Score: 1
      The thing to remember is just because the feature is there doesn't nessarily mean that the user will use it.

      A Windows user can use iTunes (which now is forced on you with Quicktime), CDex, and a number of other programs. It's like the old Netscape, IE debate.

    18. Re:Interesting Article by Anonymous Coward · · Score: 0

      dude I suffered from that in xp...try gaim windows port...suddenly one day dllhell broke loose..ughh..

    19. Re:Interesting Article by MoneyT · · Score: 1

      But a good portion of users will indeed use WMP, because it's the default. And the default automaticaly applies DRM to your own work.

      --
      T Money
      World Domination with a plastic spoon since 1984
    20. Re:Interesting Article by PPGMD · · Score: 1

      Well at least it's better than royalties on our MP3 players and CD-R's, and those of us that want to use other programs can.

    21. Re:Interesting Article by Foolhardy · · Score: 1

      And um, no Windows File Protection fixes it. When a crappy installation program overwrites a system file, WFP sliently replaces it with the correct (newest) version. That's what that big 'dllcache' folder is for.

    22. Re:Interesting Article by Anonymous Coward · · Score: 0

      So we can just apply AKAImBatman's reply to this one, too. That's handy.

    23. Re:Interesting Article by umofomia · · Score: 2, Informative
      Umm... no. The problem of DLL hell is because programs (including Windows) all throw their DLLs into the winnt\system folder. New versions of DLLs overwrite old versions, files get left behind during uninstalls, etc. All this contributes to the long-standing problem of "DLL hell". Simply allowing multiple/separate copies in memory is something that all OSes (including Windows) have been able to do for many, many, many years.
      Umm... no. If you had done your own research, you would have found out that Windows XP does not allow random programs to overwrite DLL files in the system folder using System File Protection (SFP). Instead it will write the file to another location and keep track of the separate DLL through was is known as a manifest. When the application requests for that specific version of the DLL, the manifest will provide it for the application.

      For more info, see:

    24. Re:Interesting Article by Durandal64 · · Score: 1
      So in the words, you download programs from the internet, execute them, and then type in your password when prompted... Can you say the word 'Trojan' ?
      As opposed to downloading a program from the internet, executing it, never being prompted for a password ... can you say, "Much bigger chance of successful trojan infiltration"? Look, users aren't perfect, but if a program asks for administrator privileges, users have the opportunity to deny it. Windows installers and programs never give that opportunity. If you're logged in as an administrator, you've never, ever prompted for a password by default. In Mac OS X, you're always prompted if a program requests administrator privileges by default (you can tell the system to automatically authenticate, but this is off by default, and for good reason).
    25. Re:Interesting Article by bovinewasteproduct · · Score: 4, Informative

      Windows XP doesn't suffer from that issue

      Considering that only about 8% of the windows users are running XP (95, 98 and 2000 are the majority), then his comments still stand. The recent spate of articles on MS dropping support for Win98 has posted the ratios quite clearly.

      BWP

    26. Re:Interesting Article by spitzak · · Score: 1

      That only works for *new* software rewritten to take advantage of it.

      Also a malicious installer can still clobber an existing DLL in order to install spyware (though I suspect an Apple installer would be able to do this too if the user types in their password).

      Actually Windows has had a way to avoid DLL hell for a long time. Programs look in the same directory as the executable to find dll's first. So the programs should just ship with the dll's they want in the same directory, and install as a new directory. Power users who want to use newer dll's can try deleting/renaming the ones with the app and seeing if they still work. This scheme works so well that large Linux apps are supporting it even though Linux does not have this feature (it is typically done by a small wrapper program that sets LD_LIBRARY_PATH).

      Unfortunately for whatever reason Windows apps don't work this way, in many ways combining the worst features of Unix layout (where files must be stored in directories by function, ie librarys here, programs there, config files elsewhere...) with Window's own limitations (screwy pre-multiprocessing shared libraries with shared r/w segments, and the "registry" which is like a really bad file system). The cynic would say that Microsoft did this for evil intentions so they could break any software they wanted by changing a DLL, but in reality it is probably just stupidity.

    27. Re:Interesting Article by e2d2 · · Score: 1

      And to further elaborate from what I know about programming on the win32 environment, this is a temporary solution for DLLs that run in a COM environment.

      Move to .Net and you cannot only drag and drop your DLLs without registering them locally (provided you have the proper permissions to not only place the dll there but execute it also) but you also can have multiple versions of the same dll registered in the Global Assembly Cache (GAC) for multiple apps on the same machine to reference at runtime (Referencing a dll from the GAC is optional). This GAC will serve as a registry for DLLs and other .Net assemblies.

      So yes, DLL hell is over. Every application will have it's own copy of the dll to use or reference a common DLL by checking the GAC for the correct version.

      The implications of multiple dll/lib versions on the same machine are not restricted to just Windows but the same type of dependency problems might ensue. It comes down to good administration of the machine by competent folks, same as always.

    28. Re:Interesting Article by leifm · · Score: 1

      That's the beauty of the Mac/Linux/Win arguments. Most of the people spouting off reasons not to use whatever one they hate haven't used it for years, so you end up with these retarded debates about non-issues. When it comes right down to it all three are pretty good, and all three have strengths and weaknesses, and everyone would be better off pestering the developers of their OS choice to improve on the weak points rather than debate the merits of their OS to others who probably aren't going to switch anyway.

      I've used all three, and currently I'm running XP Home. Why? Because two iBook hardware failures have me tense about Apple hardware (not saying it sucks, saying my experience has been bad so I am staying away), for my purposes Linux isn't a great desktop choice yet, and Windows works better for me. So at present I am a Windows user. Yet I like many aspects of Linux and want to see it succeed, and I think OSX is great too. See we can all get along!

      --

      "Windows Me offers tremendous reliability and stability improvements..." -- Paul Thurott
    29. Re:Interesting Article by Daytona955i · · Score: 1

      Can you say "Oh Cr@*, I read my e-mail and now I have a virus" oh yeah... "and now everyone in my address book is going to get it to."

      or "Oh Cr@*, I opened a word document and now I have a virus"

      or "Oh no, I was browsing the web with IE and now I have a virus"

      No system is 100% safe... even if you disconnect it from the internet and put it in a safe, someone will still be able to get it... it just a matter of how easy it is to get to.

    30. Re:Interesting Article by Blakey+Rat · · Score: 1

      This is off-topic, but why doesn't anyone ever mention ME?

      Sure, ME sucks and we've love if it didn't exist, but I know a good portion of the Windows-using public uses ME... and yet it never shows up on any statistics. (Google, for instance, doesn't list ME.) It is being grouped with 98 for these studies?

    31. Re:Interesting Article by spectecjr · · Score: 2, Insightful

      Considering that only about 8% of the windows users are running XP (95, 98 and 2000 are the majority), then his comments still stand. The recent spate of articles on MS dropping support for Win98 has posted the ratios quite clearly.


      That would be 38% according to Google, by the way. That study you're misquoting only surveyed a small sample of a specific market segment.

      --
      Coming soon - pyrogyra
    32. Re:Interesting Article by bovinewasteproduct · · Score: 1

      Well w3schools show XP at 19% so who knows?

      It is less than 51% by any measure, so the majority of MS Windows users still deal with DLL Hell.

      My original claim still stands.

      BWP
      BTW, how did I misquote the study?

    33. Re:Interesting Article by EddWo · · Score: 1

      There is a reason for keeping the dlls in one place, and its the reason for dlls in the first place. When two processes request the same dll the OS only loads it into physical memory once and maps it in to each processes address space.
      Virtually every program you run will be using user32, gdi etc, and the memory sharing reduces the memory requirements considerably. There is no reason for a dll that only one process uses being stored in the system folder, but programs tend to install files that might be shared by several processes and a lot of installers are not very careful how they do it.

      Microsofts solution to dll hell with System File Protection does add another layer of bloat, but it also solves the problems of crappy old program installers overwriting critical system files. Microsofts curse is the level of backwards compatibility it must maintain so that 5+ year old VB line of business apps go on working on each new version. The number of hacks that must be introduced in just to keep poorly written programs running are probably the cause of many of the problems. XP home could have better security if it didn't make every user an administrator, but how many people would complain if all their old apps and games stopped working?

      With closed source software binary and environment compatibility is paramount.

      The registry was an OK idea that turned out badly. Its a good idea to have a centralised way of storing/retrieving application settings, com componant registrations, file type associations etc.
      Its a good idea to have this be a cached in memory hierachical structure for fast access. Its not a good idea to have its backing store be a single binary file that continually expands and cannot easily be repaired if mistakes occur. Its not a good idea to let any program alter any other programs settings, or take over file types without permissions.

      Things like gConf are the registry done right.
      Theres no reason not to store the actual settings in per application xml files that are parsed into a memory based structure for fast access and rewitten to the disk in human readable form on modification.

      --
      "Taligent is still pure vapor. Maybe they'll be the last who jumps up on Openstep... "
    34. Re:Interesting Article by EddWo · · Score: 1

      But you shouldn't compare the security of OSX with Windows98/ME. Compare OSX with NT based systems and oS9 with 9x. One generation was built with security in mind, the other wasn't. The issues with 2000/XP are out of the box configuration issues generally and not OS design. NT can be secure, it just takes a bit of work because the systems pre Server 2003 were shipped configured for compatability rather than security.

      --
      "Taligent is still pure vapor. Maybe they'll be the last who jumps up on Openstep... "
    35. Re:Interesting Article by InadequateCamel · · Score: 1

      He states in the article that "DLL Hell" was in older versions of Windows. Though XP does not have the same DLL troubles it does have other irritating issues, such as leaving entries in the registry (such as when an uninstall crashes) and leaving files required for installation repair/uninstallation in directories such as Temp rather than a safe location.

    36. Re:Interesting Article by davegust · · Score: 1

      automaticaly applies DRM to your own work.

      Seems bold of you to claim a music CD as your "own work". When was the last time you ripped a CD that wasn't copyrighted?

      If you are in fact a music producer, surely you have better tools that WMP with which to copy your tracks. I know you are not, otherwise you would not be defending the illegal distribution of copyrighted material.

    37. Re:Interesting Article by MoneyT · · Score: 1

      Well, for starters, as a musician, I tend to record my performances. Likewise, part of my public speaking courses involves recordings of ourselves. Look, I'm not taking a position one way or the other here, what I'm saying is that it's unfair and demeaning to treat your customers as criminals.

      --
      T Money
      World Domination with a plastic spoon since 1984
    38. Re:Interesting Article by davegust · · Score: 1

      Let's be honest. Nearly all copied music files are illegally copied, and nearly all P2P music swappers are criminals.

      This isn't the Betamax case. There are very few justifiable reasons for ripping to non DRM files. If Microsoft were the government, or the only vendor of multi-media software, I would be the first to join you in denouncing the loss of liberty.

      Microsoft is doing what the corporate world is demanding, and that is protecting property rights. They're trying to walk the line between satisfying end-users and content providers. You may not like their choice, but then you still have options.

      You should like Longhorn better because there be a sandbox - inside will be Sony, Universal, etc - and outside will be your content, over which you will have complete control. Good fences make good neighbors.

    39. Re:Interesting Article by Firehawke · · Score: 1

      Yeah, and the response to that in return as well.

      It's important in the distinction of Windows not allowing DLLs to be dumped all over System/System32 anymore-- that was the entire lynchpin of the problem in the first place with applications clobbering each other.

  9. Curious.. by Metallic+Matty · · Score: 4, Informative

    You could have found a fairly accurate rebuttle right here at . as well.

    Minus the trolls and such.

    1. Re:Curious.. by Anonymous Coward · · Score: 0

      What about minus the zealots?

    2. Re:Curious.. by danigiri · · Score: 3, Interesting

      Sorry to cross-post (posted on previous discussion) but I'm lazy (and point still stands). Here's another rebuttal from me that uses no personal attacks or any of that crap:

      Dear Mr. Ulanoff,

      I am writing to you just to send you a couple of informative references on general computer security. I promise to stick to the basics, and I am sure you will dig deeper if interested.

      One of the basics of remote exploits is the ability to -once a remote vulnerability is discovered-, send malicious code snippets that get executed with privileges on the target computer. For instance, they might be sent exploiting a buffer overflow bug or a flawed service left running on an open port.

      This is well known in the MS Windows world and even Linux, as they commonly share the same underlying hardware architecture (namely x86). There is plenty of information on how to build such malicious code snippets (basically anyone knowledgeable in x86 assembler can do it) as well as pre-built apps and scripts to send them. This is well known. It is also well known that a vulnerability must be present for the code to be able to be executed at all.

      It is a common myth that -by following this logic-, other platforms that are less used, like for example MacOSX (subject of a security article of your own), are more secure because technical knowledge about them is less common (eg. PPC assembler language) and are not so commonly used. One might think the malicious code needs to be built by real gurus, few in number, that have no interest in doing that.

      *However*, doing a trivial search on Google (also published on /. and so seen by thousands) this paper shows up:

      http://www.securiteam.com/securityreviews/PPC_OS X_ Shellcode_Assembly.pdf

      Is a no-nonsense compilation of MacOSX PPC malicious payloads and the rationale behind them. After copy-pasting from it, anyone can do remote attacks on MacOSX, *provided* a vulnerability is actually found. No vulnerability, no attack. The paper requires a low level of technical knowledge and actually has little merit (apart from being somewhat clear and concise).

      So, using information freely available, easily found, in common knowledge (published on /., not some backwater usenet), anyone could attack MacOSX boxes, *if* a vulnerability is discovered in it or in its running services.

      So it *cannot* be possibly said that MacOSX achieves its high level of security by obscurity. It accomplishes it by *design*.

      It is really sad that the old argument of 'security by obscurity' is being raised over and over. Read that paper.

      Mr. Ulanoff, I promised you two links and I have provided only one. The other is not actually a link but a reference. Just walk to your nearest technical bookstore or Computer Science library, look for the PPC assembly and architecture books that have been publicily available for years. My cheapo college library has them, yours surely has.

      I am looking forward to further informed security articles by you. Please do not hesitate to mail me should you need further references on this or any other technical question.

      Best regards,

      xxxxxxx

    3. Re:Curious.. by drsmithy · · Score: 1
      It is a common myth that -by following this logic-, other platforms that are less used, like for example MacOSX (subject of a security article of your own), are more secure because technical knowledge about them is less common (eg. PPC assembler language) and are not so commonly used. One might think the malicious code needs to be built by real gurus, few in number, that have no interest in doing that.

      This is not the "myth" (and it's not a "myth"). The reasoning you are trying to dismiss is not how you have explained it - it says platforms that are less common are attacked less and even when successfully exploited, have lower levels of noticability and/or impact. Silly people *infer* from this that, therefore, the platforms that are attacked and exploited with lower levels of frequency and impact are more secure. The argument is not that less used platforms are more secure because fewer people have the necessary knowledge, it's that less used platforms aen't exploited as much because fewer people are trying, any exploits have a smaller impact and problems are a lot easier to contain and correct.

      You don't get as many exploits on something like OS X because a) fewer attacks target it and b) even if it is successfully exploited, it affects a much smaller proportion of users - thus dramatically limiting both the ability to spread and the negative impact.

      Simple statistics should tell you that given two equivalent exploits for OS X and Windows, the exploit for Windows will affect around ten times as many machines, cause ten times the damage and be ten times more noticable (personally, I'd argue principles like critical mass would make the relative impacts disproportionate to market share, but that's another discussion). What you *can't* reasonably deduce from that is whether or not OS X is ten times more secure - yet that's what so many people try to assert. They're basically taking the answer (Windows gets more attacks) and trying to deduce the question from it.

      Is a no-nonsense compilation of MacOSX PPC malicious payloads and the rationale behind them. After copy-pasting from it, anyone can do remote attacks on MacOSX, *provided* a vulnerability is actually found. No vulnerability, no attack. The paper requires a low level of technical knowledge and actually has little merit (apart from being somewhat clear and concise).

      As clear and concise as that paper may be, it still doesn't approach on the ease and simplicity of a script kiddies "Virus Creation Wizard".

      So, using information freely available, easily found, in common knowledge (published on /., not some backwater usenet), anyone could attack MacOSX boxes, *if* a vulnerability is discovered in it or in its running services.

      The non-trivial assumptions you are making here are a) *if* a vulnerability is found, there will be proportionally just as many people trying to exploit it and that any successful exploits will be just as "bad" and b) it's the same basepoint people exploiting Windows start from.

    4. Re:Curious.. by Minna+Kirai · · Score: 1

      Simple statistics should tell you that given two equivalent exploits for OS X and Windows, the exploit for Windows will affect around ten times as many machines, cause ten times the damage and be ten times more noticable

      Actually it'd be greater than 10x. You shouldn't expect the relationship between popularity of a platform and the vulnerabilities researched for it to be linear. (By "researched" I mean attempted to discover. The number of discovered vulnerabilities will equal the number researched multiplied by some coefficient of the system's inherent security)

      A better assumption would be a variation of the network effect: the number of vulnerabilities researched goes up with the square of the platform's popularity.

      The number of hackers with access to the platform is linear with popularity. The incentive for an individual hacker to work on it is also linear with popularity. So the product of those two values will equal the amount of work put in to find exploitable flaws.

      Following this reasoning, nearly all of Microsoft's apparent vulnerability could be accounted for by popularity.

  10. Windows are more secure. by Anonymous Coward · · Score: 1, Funny

    My windows all have locks on them. Do your apples?

    1. Re:Windows are more secure. by Anonymous Coward · · Score: 0

      My windows all have locks on them. Do your apples?

      I threw an apple through each window. So much for your locks.

    2. Re:Windows are more secure. by c1pher · · Score: 0, Offtopic

      but Windows is often broken, hence the bugs crawl in..

      --
      The Adult Happy Meal - "I'm lovin' it!"
    3. Re:Windows are more secure. by Anonymous Coward · · Score: 0

      No, but all of my apples have stickers that say "Razorblade Inside".

    4. Re:Windows are more secure. by gellenburg · · Score: 1

      Maybe not, but if I throw my apples at your windows hard enough, chances are your windows will break.

      Or, you'll have apple sauce.

  11. The main difference by LinuxMacWin · · Score: 3, Interesting

    .....

    Contrary to his article, the small market segment held by Apple doesn't automatically make the Mac OS less vulnerable to attack or exploitation. Any competent security professional will tell you that "security through obscurity" - what Lance is referring to toward the end of his article - doesn't work. In other words, if, as he suggests, Mac OS was the dominant operating system, its users would still enjoy an inherently more secure and trustworthy computing environment even if the number of attacks against it increased. That's because unlike Windows, Mac OS was designed from the ground up with security in mind. Is it totally secure? Nothing will ever be totally secure. But when compared to Windows, Mac OS is proving to be a significantly more reliable and (exponentially) more secure computing environment for today's users, including this security professional. .....

    1. Re:The main difference by Firehawke · · Score: 1

      Oh, I fully agree, but at the same time I have to question all these benchmarks we use to compare architectures. Not the numeric kind, but the not-so-easily quantified ones.

      For instance, the "Grandmother" test-- the very idea itself is flawed. A computer is a more complex tool than most any other; the sheer range of possibilities make it impossible to design it completely to the point that someone can sit down at one and figure out everything there is to know without a lot of time and effort.

      Then, on top of this, you've got the idea that the two most-frequently compared via this already flawed test are BOTH failing it though you'd never hear that from the way the detractors talk.

      MacOS, Windows, Linux, BSD-- there IS no panacea for the desktop. The answer for one person will not be the answer for everyone.

      Yet, we'll still be battling out this pointless war years from now in a holy war full of fervor reminiscent of those that spilled real blood in past centuries.

      Both of the articles this story references are nothing more than a continuation of misfacts and misconceptions that continue to be thrown around.

    2. Re:The main difference by Trurl's+Machine · · Score: 4, Insightful

      Any competent security professional will tell you that "security through obscurity" - what Lance is referring to toward the end of his article - doesn't work.

      Please observe that the term "security through obscurity" is often used in two slightly different meanings, one that obviously doesn't work and one that is at least not so obvious. Let me separate them:
      THE ONE THAT OBVIOUSLY DOES NOT WORK is "let us make our system as obscure as possible by refusing to supply any extensive documentation to the public, not to mention the source code; the less anyone knows about our system the better". Microsoft often resorted (still resorts?) to this kind of "s-t-o" strategy. It doesn't work, because sooner or later the internal documentation will leak, malicious crackers will get it anyway and the bona fide hackers won't provide you with their valuable security alerts, patches etc. This meaning of "s-t-o" has actually nothing to do with the popularity of a given system - it's a matter of a vendor's strategy, not a market share.
      THE ONE THAT IS NOT THAT OBVIOUS AFTER ALL is "let us maximize our security by choosing a system that is not-so-popular, so at least the script kiddies would have to do some homework before they could even try to log in to our network, not to mention use any actual exploits". To some extent it works - script kiddies by very definition go for an easy prey and a not-so-popular system is not one.

      Now, please observe that MacOS X does indeed offer "s-t-o", but only in the latter, not-so-obvious meaning. In the first meaning, it is not obscure at all. Everything related to network, communications, protocols etc. is open in MacOS X - only the GUI layer is proprietary.

      I don't like the "security through obscurity doesn't work" mantra just because it is a mantra - people seem to just repeat it, without backing it with any examples. In some cases it's obvious, but in some - it is not. Just wanted to clarify that.

    3. Re:The main difference by drsmithy · · Score: 1
      That's because unlike Windows, Mac OS was designed from the ground up with security in mind.

      Except Windows NT *was* designed from the ground up to be secure - moreso than OS X.

      There's a whole bunch of people here who seem incapable of distinguishing the difference between *design* and *implementation*.

      *Design* gives you things like multiple user contexts and ACLs.

      *Implementation* gives you things like default user running as admin and world-writable directories.

      *Design* is really hard to fix - no-one is going to make DOS or Windows 95 secure, for example, or escape the problems involved with an all-powerful root user just by twiddling the implementation.

      *Implementation* is relatively easy to fix - all you need to do is pick some decent defaults and coerce developers into obeying them.

    4. Re:The main difference by Anonymous Coward · · Score: 0

      "Any competent security professional will tell you that "security through obscurity" ... doesn't work."

      I am sorry, but you are just ignorant. Security through obscurity DOES work, and can be a vital component of a secure and useable system.

      What exactly do you think a password IS?

    5. Re:The main difference by tres · · Score: 1

      You know, your whole argument rests on the assumption that the number of vulnerabilities associated with any platform is analogous to the number of script kiddies on any platform; i.e. script kiddie==vulnerability.

      This is a spurious correlation. The number of vulnerabilities for any platform is not the result of the number of script kiddies out there on the platform. Script kiddies rely on the existence of hacks and software as well as vulnerabilities to exists. The script kiddies that exist for any platform are a symptom, not a cause.

      So, your "not so obvious" definition of security through obscurity--though entertaining--doesn't really hold water.

      --
      Notes From Under *nix: blas.phemo.us
    6. Re:The main difference by EddWo · · Score: 1

      Thankyou.
      Too many people here compare the security of *nix and Mac OSX to Windows 9x.

      Unix isn't inherently more secure than NT, its just some bad decisons by MS to put features and backwards compatibility above security defaults that makes Windows less secure out of the box.

      The idea that NT cannot be locked down as much as Unix due to design issues seems to perpetuate.

      --
      "Taligent is still pure vapor. Maybe they'll be the last who jumps up on Openstep... "
  12. See what happens? by Anonymous Coward · · Score: 1

    When you add value to BSD software? You out-preform Microsoft.

  13. My word-search on the article ... by foobsr · · Score: 2, Interesting

    ... missed both UNIX and BSD.

    Now what except the GUI is so specific to OS X that one may write an article related to security without at least touching the root(s).

    CC.

    --
    TaijiQuan (Huang, 5 loosenings)
    1. Re:My word-search on the article ... by pyros · · Score: 1
      your word-search sucked.

      Unlike Windows, Mac OS X requires an administrator password to change certain configurations, run the system updater, and when installing new software. From a security perspective, this is another example of how Apple takes a proactive approach to system-level security. If a virus, remote hacker, or co-worker tries to install or reconfigure something on the system, theyre stymied without knowing the administrators password stored in the hardened System Keychain. ( Incidentally, this password is not the same as the Unix 'root' account password of the system's FreeBSD foundation, something that further enhances security.) In some ways, this can be seen as Mac OS X protecting a careless user from themself as well as others.

      emphasis added.

    2. Re:My word-search on the article ... by Anonymous Coward · · Score: 0

      Actually, broham, he does mention FreeBSD:

      "(Incidentally, this password is not the same as the Unix 'root' account password of the system's FreeBSD foundation, something that further enhances security.)"

      I haven't used OS X in a couple years now, but I'm rather quite certain that it was originally based on 4.4BSD-Lite, and not FreeBSD in particular...

      -Jacque Schitte

  14. Why the problem? by Anonymous Coward · · Score: 0

    PC Mag (and other MS type mags) are dominated by authors who are devoted to MS. It was a given that they are going to write in this fashion (same style of writing has been going on against Linux for years). I say, do not worry about it. They will be going away sooner rather than later.

    1. Re:Why the problem? by Anonymous Coward · · Score: 0

      Yes but in terms of "going on against Linux" they were right. Linux is a piece of shit, compared to Windows XP. When longhorn comes out, Linux is toast. OS X towers above both of them.

  15. "what happens when you don't understand..." by Bug-Y2K · · Score: 2, Insightful
    "... the problem."

    A blog entry (not mine) on the subject.

    Enjoy.

  16. He he he by Jon+Abbott · · Score: 1
    From the article:
    In other words, you're either with him or with the "zealots." Where have we seen this narrow-minded extremist view before?
    Sounds very familiar...
  17. The wierd thing... by stuffedmonkey · · Score: 3, Insightful

    is that Mac os 9 was completly safe to the outside world. AFIK there were no remote holes - now it did crash every ten to fifteen minutes on me, but I've never seen remote vulnerablitly. Wasn't the army using a few G4 towers with Webstar as html servers? I wouldn't go back to 9 from 10.3 - but it was amazingly secure.

    1. Re:The wierd thing... by log0n · · Score: 1

      OS9 didn't have a CLI to exploit and no built-in remote admin features, it wasn't really multi-user oriented, and most importantly it didn't use null-terminated strings (meaning no buffer overflows).

      It was secure

    2. Re:The wierd thing... by log0n · · Score: 1

      oops..

      it was secure because it was pretty much air tight to the probing outside world.

    3. Re:The wierd thing... by jaysones · · Score: 2, Insightful

      What do you mean "no doubt there were plenty?" Is that just pure speculation? OK here's my rebuttal: There were none and the OS9 codebase was 5 lines long. I won't provide any proof of that statement either and we can continue our fact-free discussion.

    4. Re:The wierd thing... by HeghmoH · · Score: 1

      This is not "Insightful".

      Yes, there is plenty of doubt that there were plenty. OS 9 literally has no services built in; none. A fresh install of OS 9 is displaying no open ports to the outside world. The only kind of vulnerability it could possibly have had would be a vulnerability in the TCP stack itself. And then you have to somehow load in enough code to gain remote access. It's not going to be some little 500-byte assembly program that opens a port and connects it to /bin/sh, because these ideas don't exist. You'll have to send over a complete remote access solution with your vulnerability, because the OS didn't come with one.

      OS 9 was not particularly useful in a network environment, but rest assured that it was plenty secure.

      --
      Mod down posts with a "Free Mac Mini/iPod" sig, they're spam!
    5. Re:The wierd thing... by Graff · · Score: 2, Informative
      Mac os 9 was completly safe to the outside world. AFIK there were no remote holes - now it did crash every ten to fifteen minutes on me, but I've never seen remote vulnerablitly.

      The classic Mac OS's did have vulnerabilities, but they were not well-documented and sporadic. In certain places bad coding produced code that was vulnerable to buffer overflow exploits. However, those are difficult to use under the best of circumstances.

      Because Mac OS did not run on x86 hardware it had a different stack structure. Not only that but the processors used have always been big-endian. In order to exploit the buffer overflow vulnerabilities you would need to code in PowerPC assembler, using big-endian, and in a manner able to exploit the stack structure of Mac OS. This is a tall order because it is uncommon enough that there is not many resources out there on how to do it. Script kiddies thrive on these exploits in the x86 world because there is a ton of info on how to do it.

      Not only that but Apple's development is pretty tight and planned and they did nip a lot of these invunerabilities in the bud before they became common knowledge. So no Mac OS, classic or modern, has ever been completely bulletproof but it has been a very hard target to hit for exploiters. So hard. in fact, that almost no attempts have been made
    6. Re:The wierd thing... by Trurl's+Machine · · Score: 5, Informative

      is that Mac os 9 was completly safe to the outside world. AFIK there were no remote holes - now it did crash every ten to fifteen minutes on me, but I've never seen remote vulnerablitly.

      You can see one anytime you want by just checking this test site. It works in a similar way as the infamous autostart worm that plagued MacOS Classic machines. The vulnerability works as follows:

      1. You click on a link on a website like the above. It starts to download a stuffit-packed disk image to your desktop [without asking; that's the default configuration]
      2. Stuffit unpacks and mounts the image [without asking; that's the default configuration]
      3. Classic QuickTime sees a newly mounted image and initiates Autostart procedure [DEFAULT CONFIGURATION!]
      4. Bingo - you allowed a remote source to execute arbitrary code on your system; and even under MacOS X, it started as a Classic layer process so it runs actually as root

      The test site "attacks" you only with a very simple AppleScript applet that only opens your trashcan and that's it. But just think of the possibilites for a really malicious use. It was a very severe vulnerability for all vanilla-configured MacOS 9 (and earlier) machines; but unfortunately, also MacOS X machines with their Classic layer configured as the vanilla MacOS 9 were affected. THIS INCLUDES the MacOS X 10.3 "Panther". In fact, Classic layer always was and still is the biggest security hole in MacOS X, but that's another story. Anyway, Apple was crazy to provide Autostart option in QuickTime (who needs it, anyway?) but it was even more crazy to provide it as the DEFAULT configuration.

    7. Re:The wierd thing... by Durandal64 · · Score: 1

      How the fuck is pure speculation 'insightful'?

    8. Re:The wierd thing... by soft_guy · · Score: 1

      Not only were there not any publicized holes, but there were actually contests with prize money to be awarded to anyone who would find a hole.

      There were never any takers on a standard system with StarNine installed. Someone did once find an exploit with a third party plubin to WebStar.

      A standard install MacOS 9 box did not have any security vulnerabilities over the network. None.

      No open ports - nothing to attack. You'd have a better chance trying to gain access via AppleTalk than TCP/IP - and even AppleTalk wasn't on by default.

      --
      Avoid Missing Ball for High Score
    9. Re:The wierd thing... by sandbagger · · Score: 1

      If anyone was trying to hack into my networked OS9 machine, all I had to do was hold down the mouse button. :)

      --
      ---- The above post was generated by the Turing Institute. Maybe.
    10. Re:The wierd thing... by martinX · · Score: 1

      hahaha. as a System 7 -> OS 9 user, i appreciate the humour in that post. Why DID a simple thing like a menu dropping down bring the whole system to a screeching pause??? Now I have OS X goodness on my Mac.

      --
      When they came for the communists, I said "He's next door. Take him away. Goddam commies."
    11. Re:The wierd thing... by Anonymous Coward · · Score: 0

      Caution Trurl's Machine :

      1) By default launching Classic need confirmation from the user.
      2) Auto-start CDs doens't launch Classic.
      3) As said in Forno's article : programs cannot modify system files, security preferences or install software without user password

  18. It wasn't just his tone by burgburgburg · · Score: 1
    It was the content. He didn't understand the problem, the overblew it beyond any comprehension and he attempted to find an equivalence between the issue and the base, core problems with Windows as far as security. The fact that he ladled his ridiculously stupid "commentary" with a kid burning ants gleefulness was just a capper.

    That people pay him money to spew out crap like that (and that other people that are supposed to be fact-checking/editorially judging are as well) is truly depressing.

  19. Mac Elite loves to feel cocky... by FatSean · · Score: 1

    ...right you are!

    --
    Blar.
    1. Re:Mac Elite loves to feel cocky... by Dutchmaan · · Score: 4, Funny

      With all due respect any "elite" user is pretty abhorrent to be around...

      I'm sure we all know a:

      Mac Zealot
      Microsft Apologist
      Pompus Unix Geek

    2. Re:Mac Elite loves to feel cocky... by KevCo · · Score: 3, Funny

      But now you can be a Mac Zealot and a Pompus Unix Geek at the same time! Its great!

    3. Re:Mac Elite loves to feel cocky... by scottblascocomposer · · Score: 1

      Something about that subject line just sounds dirty...

      --
      To reign is to serve.
    4. Re:Mac Elite loves to feel cocky... by southpolesammy · · Score: 4, Funny
      Pompus Unix Geek
      Wally -- "Wait a minute, that beard, those suspenders, that smug expression!"
      Wally -- "You're one of those condescending UNIX computer users!"
      UNIX-guy-- "Here's a nickel, kid. Get yourself a better computer."

      --Dilbert, c. 1994
      --
      Rule #1 -- Politics always trumps technology.
    5. Re:Mac Elite loves to feel cocky... by notque · · Score: 1

      I'm sure we all know a:

      Mac Zealot
      Microsft Apologist
      Pompus Unix Geek


      And some of us know someone who is all three.

      *shudder*

      --
      http://use.perl.org
    6. Re:Mac Elite loves to feel cocky... by Anonymous Coward · · Score: 0

      I'm sure we all know a:

      Mac Zealot
      Microsft Apologist
      Pompus Unix Geek


      The most bizarre character I've ever met was a Microsoft apologist *and* a mainframe bigot.

    7. Re:Mac Elite loves to feel cocky... by Anonymous Coward · · Score: 0

      Dear God/Allah/Yahwe/Jehovah NO!

    8. Re:Mac Elite loves to feel cocky... by ImTwoSlick · · Score: 1
      I'm sure we all know a:

      Mac Zealot
      Microsft Apologist
      Pompus Unix Geek


      Shoot... What if I'm all three?

    9. Re:Mac Elite loves to feel cocky... by G-funk · · Score: 1

      Dude, this is slashdot. Most of us _are_ one of these. That's why it's so fun in here :)

      --
      Send lawyers, guns, and money!
    10. Re:Mac Elite loves to feel cocky... by ernstp · · Score: 2, Funny
  20. I have not heard of one successful r00ting of OS X by teamhasnoi · · Score: 5, Interesting
    Are there *any*? With a generic default install of 10.3 (plus net connection), are there any remote exploits? I'm guessing that any exploit that has been found is due to 3rd party software.

    Are there any viruses/trojans for OS X?

    I know there was the ssh deal a while back, but does anyone know of any remote r00ting of an OS X box anywhere?

  21. Re:Don't always assume a smear campaing by proj_2501 · · Score: 5, Insightful

    "or wrong, never fully read it or the rebuttal"

    so why comment on the relationship between the two if you are obviously misinformed and you admit it?

  22. Re:Don't always assume a smear campaing by EvilFrog · · Score: 3, Interesting

    The tone of the article has a lot to do with the assumption.

    I mean, if I said, "I wish he'd just shut his mouth if he's not going to read the article," you can safely assume more malice there than if I said "He really should read the article before commenting," right?

  23. Re:PC != windows. by Sexy+Bern · · Score: 1
    Also, Apple != Mac OS

    19:56 cyprus ~ % uname -a
    Linux cyprus 2.4.18-newpmac #1 Thu Mar 14 22:44:49 EST 2002 ppc GNU/Linux

  24. Audit. WAS: Re:trust by voixderaison · · Score: 5, Insightful

    If you work in a place where "security is EVERYTHING", then you should know that trust is *not* the bottom line.

    Don't trust vendors.
    Don't trust open source.
    Trust no one.
    Audit.

    --
    Things should be made as simple as possible, but not any simpler. -- Albert Einstein
  25. My security answer by pvt_medic · · Score: 1, Funny

    My security is a big ax. Just try breaking into my computer, and I will HACK you.

    --
    30% Troll, 50% Underrated, 10% Interesting
    Score:5, Troll
  26. Re:Don't always assume a smear campaing by pyros · · Score: 5, Insightful
    Not to say the original article was right (or wrong, never fully read it or the rebuttal) but it's shortsighted to assume criticism comes from zealous hate.


    It's not too much of an assumption. The author of the orinigal piece said he was glad that there was finally a big vulnerability for Mac OS, and that he was tired of Mac users looking smug when SAMS edition Conquer the Internet in 12 Hours outlook viruses pass them over. The whole piece just had a tone of "I'm really sick of people bragging about Mac OS."

  27. stubborn institutional pride/hubris, etc... by The+Lynxpro · · Score: 5, Interesting

    I think Apple has shown the way Microsoft should follow if they wish to bring security and stability to the Windows platform. Apple migrated over to the underpinnings of BSD without compromising the distinctness that only Apple brings to the table. If Microsoft truly cared about "trustworthy computing," they'd shift their gears and concentrate on gluing the Windows GUI and other applications to whatever BSD platform they chose to annoint. After their acquisition last year (the VirtualPC crew), Microsoft has the talents necessary to bring decent emulation of older Windows flavors to their new products. But apparently they [Microsoft] are too stubborn for their own good. It sounds like Longhorn will now be delayed until 2006 or 2007, and every year they slip, the more people and institutions will slip away to Linux and OS X for the very ideal of "trustworthy computing" they profess. Windows is broken as an OS, but as a GUI "bundled" on top of BSD, it would prove to be the magic Microsoft's shareholders are now searching for. And since Microsoft has been infusing SCO with cash, Microsoft would be "safe" from any litigation from SCO in regard to BSD or Linux...

    --
    "Right now, somewhere in this world, Scott Baio is plowing a woman he doesn't love," - Peter Griffin, *Family Guy*
    1. Re:stubborn institutional pride/hubris, etc... by pyros · · Score: 1

      In order to maintain the one thing the use as a competitive edge (the integration of everything) without giving the same edge to competitors would be to make a totally proprietary system forked from FreeBSD. Of course, it would remove many of the features that make it secure, otherwise the integration wouldn't work. So why bother?

    2. Re:stubborn institutional pride/hubris, etc... by zgwortz962 · · Score: 5, Informative

      Honestly, Microsoft trying to put a Windows GUI on top of BSD is probably a bad move for them. The problem, as is always the issue with new OSes, is drivers.

      Apple was able to get away with Mac OS X on top of BSD, using their own modern driver architecture (IOKit) because they had a relatively small hardware subset that they had to support (and you'll note they didn't even *try* and support a whole bunch of their older machines...). And it still took them 4 years to get the first version out the door.

      For Microsoft to to the same thing would be tons more complicated, given the ungodly amount of hardware they have to support.

      (Drivers are the long term bane of Linux and BSD as well -- The Linux driver model is, IMHO, a horribly antiquated mess needing a complete tear out and replacement. It's not going to get that anytime soon for the same reasons outlined above - too many new drivers to support. I'm not familiar with the BSD model, but if it's anything like the over 20 year old UNIX device model, I'm *very* glad Apple chose to use IOKit instead...)

      IMHO, if Microsoft wants to produce a truly stable OS, they need to tear their kernel development away from the rest of the OS, and put everything else (especially IE) in a nice isolated sandbox. I would say the vast majority of Windows security holes are there because MS tries to integrate way too much high level functionality into the core OS.

      Of course, if they do that, then they risk people adding their own sandboxes on top of their core OS (like Java...) and losing control of the application developers who currently are slaved to that highly integrated high level functionality...

    3. Re:stubborn institutional pride/hubris, etc... by DShard · · Score: 2, Interesting

      It is not the kernel that is the problem. It _is_ the GUI. NT's kernel is just as good as Darwin as it shares almost the entire design methodology. All the insecure stuff exists in userland (IE, ISS, Outlook, MS scripting, MSSQL, COM, and so on) As was haughtily brought up in the rebuttal was that by default most services are off in OSX. (Of course I fail to see how either OSX or windows are better than Linux or BSD in this regard.) Changing kernels isn't going to stop the nearly twenty years of unaudited, insecure legacy crap that is layered on top of it.

    4. Re:stubborn institutional pride/hubris, etc... by cosmo7 · · Score: 1

      All of these 'problems' can be advantages for Microsoft.

      Suppose Longhorn dies in the same way Apple's Copland did. Microsoft looks around for a unix to base a replacement (perhaps called 'OS Z'). They wouldn't go for Linux as that would be a tacit endorsement of OSS, so instead they either go for BSD, SCO or - perhaps as part of a fat deal for Apple - Darwin.

      They include an XP compatibility box, much like OS X Classic. As developers release native drivers, MS ensures that these drivers work through OS Z, not through the kernal. OS Z allows MS to abandon considerable legacy hardware - floppy drives, ports, bios and further cement its grip on commodity PC architecture.

      I'm not saying this would be a good thing, but I can imagine it happening if Longhorn goes off the rails.

    5. Re:stubborn institutional pride/hubris, etc... by Anonymous Coward · · Score: 0
      Migrating to a BSD layer brought them the vast Open Source unix world and some of the mindshare which goes with being a player in that world. It brought them the ability to run a lot of applications which a Mac could not run before. What it did not really bring was a greater level of security, as OS 9 boxen were already damn near impossible to hack before the migration.

      There were plenty of things wrong with System 7 - MacOS 9, but poor security was never one of them.

    6. Re:stubborn institutional pride/hubris, etc... by spitzak · · Score: 1

      For a long time Linux had *lots* of services enabled by default. Often every possible thing was turned on, such as ftp. Linux users should not be too smug, they were as stupid as Microsoft at one time.

      Fortunatly at about the moment people started using Linux in home situations but with always-on connections (1996 or so) this was realized to be very stupid, and it seems modern ones have everything turned off. But I'll bet there are a lot of completely open old Linux boxes out there still!

      Modern Windows seems to have turned everything off except for the services needed to connect to and obey the mothership, so they are improving as much as their business model allows.

    7. Re:stubborn institutional pride/hubris, etc... by Anonymous Coward · · Score: 0

      It's not so simple. Unfortunately, MS and Apple have gone down different paths for compatability.

      In the mid 1980's MS bent backwards to make sure that backward compatability was seen as a DOS trait. There were lots of tricks to make programs faster but you tied yourself very closely to the OS. MS liked people being tied to their OS and maintained compatability with these bad programming practices. It continues today with people calling undocumented system dll functions.

      At the same time, the mid 80's, Apple taught everyone that conformance to the published API was all they cared about. People tried to do the same thing with MacOS that they did with DOS and were supprised when Apple broke everything but the API.

      So MS has all of these tricks programmers have used that have to stay in the system. But Apple can change the OS, processor or whatever and it can still behave like a Mac.

    8. Re:stubborn institutional pride/hubris, etc... by The+Lynxpro · · Score: 1

      "Honestly, Microsoft trying to put a Windows GUI on top of BSD is probably a bad move for them. The problem, as is always the issue with new OSes, is drivers."

      Funny, you should mention the drivers issue. I seem to recall that Windows2000 had driver issues (actually, the lack of drivers) when it debuted and that was one of the major reasons why gamers had to stick with Win98SE for their rigs instead of moving to the more stable and SMP supporting Win2000 platform.

      Yes, Apple has/had much less hardware to have to support and they did exclude a lot of machines in their migration path to OS X. However, Microsoft does not want to support older hardware either. If Longhorn requires "Trustworthy Computing" built into BIOS and microprocessor chips, then Microsoft will be excluding the entire existing PC base from their operating system roadmap. Therefore, the driver issue wouldn't be an issue anyway since Longhorn (either based on Microsoft code or BSD for this example) will already artificially limit the hardware it will interact with.

      Of course, this could all be posturing by Microsoft and they will probably cave in before 2007 on the hardware keys or face even further erosion of their monopoly...

      Interesting post, by the way... :)

      --
      "Right now, somewhere in this world, Scott Baio is plowing a woman he doesn't love," - Peter Griffin, *Family Guy*
    9. Re:stubborn institutional pride/hubris, etc... by Anonymous Coward · · Score: 0

      You are ignorant. The problems with windows have nothing to do with the NT core.

      The NT core of Windows was designed with security in mind, and is quite successful. The problem has always been the Windows implementation on top of the NT security being too lax in order to allow for ease-of-use for end users. Windows security needs to be fixed, but BSD isnt the solution because NT isnt the problem.

    10. Re:stubborn institutional pride/hubris, etc... by DShard · · Score: 2, Interesting

      If you have _any_ OS sitting on the internet with no firewall between you and joe script kiddie and have not at least turned off all unnecissary services then it is simply your own stuppidity. When you _can't_ turn off those services and you get caught with microsofts pants down switch to some other system who cares. Having installed slackware circa 94 I don't remember having all services on. Knowing the people I did at college would have given them ample oppertunity to screw with me... So your either misinformed or worse...

    11. Re:stubborn institutional pride/hubris, etc... by EddWo · · Score: 1

      Looks like they agree with your idea. Microsoft to reshuffle Windows Unit

      --
      "Taligent is still pure vapor. Maybe they'll be the last who jumps up on Openstep... "
    12. Re:stubborn institutional pride/hubris, etc... by davegust · · Score: 1

      I seem to recall that Windows2000 had driver issues (actually, the lack of drivers) when it debuted

      Win 2000 and 98 both supported the unified driver model, which was available to developers at least four years before 2000 was released. This was done to ensure 2000 had good driver support at it's release - which it did. 2000 wouldn't support 95 drivers, but it would use both 98 and NT drivers.

      The parent is right - driver support is critical for an OS. One could argue it is the primary purpose for an OS to exist. Printer drivers were a primary reason for creation of Windows in the early 80's. Bill needed an environment for Word and Excel, one for printer manufactures to target. You see WordPerfect 5.1 was number one largely due to it's fantasic use of printers - cool fonts and graphics, independant of printer capability. Printing under Linux/Unix is still an adventure if the printer doesn't support post-script.

    13. Re:stubborn institutional pride/hubris, etc... by eMilkshake · · Score: 1

      There has only been one kernel exploit in Windows in the last few years, if memory serves correctly. A lack of memory protection was highlighted as a contributing cause to slammer, but that wasn't the only cause.

      What you recommend is a kernel switch. That's not where the problem has been. Now, NT x employs a microkernel architecture, so some of the services that have gotten exploited would have been in the Linux kernel (not sure about BSD), so you could argue there, but again, it's the higher services that get hacked.

      Do you think if IIS was ported to BSD or Linux it would be safer? Do you think Outlook would be different? Do you think the default user would not be root? Haven't you seen the exploit that uses the GUI COMBO BOX of all things?

      No, Windows has a great kernel. It's modular and scalable and performs well. Windows understands granting tokens various rights so you don't have the root/nonroot scenario. That other stuff to which you refer is the problem, so switching kernels/cores isn't the answer unless it's the impetus for an overhaul, but it's the overhaul that's needed.

      Ironically, I remember Windows NT as being the overhaul that Win16 needed because Win16 had been remade too often and crusted up with "end user junk." It seems history repeats itself.

      Still, backwards compatibility is difficult, and you have to make a choice -- do you want to be able to run Visicalc on Windows XP (you can) or do you want a locked down, secure system? How many times has Apple remade things? They switched computer platforms (Apple I, II, III, Lisa, Mac), they switched CPUs (68K, PPC) and they switched the fundamental OS. MS switched from 16bit to 32bit. They don't even support other CPUs anymore (with a wink at 64bit). The industry would kill them if they made the switches that Apple made. I believe it's maintaining this compatibility that gives them many of the problems and hurdles to making better products.

  28. Can't resist... feeding... the... Troll by kylef · · Score: 4, Funny

    You are right, of course. But expecting Forno to avoid name-calling would mean expecting him to avoid feeding the Troll. This one was so cute, and looked so hungry... Maybe just a LITTLE food would be okay...

    Crap. Slashdot picked it up. So much for keeping the Troll population down this Christmas season!

    1. Re:Can't resist... feeding... the... Troll by RogerWilco · · Score: 1

      Hmmm, better memorize some Melv's Acid Arrow spells, maybe add a Fireball and a Flaming Sphere while we're at it.

      --
      RogerWilco the Adventurous Janitor
  29. Re:PC != windows. by Anonymous Coward · · Score: 0

    Also, Mac OS != Mac OS X, since the original article's autor used the interchangable.

  30. Better read than the PC Mag Article by OS24Ever · · Score: 3, Funny

    This at least had some bullets that backed up the statements.

    The PC Mag article read as a 'neener neener neener I hate you' article vs. something with content.

    --

    As a rock-in-roll Physicist once said, No matter where you go, there you are.

  31. Re:Don't always assume a smear campaing by NaugaHunter · · Score: 5, Informative

    From the original article:
    How cocky are you feeling now, Mac elite?

    While the original article's criticism may not have come from "zealous hate", it certainly didn't come from impartial journalism. This and other statements like it definitely tinted it from simple reporting to an apparent attack, complete with the subliminal childish prat-calls.

    --
    R: That voice. Where have I heard that voice before? B: In about 365 other episodes. But I don't know who it is either.
  32. Re:PC != windows. by Sexy+Bern · · Score: 1
    Worse still, autor != author

    :)

  33. Gratuitous politics by Silverhammer · · Score: 0

    Blockquoth the article:

    In other words, you're either with him or with the "zealots." Where have we seen this narrow-minded extremist view before?

    Oh joy, now we can't even have a decent "Mac versus Windows" flamewar without someone spinning off into gratuitous political trolling. May they both rot in /dev/null...

    1. Re:Gratuitous politics by Ohreally_factor · · Score: 1

      Unix vesus Vax is political?

      --
      It's not offtopic, dumbass. It's orthogonal.
  34. Parent post summed: by Jesrad · · Score: 1

    "Never attribute to malice what can be explained by stupidity."

    --
    Maybe we deserve this world ?
  35. This just in by Anonymous Coward · · Score: 0

    I can counter anything by countering it. It means I'm a clever zealot. More at 11.

  36. Your word search is broken :) by Mr.+Sane · · Score: 2, Interesting

    Snippets from the article: ..."system's FreeBSD foundation"...
    and ..."the Unix-based Mac OS X system"...
    and ..."not the same as the Unix 'root' account password"...

    You must be referring to the *original* article... the first makes no reference to BSD or UNIX. Based on that, I wholeheartedly agree with your assessment - I do not think that the original author had a real understanding of OS X, BSB, UINX, or for that matter, even Windows.

    We would never actually read a serious article of this nature because any person that takes the time to do a security review of Windows would find so many holes they would never finish their article. And they'd probably have to write it twice. And it would be posted on the internet before they could publish it.*

    *I may have exaggerated slightly on the last few points :)

    1. Re:Your word search is broken :) by Mr.+Sane · · Score: 1

      That would be BSD and UNIX. I don't understand BSB and UINX either.

    2. Re:Your word search is broken :) by WebMasterJoe · · Score: 1
      I do not think that the original author had a real understanding of OS X, BSB, UINX, or for that matter, even Windows.
      Oh, there are plenty of other OS's he probably didn't understand, like AimgaOS, BoES, Solairs, NQX, or even Windows PX. :)
      --
      I really hate signatures, but go to my website.
    3. Re:Your word search is broken :) by foobsr · · Score: 1

      ... no, it was me. RTFA/2 sucks, I missed the read more.

      Regrets. Blush.

      CC.

      --
      TaijiQuan (Huang, 5 loosenings)
  37. This seems awfully long-winded... by WIAKywbfatw · · Score: 5, Funny

    Hey, reading this is slow going. Anyone got a link to the PowerPoint slideshow version for dummies?

    --

    "Accept that some days you are the pigeon, and some days you are the statue." - David Brent, Wernham Hogg
    1. Re:This seems awfully long-winded... by Frymaster · · Score: 1

      don't you mean "keynote slideshow for dummies"?

    2. Re:This seems awfully long-winded... by Saeger · · Score: 2, Funny
      Don't be ashamed of your short attention span, my brother! These are fast times we are living in, but your brain isn't getting any faster (yet) to process all that information in its entirety... until now!

      Try the revolutionary new NeuralInfo(TM) interface chip. It's very simple: all it takes is one person to learn or experience something the hard way, once, then that non-unique pattern of knowledge can shared by billions in a milliseconds.

      The "RTFA mod"(TM) is only 50 credits! ("Read" in past tense)

      --

      --
      Power to the Peaceful
  38. MS should learn from ship builders by nv5 · · Score: 5, Insightful

    One of the great breakthroughs in safety design came when ships started to be built with compartments, which would prevent a single hull puncture to sink the whole ship. (Sadly the Titanic's compartments were all aligned in one dimension, so when the puncture was very long, it compromised all compartments).

    One of my greatest concerns with MS attitude towards design of their "ships", especially Windows and Office is, that they are integrated way too much. So any security "puncture" spills over way too easily into the rest of the ship. As a very annoying side effect, one ends up re-booting for way too many MS patches. Why should I have to reboot, if I patch my browser or e-mail client?

    Of course, MSIE, Outlook and MS Office vulnerabilities have been a lot less worrying for me, since fully switching to Mozilla and OpenOffice over a year ago!

    1. Re:MS should learn from ship builders by Anonymous Coward · · Score: 0

      To patch IE requires a reboot because IE is running to run windows auto-update. I didn't have to reboot when I patched IE from a zip drive.

    2. Re:MS should learn from ship builders by freeweed · · Score: 1

      Why should I have to reboot, if I patch my browser or e-mail client?

      This one's even more fun:

      1. Install IPX on an XP box. You don't have to reboot. Cool, MS figured out how to load a network stack dynamically.

      2. Now uninstall IPX. You're asked to reboot.

      3. ?

      4. ????????

      I'm so far happy with the less frequent reboots in the modern NT world, but does anyone have an idea as to why installing doesn't require a reboot, but UNINSTALLING does?

      --
      Endless arguments over trivial contradictions in books written by ignorant savages to explain thunder in the dark.
    3. Re:MS should learn from ship builders by Keeper · · Score: 1

      Why should I have to reboot, if I patch my browser or e-mail client?

      Because one of the file(s) replaced by the installer is in use by another applicaiton, and the old version can't be removed until it is no longer in use. When most installers run, they schedule a task to run when the computer starts up to remove the old file and replace it with the new one.

    4. Re:MS should learn from ship builders by BitchKapoor · · Score: 1

      That doesn't make any sense, you could just have a separate process which gets started and finishes updating MSIE after the browser has closed.

    5. Re:MS should learn from ship builders by Anonymous Coward · · Score: 0

      Actually Microsoft should have paid attention in software engineering class. Specifically the lecture about making sure your applications/libraries have high cohesion and low coupling.

    6. Re:MS should learn from ship builders by nv5 · · Score: 1

      Because one of the file(s) replaced by the installer is in use by another applicaiton, and the old version can't be removed until it is no longer in use. When most installers run, they schedule a task to run when the computer starts up to remove the old file and replace it with the new one.

      sigh... sorry - the question was rethorical - I know the technical reasons; it exactly underlines the point I was trying to make; the MS design is lousy, since it uses files in regular apps, which are in use (or just marked as such) by the OS. This is lousy design, and many other applications (e.g. Mozilla) don't have that problem. And of course on Linux rebooting is an almost unknown occurrence after software upgrades - similarly on the Mac, a reboot usually only required after a major OS upgrade. So it can be done :)

      And this overly integrated design is at the source of a lot of my concerns as per my original post (2 levels up).

    7. Re:MS should learn from ship builders by blasphemi · · Score: 1

      4. Profit! (For M$ that is).

    8. Re:MS should learn from ship builders by tc · · Score: 1

      So why not just shut down the app in question (or prompt the user to do so) rather than rebooting the whole freaking system?

    9. Re:MS should learn from ship builders by Keeper · · Score: 1

      What, you think it's BETTER to take a file being used by an application and replace it with another one? WHILE IT IS RUNNING? What planet are you living on? Worst. Idea. Ever.

      I've actually seen some installers ask you to shutdown applications that are using files it needs to replace, which avoids the reboot problem. But most of them just go the "ask the user to reboot" route. I've also seen installers that ask you to reboot your computer for no apparent reason whatsoever.

      Getting back on track somewhat, Mozilla doesn't have the problem because it doesn't share any components with other applications. Try installing a new version of Mozilla on top of an old one while it's running -- you'll have problems.

      On linux, every version of every library is given a unique filename. So you've got like 50,000 versions of the same library on your machine (which may or may not be a good idea).

      I don't have any recent experience with Macs, but my experience with them in high school lead me to believe that the concept of a 'shared library' didn't exist on them. Everything was bundled into the application. And reboots were required anytime you dropped something in the system folder, not just OS upgrades.

      So if you think that shared non-statically linked libraries are bad, then yes, you won't like the Windows way of doing things.

    10. Re:MS should learn from ship builders by Keeper · · Score: 1

      Some of them do (see the Office2k3 installer). Most don't. Others ask you to reboot the machine for the hell of it (the company I used to work for went this route; the guy working on the installer was a freek'in idiot).

    11. Re:MS should learn from ship builders by nv5 · · Score: 1

      I think your observations are correct (at least in my experience). Of course it's a really bad idea to replace libraries in a running program. That's why many of the better installers restart the program in question when upgrading (rather than the whole machine). And of course, if the shared libraries are part of the OS, you are pretty much stuck with a reboot. Your last sentence,

      So if you think that shared non-statically linked libraries are bad, then yes, you won't like the Windows way of doing things.

      captures my sentiments. I know, shared libraries create efficiencies, but at least for me, at too high of a price in terms of security. It may very well be a personal bias, but I'd rather spend a bit more on extra disk space and RAM for the extra security of more compartementalized applications.

      Don't mean to offend, but in the trade-off of security vs. convenience, in the age of the Internet, I have become much more biased in favor of security.

    12. Re:MS should learn from ship builders by Keeper · · Score: 2, Interesting

      captures my sentiments. I know, shared libraries create efficiencies, but at least for me, at too high of a price in terms of security. It may very well be a personal bias, but I'd rather spend a bit more on extra disk space and RAM for the extra security of more compartementalized applications.

      When you statically link libraries, each time you get a security fix for a library you have to rebuild ALL of the effected applications and redeploy them. Forget one, and you're still vulnerable. With dynamically linked libraries, when you replace the library all of your applications get the fix.

      I don't see a security benefit to statically linking a library instead of using a shared library -- if the shared library can be compromised, any of the applications that statically link to that library can be compromised as well.

    13. Re:MS should learn from ship builders by Ciggy · · Score: 0

      M$ probably ARE following the designers' of the Titanic, along with their builders.

      From my memory [of reading about the Titanic disaster - references I can't find at the moment], the Titanic could easily survive a gash through the first 4 of the 14 watertight compartments; however, the gash reached into the 5th. This shouldn't have been too much of a problem, but with the first 4 compartments flooded, the bows dipped; however, for some obscure reason, the 5th bulkhead wasn't as tall. As the bows dipped, the water then flowed over the top into the 6th compartment; followed by more dipping and more overflowing...

      Is IE the 5th compartment/bulkhead of Windoze?

      --

      A rose by any other name would smell as sweet;
      A chrysanthemum by any other name would be easier to spell
    14. Re:MS should learn from ship builders by angulion · · Score: 1
      One of the great breakthroughs in safety design came when ships started to be built with compartments, which would prevent a single hull puncture to sink the whole ship. (Sadly the Titanic's compartments were all aligned in one dimension, so when the puncture was very long, it compromised all compartments).

      The punture on Titanic wasn't that long, the bigger problem was that the compartment walls wasn't high enough, so that when the stearn flooded and sank somewhat, the water spilled over from one compartment to the next resulting in further flooding, finally sinking the whole ship.

  39. Lance Ulanoff... by Anonymous Coward · · Score: 0

    ... should be more worried about his Job security. f00l!

  40. a few things by BigBir3d · · Score: 5, Insightful

    Firstly, my new office machine is a Dell with XP Pro. My home machines are iBook with 10.3, and a ThinkPad with Mandrake 9.x (uptime near 60 days now). All 3 are stable machines that do what I want, when I want. The Thinkpad was the #1 machine until I had enough scratch to buy the iBook (apple.com does nice refurb sales from time to time). When sobig and the other malicious worms of 2003 came out, my office was all win98 machines, and a NT 4.0 server. Due to reading /. and using Norton Antivirus, the only machine affected by the onslaught were the machines I was not "allowed" to touch (#1 computer guy {I am the secondary guy}, and the owner of the company {"I did that already"}. In short, you can run any of these machines safely, with most all of the latest software. It just helps if you are not an idiot.

    PEBKAC

  41. Deservedly by burgburgburg · · Score: 4, Interesting

    The original "commentary" was not just chock full of factual errors, improper syllogisms, et. al. It was dripping with such a malice-filled glee at the notion that OS X might be as insecure as Windows that one has to wonder as to real root of the author's problems. He mentions how angered he is by the laughing of OS X users every time he has to deal with another Windows virus/trojan/bug. Are "commentaries" like his the sad, pathetic result of not working on an OS that "just works"?

    1. Re:Deservedly by trick-knee · · Score: 1

      > Are "commentaries" like his the sad, pathetic result of not working on an OS that "just works"?

      so, in short, The lady doth protest too much.

  42. Re:Don't always assume a smear campaing by antiMStroll · · Score: 3, Informative
    There's and easy way to confirm or dispute the contention. Read the damn article. But since that's too troublesome for the moderators, enjoy some choice cut'n'paste:

    I know this is wrong, but in one respect I was happy to learn earlier this month about the discovery of a significant security hole in the Jaguar and Panther...

    I was tired of the "We use Macs because they don't get attacked by viruses and hackers" refrain from Mac nuts.

    I generally counter with what is apparently a secret carefully hidden from Mac zealots:...

    But the mindlessly superior retort is always the same....

    Given this recent development, my question is, "Will you be stuffing that superior attitude in your crow or eating it separately, sir?"

    Those quotes alone comprise half the first few paragraphs. See, that wasn't too hard, was it?

  43. security through obscurity by siskbc · · Score: 3, Interesting
    "security through obscurity" - what Lance is referring to toward the end of his article - doesn't work.

    I realize this is an oft-repeated truism, and obscurity alone doesn't make a system truly secure...but it certainly helps. To make an analogy, I know of many friends who have been robbed, even when their valuables were well-locked. However, those who put their valuables in places theives never think to look are generally the ones who keep them - good security is never perfect, and is generally at best a deterrent, at worst a challenge. Hell, security through obscurity is the whole basis for steganography, though most would recommend encryption as part of a "why not?" sort of preprocessing step.

    As such, I think it's a given that Windows is at least less secure because of its market share. Whether Mac is more secure because of its obecurity is debatable - I'm sure there are a number of generic unix exploits that macs would suffer from, and the general unix community is very high profile.

    --

    -Looking for a job as a materials chemist or multivariat

    1. Re:security through obscurity by E-Rock · · Score: 1

      Most of the security problems I've seen come from moron users running questionable applications.
      If the e-mail blast from ass-munch marketing had a mac version of their software, spyware and trojans would be just as prevalent on the Mac OS as it is in Windows; but when 90%+ of the machines on the other end are all going to be Windows, you don't write another version.

  44. Re:THINK. by Anonymous Coward · · Score: 0

    LOL :)

  45. We'll Just Have to see by KaeloDest · · Score: 2, Insightful

    I Use, Run and Endorse OS X Server. For home and office use. I was co-incidentally running a Lab similar to that root exploit and guess what OSX is a ::real unix:: it has an exploit. I couldn't replicate because I use Kerberos. But this is the first and only time that I have had my development box (OBJ C / Java), Workgroup Server AND desktop on the same HW. with no loss of data in about three years.
    In three years M$ will come out with supposedly secure computing, with more of an eye toward how to KEEP drm secure than how to prevent massive system intrusions violations. In the past seven years I have had none of this virus hype. It seems like the Mac users and the Linux users are having more in common every year (Except the OS X gets faster on the same HW :-> ). The only way to really be sure is to try the mac. Yes Apple has some ::Issues:: it was only a matter of time before people clues into the OS a year plan. But the money goes into REAL r&d that makes my sysAdmin at home and work so much easier. From time to time I get a hack attempt. But my mac is set up as an Win2K ActiveDirectory PDC and my logs keep me laughing. I hardly even boot my PC as it would be a real security risk
    So before you bash the OS the real question is do you run it. And if not when was the last time you were really happy with your OS
    -- P.S.> I will not go to Server 10.3 as I already implemented all of the documented features by 05/2003

    --
    --Shaddup and support your local PBS station Plan for it
  46. Mac security needs to be taken seriously by Anonymous Coward · · Score: 0

    There are after all literally hundreds, maybe thousands of Macs on the Internet these days. Imagine if a significant portion of them were compromised. The ensuing chaos would be a huge problem for Mac and Windows users alike.

    1. Re:Mac security needs to be taken seriously by oscast · · Score: 1

      hundreds or thousands?

    2. Re:Mac security needs to be taken seriously by Anonymous Coward · · Score: 0

      I've heard estimates in the thousands, but I'm not entirely convinced there are that many yet.

    3. Re:Mac security needs to be taken seriously by oscast · · Score: 1

      As long as we're trolling... why not just say 10s?

    4. Re:Mac security needs to be taken seriously by Anonymous Coward · · Score: 0

      actually i was giving my estimates in binary.

  47. Re:hes totally wrong by Anonymous Coward · · Score: 1, Insightful

    Sorry, but that's a bug. It should error. Not failing (or at least indicating) the flaw is wrong.

    Look at all the security holes because IE tries to "help" you with the type of a file.

  48. My sepll chekcer is broken :) by Mr.+Sane · · Score: 1

    However, Solairs is a fantastic car... food... er... movie.

  49. Re:Don't always assume a smear campaing by anachattak · · Score: 1, Interesting
    The author of the rebuttal article completely missed the point (or just wanted an excuse to make another Mac v. Windows comparison).

    Alright, just so I don't get dubbed Troll by any Mac Fan(atic)s out there - THIS IS NOT A DEFENSE OF THE WINDOWS OPERATING SYSTEM OR A COMPARISON BETWEEN THE MAC OS AND WINDOWS. If you read Lance's original article, it's not saying "Windows rule, Macs drool" on the basis of the security flaw he mentions. It's about something bigger, which is an underlying issue in the Mac community: fixation on image.

    No serious, knowledgeable Mac user is going to sit down and tell you that "their" OS is descended from heaven, perfect and secure in every facet. Albeit, it's a LOT better than Windows, but it's got a couple issues of its own. But I know a lot of guys who bought Macs because "My old computer got a virus, and a guy told me Macs don't get viruses" or "I don't know anything about computers, but I want something that can't break." These guys need to read Lance's article because Macs CAN get viruses and do have the occasional security holes (though still nothing like Windows, but again THIS IS NOT A COMPARISON).

    For the educated Mac user, Lance's article was "much ado about nothing." But there is a faction in the Mac community which claims that they know their OS is not invulnerable, but any criticism or discussion of a flaw results in personal attacks against the original author, their OS, their family, friends and pets, followed by an extensive feature-by-feature OS comparison. For these people, the security of the Mac OS has not been attacked; instead, their worth as individuals has been smeared (by means of their personal investment of self-worth in the Mac "image").

    Long story short - I think the rebuttal was over the top and completely missed the point. But it nicely drew attention to a real problem: the Mac community needs to do something about the association of the Mac "image" with the identities of Mac users.

  50. Reply to rebuttal by Micro$will · · Score: 3, Funny

    To: Richard Forno
    From: Lance Ulanoff
    Subject: Re: Mac Security

    YHL YHBT HAND

  51. Re:Audit. WAS: Re:trust by rwven · · Score: 1

    my point is kinda the lesser of two evils. who do you trust the most. and that is ALWAYS laced with your own resposibility. if you hire a body guard and trust him to protect you then you had better remember to pay him his wages. just as you'd better remember to keep an eye on everything and make sure everything is up to date...

  52. Re:Here We Go Again ... by Anonymous Coward · · Score: 0

    large numbers of Apple users do tend to fall into the moronic zealot category - see Slashdot for examples.

    That would be the 'Linux' example eh?

  53. story NOT and editorial by acomj · · Score: 1

    News stories are supposed to be based on fact, or have factual content (not that there is ever completely bias free journalism). Editorials are bassed on opinion.

    Unfortunetly the orignal story was an editorial, but not presented as such.

  54. Re:Can't beat BSD! by Anonymous Coward · · Score: 0

    And $89 Windows upgrades every three years!

  55. Re: DLL Hell by Anonymous Coward · · Score: 2, Insightful

    You're confusing Microsoft propaganda ("we fixed DLL Hell!") with reality.

    The reality is that new applications written specifically for .NET may manage to avoid most of DLL Hell (except for all the caveats like ADO problems), but this is of limited help with the existing DLL hell (eg, shell versions, which is a problem noone can fix but Microsoft, and they lack the money and incentive).

  56. I subscribe to PC Mag by harborpirate · · Score: 1, Insightful

    And I read the original article in the magazine when I got it. Contrary to the rebutters opinion, I did't see the article as "muckraking". The author may not be as well informed as he should be. Pointing out that a simple firewall is enabled by default and that changing system settings is more difficult in Mac OS X would have gone a long way toward mitigating this kind of response, but certainly would not have eliminated it. I get the feeling that merely suggesting that Mac OS X feels less pain from viruses, trojans, and other nasties in part because it has a smaller market share would result in this sort of response regardless of how well informed the journalist was about Macs.

    I think the author of the original commentary article, Lance Ulanoff, is at least partially correct. I've seen other posts in this article thread stating that "security through obscurity doesn't work". Actually, it does, until the vulnerability is discovered. Does Mac OS X have undiscovered vulnerablities? I can almost assure you it does. No programmer, no matter how intelligent, can ever come up with every sneaky, crafty, or just odd tactic that crackers will try.

    So is Mac OS X less of a target because of smaller market share? Yes.
    Is Mac OS X more secure in a default configuration that Windows XP? Yes.

    Its really pretty simple when you look at it objectively. I maintain that if you have a normal doofus user setting up an OS, you have an unsecure OS, Windows or not.

    --
    // harborpirate
    // Slashbots off the starboard bow!
  57. It's Odd by killmeplease · · Score: 0

    It is odd that a writer would make comparisons between OS X and Windows. I seem to remember the worlds computer systems grinding to a halt a few months ago due to Windows only worms, including Fortune 500 Companies, Government networks, and thousands of small businesses. In total I bet these worms cost the United States alone $10 billion in lost productivity and computer repair costs. Now I seem to forget the last time Macintosh had any sever problems that affected anyone seriously. I know this is flamebait for you Windows fans that disregard the Windows worms like it was all a haulocause type conspiracy to make light of your beloved Windows. To all those conspiracy theorists out there, I love you man.

    --
    - Kill Yourself, spare us all! -
    1. Re:It's Odd by E-Rock · · Score: 1

      We disregard them becuase it was administrative negligance that was the biggest factor in the event. When you're told a couple months in advance that there's a remote compromise that will allow an attacker to install software as admin/root, you patch the damn computers, or put up a firewall, or something other than just leave them out there connected to the network.
      When you don't, you get laughed at when you get hacked. Works for any OS.

  58. Neither have I by Anonymous Coward · · Score: 0

    -----BEGIN PGP SIGNED MESSAGE-----
    Hash: SHA1

    As one of the local Network specialists at Macbidouille, I have never heard of a single rooted Mac user, even though a number came and alarmingly asked about strange network behaviour, when all they really had was ISP DNS problems or firewall misconfiguration.

    There's also the casual shot at Mac antivirus software that only have definitions for PC-specific viruses.

    And IIRC the recent ssh vulnerabilities did not affect Mac OS X (they affected OpenSSH 3.7 and 3.7.1, not the version provided by Apple).
    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.2.3 (Darwin)

    iD8DBQE/3hkF76Zattu5F5URAqV/AJ4rovUhMjucZ1dZTKjc mq hbDcPqxQCfVsp+
    pTy2e+aiWuwkaIFRkrOaErM=
    =zAhE
    - ----END PGP SIGNATURE-----

    1. Re:Neither have I by radio4fan · · Score: 1

      by Anonymous Coward [...]
      -----BEGIN PGP SIGNED MESSAGE-----


      You post as AC, and sign it?

      You've gotta stop smoking that stuff during the day...
    2. Re:Neither have I by Anonymous Coward · · Score: 0

      Got to make sure it really [i]is[/i] ac, right?
      -AC

  59. Not a fair comparison by andman42 · · Score: 3, Interesting

    Ironically, despite a few hiccups along the way, it's becoming clear that Mac OS, not Windows, epitomizes Microsoft's new mantra of "secure by design, default, and deployment."

    That is true, right now, but it is not a fair comparison.

    Look, I'm no MS fan, but they have not released an operating system since they started their "trustworthy" initiative. The Windows operating systems being discussed are old (WinXP came out in 2001), and obviously full of holes--so full of holes that MS had to start this whole focus on security.

    So comparing anything to an admittedly weak and insecure operating system is just plain silly. Everyone knows Windows is insecure. Saying MacOSX is more secure than Windows means nothing, and in fact makes OSX security look comparable to that of Windows when in fact it is far better (regardless of what that PCMagazine moron wants to believe).

    So, how about we give MS a chance and at least wait for them to release an OS under their "secure by design, default, and deployment" banner before we start ripping it. We may be pleasantly surprised (although I doubt it).

    1. Re:Not a fair comparison by danigiri · · Score: 5, Insightful
      Look, I'm no MS fan, but they have not released an operating system since they started their "trustworthy" initiative. The Windows operating systems being discussed are old (WinXP came out in 2001), and obviously full of holes--so full of holes that MS had to start this whole focus on security.

      XP might be old, but it is what people are allowed to buy *now*, so your point does not apply. It is insecure *now* and it is being sold *now* (read, not discontinued or the like).

      So, how about we give MS a chance and at least wait for them to release an OS under their "secure by design, default, and deployment" banner before we start ripping it. We may be pleasantly surprised (although I doubt it).

      I have just installed a network of computers, loaded with MS software I just bought. I need to be secure now, not in 2-3 years time.

      dani++

    2. Re:Not a fair comparison by Keeper · · Score: 1

      Win2k3 was released after the trustworth computing initiative.

    3. Re:Not a fair comparison by RogerWilco · · Score: 1

      If XP is so old, then you must have been running Longhorn for about 4-5 years now I suppose? I would not call something old, if it was the newest thing I could buy.
      MS has had the same amount of time as Apple, IBM, or Linus to create and release a secure OS. It's not like they didn't have any resources or did not know security was important before 2001.
      I liked the analogy somebody else made with shipbuilding. I think MS could be seen as a speedboat builder that finds again and again that a speedboat of half a mile long might still be faster as a super tanker, but is nowhere near as secure as it's compartimented double walled counterpart. It will probably crash more often too.
      I know this analogy flawed but I like the picture, oh and I know little about boat building...

      --
      RogerWilco the Adventurous Janitor
    4. Re:Not a fair comparison by Anonymous Coward · · Score: 0
      I have just installed a network of computers, loaded with MS software I just bought. I need to be secure now, not in 2-3 years time.

      "I just jumped out of a plane without a parachute. I need to learn how to fly like right now!"

      Well, that's the nature of free will. It's really tough that people make expensive choices sometimes. Maybe you'll get lucky on the way down.

      Actually, you are lucky. It's still not too late to write off your mistake and switch to something more secure. You have a number of excellent options that will preserve your infrastructure investment: Linux, Solaris, and BSD are all very well engineered and well supported. They're all available now for the same hardware that runs Microsoft products, they're significantly more secure and they're also much less expensive.

      You certainly don't have to pray for Microsoft to get their act together. Based on their track record, you could be waiting a long, long time before that happens.
  60. Re:Don't always assume a smear campaing by Anonymous Coward · · Score: 0

    You expect anything different when the Macintosh is involved? :)

  61. Yeah yeah. by mindstrm · · Score: 5, Informative

    My summary of the situation:

    - Nothing is totally secure, if it's at all useful.

    - Windows is demonstrably NOT secure. IT's been riddled with nasty bugs for years.. and for Joe Average, WHY doesn't matter.

    - OS X is without question far more secure than windows, and less buggy. That is not to say it's immune, or that it can't be hurt ever, but several factors both in low-level design, and in user interface design, specifically how easily users can turn on and off certain services, makes it less prone to exploits.

    - Yes, it has a smaller market share, and hence, less attention is focused on it, and that certainly IS a factor.. but it doesn't change the fact that mac users don't have to worry about viruses on a dialy basis at the moment. It also isn't the only factor, and hardly means "Oh it's just as insecure as windows"

    The #1 insecurities in windows are related to bad design... and a narrow interpretation of how the computer will be used in a network environment. Having all these services listening by default is bad. Having them difficult to shut off is even worse.

  62. Re:Here We Go Again ... by Anonymous Coward · · Score: 0

    Yeah, that's true, but he's not very smart at all.

  63. Please mod parent UP by Anonymous Coward · · Score: 0

    The provided blog entry is very interesting. Author cites relevant RFCs, great stuff. Miles from the bullshit the PC-Magazine idiot is saying.

  64. Re:THINK. by Anonymous Coward · · Score: 0
    And don't forget how much attention you'll get.

    For a moment everybody in America will know about you.

  65. Re:Don't always assume a smear campaing by kisrael · · Score: 2, Insightful

    Yes, actually the ending sentence that comes right after that
    Hmm. Suddenly it's gotten pretty quiet around here.
    REALLY got on my nerves. Anyone who declares victory at the end of their own damn article...

    and hell, Windows is the only OS I use on a daily basis, other than some Usenet in a Unix shell account.

    --
    SO YOU'RE GOING TO DIE: The Comic for Dealing with Death
  66. Who is uninformed by Foolhardy · · Score: 1
    The real security wisdom of Mac OS lies in its internal architecture and how the operating system works and interacts with applications. It's also something Microsoft unfortunately can't accomplish without a complete re-write of the Windows software -- starting with ripping out the bug-riddled Internet Explorer that serves as the Windows version of "Finder." (That alone would seriously improve Windows security, methinks.)
    What does explorer's search have to do with security? How is it insecure?

    Next paragraph, he complains that Windows's out-of-the box config (leaving so many things running) is bad. I agree. MS is improving in that area; WS2k3 is much better. Not being able to stop/disable RPC is an issue, however. I don't know what's so hard about disabling services anyway. You can even do it from the command line; just tell users to go Start->Run and type "sc stop messenger" to stop messenger, and "sc config messenger start= disabled" to disable it.

    The next paragraph about installation is bogus. It is crappy installation programs that overwrite system files, and system file protection (min win2k) makes it a non-issue. I wish there was an example of a patch doing all of those things to configuration, since I don't know what he is talking about.

    Don't like media player? Don't use it. There are plenty of alternatives; I recommend Winamp 2.

    Many of the security concerns he points out are easily remidied by not running everything under admin, or at least avoiding crapware.
    Unlike Windows, Mac OS X requires an administrator password to change certain configurations, run the system updater, and when installing new software. From a security perspective, this is another example of how Apple takes a proactive approach to system-level security. If a virus, remote hacker, or co-worker tries to install or reconfigure something on the system, they're stymied without knowing the administrator's password stored in the hardened System Keychain.
    What do you mean, unlike Windows? You have to be an admin to install mostly anything, or change most computer settings on Windows.

    I used the app access control panel in Windows to use Mozilla, and it works fine. There is nothing forcing you to use MS Media Player, Outlook Express, or IE for the internet. It IS more work to use a different shell than explorer (which uses IE a lot), but there are alternatives to that too.

    Yes, 'Trustworthy Computing' is a thin marketing slogan, but the issues the author tries to bring up are a combination of unsubstantiated and easy to work around.
    1. Re:Who is uninformed by jhurshman · · Score: 2, Insightful
      The real security wisdom of Mac OS lies in its internal architecture and how the operating system works and interacts with applications. It's also something Microsoft unfortunately can't accomplish without a complete re-write of the Windows software -- starting with ripping out the bug-riddled Internet Explorer that serves as the Windows version of "Finder." (That alone would seriously improve Windows security, methinks.)
      What does explorer's search have to do with security? How is it insecure?
      The OS X Finder is not the equivalent of Explorer's search. It is the equivalent of Explorer. Yes, the "Finder" name is somewhat of a misnomer, though file searching is part of the Finder's capability. So the original author is not saying to rip out Explorer's search capability, he's saying rip out Explorer completely.
      I don't know what's so hard about disabling services anyway. You can even do it from the command line; just tell users to go Start->Run and type "sc stop messenger" to stop messenger, and "sc config messenger start= disabled" to disable it.
      "Hard" could mean complicated or involving many steps. I agree going to Start->Run and typing "sc stop messenger" isn't hard in that sense. However, "hard" could mean unintuitive and unlikely to be discovered by the average user within his own lifetime, let alone the lifetime of his computer. I think that's the relevant sense here.
      --

      Do not speak unless you can improve on the silence.
    2. Re:Who is uninformed by gregsv · · Score: 1

      Unlike Windows, Mac OS X requires an administrator password to change certain configurations, run the system updater, and when installing new software. From a security perspective, this is another example of how Apple takes a proactive approach to system-level security. If a virus, remote hacker, or co-worker tries to install or reconfigure something on the system, they're stymied without knowing the administrator's password stored in the hardened System Keychain.

      What do you mean, unlike Windows? You have to be an admin to install mostly anything, or change most computer settings on Windows.


      That is true, except the default Windows configuration is to automatically log on as the administrative user with no password when the system is booted up.

    3. Re:Who is uninformed by Anonymous Coward · · Score: 0
      "What do you mean, unlike Windows? You have to be an admin to install mostly anything, or change most computer settings on Windows."

      Or say ... run anything. The "User" level is useless and runs little software and the "Power User" while somewhat better has several problems in using MS Office (win2000) and other common software. Now not all of these are in MS programs but as a result of auto logging in as an admin (and creating all of the setup users or upgraded users as admins )on XP Home this kind of sloppy coding "works" and is considered OK. Even the brief for this kb article is insane:
      (293834) - After you install Windows XP, you have the option to create user accounts. If you create user accounts, by default, they will have an account type of Administrator with no password.
    4. Re:Who is uninformed by Foolhardy · · Score: 1
      I can get all kinds of stuff to run. Including Office. Usually, MS programs are better behaved than average. Still, you are right in saying that many things require more priviliges than they should need to run. I guess this is a more fundamental difference in the coding ideologies between UNIX and Windows. Many Windows programs implicitly require access to everything, whereas UNIX programs are usually better behaved.

      To work around this, I recommend you download "su/sud" by Didier Cassereau. You can get it at http://www.loa.espci.fr/winnt/.
      Then create a cheapo cmd script: call it suaa.cmd (for Switch User to Administrator Auto), use SU with an administrator's name and password, running the desired program.
      su -u Admin -p 123 -c %1
      exit
      Change the shortcuts of picky programs to "suaa.cmd X" where X is the program name. NOTE: if the command line includes any parameters or spaces, be sure to enclose it in quotes.
      Granted, this breaks the machine's security against malicious users, but you can at least avoid running Internet Explorer as an administrator. You can go the other way too: su also works for normal users.
  67. Re:Here We Go Again ... by Anonymous Coward · · Score: 0

    Thanks for proving my point guys.

  68. This guy?! by SendBot · · Score: 0, Insightful

    Richard Forno is a security technologist, author, and the former Chief Security Officer at Network Solutions.

    Remember when everyone's domains (including aol.com) were getting hijacked because the default security was so laughable? (sarcasm)Network Solutions, now there's some credentials.

    1. Re:This guy?! by Gumber · · Score: 1

      Before you smear him, perhaps you should figure out whether he was the CSO during the period you cite.

    2. Re:This guy?! by Anonymous Coward · · Score: 0

      Maybe you should check to see if he was able to make a difference in security of the domain names. For all we know he was like a typical CSO whose focus is internal-only, and has little influence on products or services his company sells.

  69. Mac Zealots or AnitMac Zealots by Salvo · · Score: 5, Insightful

    I recently switched to MacOSX from BeOS. In my experience chatting to the Mac Community out there, they are not more fanatical than Any other Community. I've know Car Clubs who are more obsessive than the Macintosh Community.

    The only fanatics I've ran accross in the MacOSX World are the AntiMac Fanatics. For whatever reason, these individuals *hate* Macs. Not just Dislike Macs, but actively *hate* them, with a passion remeniscant of Religious Fundamentalists.

    People who rebute these AntiMac Fanatics are Labeled Mac Zealots. This is only a half truth, they are really just qualifiers of the AntiMac FUD.

    Anti-OS sentiments aren't restricted to MacOS, though, There are plenty of AntiMS, AntiLinux, AntiBSD and Anti[insert favourite OS here] Fanatics. Are you one of them?

    1. Re:Mac Zealots or AnitMac Zealots by Anonymous Coward · · Score: 0
      I recently switched to MacOSX from BeOS. In my experience chatting to the Mac Community out there, they are not more fanatical than Any other Community.
      Well, yes, provided that 'Any other Community' is comprised of BeOS zealots.
    2. Re:Mac Zealots or AnitMac Zealots by Anonymous Coward · · Score: 0

      "Anti-OS sentiments aren't restricted to MacOS, though, There are plenty of AntiMS, AntiLinux, AntiBSD and Anti[insert favourite OS here] Fanatics. Are you one of them?"

      Yup, I'm AntiMS. Not sure how one could become anti any of the others, but AntiMS is easy. You just need to have used windows for years before escaping to something better. People who have used *NIX for years and years with limited exposure to windows don't seem to develop the same hatred for it.

    3. Re:Mac Zealots or AnitMac Zealots by Anonymous Coward · · Score: 0

      Ahahahaa!

      Okay, I really like Mac OS X and own a couple macs.

      But I nearly can't believe the flaming pro-Mac fanatics I've seen on Mac sites in particular. I mean, if you dare to even point out how Apple could've done something better you'll get scorched. For examples, see comments at MacSlash or the comments in stories at MacNN. Okay, I haven't linked to any specific examples, but look someday when someone says something negative about a Mac, take a look!

    4. Re:Mac Zealots or AnitMac Zealots by Anonymous Coward · · Score: 0

      I frequent Mac sites...most people that use the Mac are very critical of Apple almost to the point of being annoying...that said it's a mixed bag, just like the real world. What I can't understand for the life of me is why someone that has never used a Mac & obviously never will goes to a site such as Maccentral & esposes total nonsense on a constant basis. I've used Windows...I prefer the Mac. I don't waste my time going to Windows Bulletin boards to point out my hatred for MS. What kind of special loser do you have to be to do that. Use what you prefer.

    5. Re:Mac Zealots or AnitMac Zealots by 4521red · · Score: 1

      About ten or 15 yrs ago there was an excellent article by Italo Calvino in either Harper's or The Atlantic in which he compared the Mac vs. Windows thing to religion. He made a case for the Mac side as Catholic and the Windows side as Protestant. Aside from the fact that I'm a card-carrying atheist and it smarted a tiny bit being thought of as Catholic, it was a beautiful article. Anyway, it does remind one of fundamentalism. Tiresome, isn't it?

  70. Re:hi people. by Anonymous Coward · · Score: 0
    I don't know if your serious or not, but in case you are I'm going to give an honest response. Jr. High sucked and High school was total hell for me. My freshmen year was by far the worst year of my life. I used to get teased and hit/kicked once or twice a week. The school I went to didn't give a fuck. They had worse problems with drugs and gangs. I wanted to kick the shit out of all of them. I wanted to make them pay for what they had done. I wanted to teach them a lesson that they'd never forget. You're not alone in your feelings. But I never acted upon my emotions and I'm very glad that I never did.

    The thing is once I finished high school and got into college everything changed. I met people who actually understood me and were like me. No one made fun of me being a nerd, hell everyone was a nerd. I was actually happy.

    Some of us have very rough times in school. Ignoring people is very hard and how to deal with what's going on really depends on a case to case basis. Sometimes you just need to find the right group of people. Some of the funest, and most accepting people that you'll ever meet are theatre geeks. It would help if you could give a few more details about what's really going on.

    But using a gun would be a MISTAKE. This will not make things better, it will only make it worse. You'll spend the rest of your life in jail around people who are far, far worse then what you get in school. Absolutely nothing positive will come from physical violence at a school setting.

    Trust me, these people will pay eventually. After 10 years of doing labor or working retail they'll maybe making 25 or 30k. You'll be making much more living in a lifestyle that they can only dream about. Even when the economy is down nerds make more money, because we can do more.

    Plus, some of them will change. I've had a couple of people tell me how sorry they were for how they treated me when I was younger. If you're serious reply to this post with more info. We'll help you through this. Things will get better. DO NOT RESORT TO VIOLENCE.

  71. So blown out of proportion ... by Zwoop · · Score: 5, Informative
    I still don't understand why this security "hole" got so much attention... Are people struggling to find problems with MacOSX? First of all, attacks like this is nothing new, just remember the old YP/NIS problems with broadcasting for the server, to mention just one example.

    Secondly, when we wrote the DHCP LDAP option specs way back when, we explicitly documented this problem in the security section:

    5. Security considerations

    Security considerations discussed in [3], particularly with respect to the
    provision of authentication information, are directly applicable here.
    Additionally, it should be noted that providing LDAP server information by
    a broadcast protocol such as DHCP may allow unauthorized clients to learn
    the location of and authentication information for LDAP servers and hence
    pose as valid clients. This presents a security problem when sensitive
    information, such as user passwords, is published via LDAP servers.

    The DHCP protocol provides no mechanisms for the client to verify the
    validity and correctness of the received information. The security
    considerations in [1] discuss several weaknesses, particularly the problem
    with unauthorized DHCP servers.


    This was written in 1997, note the last paragraph above. These issues has been discusses and documented in several RFCs, many years ago...

    -- Leif
    1. Re:So blown out of proportion ... by rjung2k · · Score: 1

      Are people struggling to find problems with MacOSX?

      Absolutely.

    2. Re:So blown out of proportion ... by Anonymous Coward · · Score: 0

      It's good to see this analysis.

      You're right that broadcasting for services entails identity issues in general. We're not all that far away from accepting the need for all network entities to carry certificates as a matter of course.

      The broadcast issue is especially on people's minds these days as we try to generalize the network to support mobility. Here it's obvious that authentication has to come first, even before routing. But as we see with DHCP, it makes sense on a static network also.

      Dan Harkins at Trapeze is a really good person to talk with about this.

  72. Re:hes totally wrong by Perl-Pusher · · Score: 2, Insightful
    Cant count the times netwcape bombs because there is an unclosed table in 500 lines of html

    If it happens that often maybe you should stop reading slashdot and concentrate more on doing your job correctly!

  73. Reply if OXS Could Outsell Windows on x86 by Bruha · · Score: 0, Offtopic

    I've heard that Apple runs a x86 version that's parrallel to the current releases just in case they were to switch platforms someday. I would definately pay for OSX but I want to use my normal hardware. And I think Apple could even sell it and driver manufacturers would support it. ATI would have little trouble supporting the rest of their cards and many of them are mac compatible already.

    APPLE Please get a clue you could tromp all over MS any day with our OS!!!

    1. Re:Reply if OXS Could Outsell Windows on x86 by lrucker · · Score: 0, Offtopic

      There was an x86 version of NeXT, but there is no x86 version of OS X.

    2. Re:Reply if OXS Could Outsell Windows on x86 by piobair · · Score: 0, Offtopic

      The real reason apple pulled rhapsody off the market(the x86 pre-cursor to OSX) was fear of MS pulling office apps.

      --
      I have a second sig, I call it sig#2.
  74. Re:Don't always assume a smear campaing by Anonymous Coward · · Score: 1, Insightful

    This and other statements like it definitely tinted it from simple reporting to an apparent attack, complete with the subliminal childish prat-calls.

    Made it onto slashdot, didn't it? I'd say the tactic worked.

  75. MOD Parent Up! by Perl-Pusher · · Score: 1

    Congradulations! Unlike some other here, you actually read the articles before posting.

  76. How many will read the rebuttal? by psychogentoo · · Score: 1
    I'm going to wager that more general computer users will have read the Lance Ulanoff article than the rebuttal. This in their minds will probably confirm what what they already believe in or don't care cuz they can "do email or internet".

    I think in order to educate the general users, such a rebuttal should be printed in the pages of which the original article was published on (pcmag). Maybe letters to the Editor?

    But on the other hand, if someone writes an article saying how great it is to live in a sewer and you happen to live in a sewer you'd prolly feel good about your living situation. The writer of this article will probably argue that houses can have backed up toilets and so a house is just as stinky as a sewer.

    If Lance wants to live in the sewer, let him write about it and feel good about his situation.

  77. Interesting by M.C.+Hampster · · Score: 1

    From the article:

    It's also something Microsoft unfortunately can't accomplish without a complete re-write of the Windows software

    Hmm, when I read this, I was intrigued and excited to see what the author had in mind. He then listed the following security differences:

    • Windows comes with many services on by default.
    • DLL Hell
    • Mess ups with the patching system (turning VBA back on, etc.)
    • Pushed DRM
    • Trusted interdependencies
    • Windows Media Player, IE, etc. being bundled and tied in with the OS

    Hmm, so which of these would require the "complete re-write" as the author claimed? None. Just about every service is turned off by default in newer versions of Windows. The newest version of IIS will not have to run as Administrator to work properly. DLL Hell has nothing to do with security, so I'm not sure why he went off on that tangent. Plus, the issue has been resolved nicely on WinXP for the most part. Plus, as more applications moved to managed code, it won't be an issue. Mess ups with the patching have nothing to do with the internals of the OS. DRM is another tangent he goes off on that has nothing to do with security. The interdependencies and tying together of Windows Media, etc. is just about the only point he really makes. Again though, this isn't an issue with the internals of the OS that would require a complete rewrite of the OS.

    Ultimately, I have a feeling that the author knows very little about the internals of the Windows OS. Claiming that a complete rewrite is the only way to secure Windows is a laughable claim that reveals him to be quite ignorant.

    --
    Forget the whales - save the babies.
    1. Re:Interesting by Wumpus · · Score: 2, Informative

      While I agree that the author is poorly informed and mostly goes on one tangent after the other in this article, there are some problems with Windows that aren't easily fixed. This page, mentioned previously on /., is one example:

      http://security.tombom.co.uk/shatter.html

      There is a followup to this paper that discusses Microsoft response the it. The author isn't happy with the response.

      The root of this issue is the Win32 API, and its origins as a real mode compatible API with no security, and no memory protection between processes. Much of the transition to Win32 seems to have been handled as a massive search and replace operation on the Windows headers, with backwards compatibility being considered more important than security.

    2. Re:Interesting by M.C.+Hampster · · Score: 1

      I've already seen this paper before and it is bogus.

      Ultimately, he is exploiting a "weakness" in Windows by sending window messages to an application that is running as a Windows Service (think deamon). Problem is, Windows Services should not create windows at all. The point of a Windows Service is to have something that is not running interactively. Norton created a very badly architected Windows application and this guy is taking advantage of it. It is not a weakness in Windows.

      If you want to interact with a Windows service, you need to architect the application as such that it does not directly create Windows, but instead communicates with an application through some sort of interprocess mechanism.

      As for the issue of memory protection between processes, what are you refering to? Processes cannot access each others memory, and if they do, it causes an illegal operation.

      --
      Forget the whales - save the babies.
    3. Re:Interesting by Wumpus · · Score: 2, Informative
      Have you read the followup? The author claims to have exploited similar weaknesses in MS software. You're right that Norton shouldn't have architected their application the way they did, but other people make the same mistake, Microsoft included.
      As for the issue of memory protection between processes, what are you refering to?

      I was refering to the old 16 bit Windows API, which the Win32 API is based on. My original post was phrased rather poorly - sorry.

      Win32's roots in the 16 bit Windows API are the reason why the class of problems described in the paper I mentioned exist - applications used to be able to pass pointers around like cookies (Microsoft's words - not mine), and that includes pointers to timer callbacks. You can still get an application to map your data (potentially, exploit code) into its virtual memory space by sending it a WM_COPYDATA message. This was done, I assume, to make it easier to port applications that relied on the lack of memory protection to the new Win32 API.
    4. Re:Interesting by Anonymous Coward · · Score: 0

      -Trusted interdependencies
      -Windows Media Player, IE, etc. being bundled and tied in with the OS

      Actually, those two parts would require rewriting the OS, according to Microsoft. At least, that's what they told the anti-trust commission before Felton proved them wrong.

    5. Re:Interesting by M.C.+Hampster · · Score: 1

      Have you read the followup? The author claims to have exploited similar weaknesses in MS software.

      Hmm, no I hadn't read the follow-up. Obviously Microsoft not following their own security policies isn't rare. :-)

      I guess one could make the point that the window messaging architecture of Windows makes it more difficult to write secure applications, but that doesn't mean it can't be done. I certaintly don't agree that it requires a rewrite of the OS to fix.

      --
      Forget the whales - save the babies.
    6. Re:Interesting by M.C.+Hampster · · Score: 1

      Actually, those two parts would require rewriting the OS, according to Microsoft. At least, that's what they told the anti-trust commission before Felton proved them wrong.

      What I'm saying is that fixing the security problems with WMP and IE doesn't require a complete rewrite of the OS.

      --
      Forget the whales - save the babies.
    7. Re:Interesting by Wumpus · · Score: 1
      I certaintly don't agree that it requires a rewrite of the OS to fix.

      Theoretically, a change to the Win32 API at that level would require sweeping changes to every part of the OS, and to every Windows application ever written. Microsoft can certainly start patching the API when people find problems, but they can't realistically make any changes that are not backwards compatible. Would such a change amount to rewriting the OS? No, not literally, but in terms of the work involved it might get close.

      This is all moot, because it'll never happen.
    8. Re:Interesting by EddWo · · Score: 1

      The WM_Timer exploit was patched a long time ago. This is no longer an issue.

      http://www.microsoft.com/technet/security/bullet in /MS02-071.asp

      In any case Windows Messages are only part of Win32 and not part of the NT kernel.
      NT was originally designed to be API independant it was to support OS/2 and also Posix APIs as well as Windows.
      The various supported APIs are built as layers on top of the NT executive. Fixing or even replacing Win32 would not require rewriting the kernel.

      With Longhorn the primary API for Windows is transitioning away from Win32 to the managed WinFX. This will be a much more code level security and Windows Messages will no longer exist in their current form.

      Win32 will of course still exist for compatibility but it will be increasingly sandboxed as WinFX based applications are created to replace their Win32 versions. Every application installed will be rated on trust with Unmanaged legacy apps automatically gaining a low trust score so the User is warned before running them.

      --
      "Taligent is still pure vapor. Maybe they'll be the last who jumps up on Openstep... "
    9. Re:Interesting by Wumpus · · Score: 1
      The WM_Timer exploit was patched a long time ago. This is no longer an issue.

      The paper I linked to has a followup where the author claims the WM_TIMER was only one facet of a deeper problem. He claims to have found numerous other exploitable problems that weren't fixed by Microsoft.
      In any case Windows Messages are only part of Win32 and not part of the NT kernel.

      Arguing that the NT kernel is meaningless, unless you can show me how to install a usable NT kernel without Win32 support. Also, the fact that Microsoft is finally shipping a safer API won't change anything if they won't stop shipping Win32, which they won't for a very long time.

      In any case, the architecture you're describing is obsolete - Since NT 4.0, Microsoft has been pulling Win32 components into the kernel.

      I don't see how Win32 can be "increasingly sandboxed" in the way you're describing. Unless you're suggesting that WinFX is going to be sitting directly on top of the NT kernel in Longhorn, and Win32 is going to be an optional subsystem, I don't see how this problem is going to be solved any time soon.
    10. Re:Interesting by EddWo · · Score: 1

      Well programs can still send messages to other programs, the software for my IR remote sends WM_Command messages to cause actions in my DVD software. But the difference is that it doesn't start the program executing arbitrary code. The WM_Timer basically told the program to jump to a pointer given in the message, most other callback messages can only start executing at a point predefined by that process.

      A full solution is to make sure all the apps that present interfaces on the desktop only run at the same privelege level as the user. Microsoft may be guilty of breaking that rule themselves, but fixing it does not require a rewrite of the kernel.

      IFAIK they made things like GDI and User32 run in kernel space for performance reasons, not changing the kernel executive itself. I'm not saying it was a good idea for stability but I don't think the kernel relies on those componants being there.

      No at the moment you can't install NT on its own, though there are some programs that are written against NT rather than Win32. But the point is that whatever problems there are presently in windows, the solution does not require rewriting everything from scratch.

      Why can't Win32 be sandboxed? They put DOS apps into NTVDM, Win16 apps run in wowexec, why not run Win32 in a layer of its own? Mac did it with classic.

      It can't happen all at once, theres too much legacy stuff to support, but once a critcal mass of WinFX apps exist Win32 can be relagated to just another subsystem.

      --
      "Taligent is still pure vapor. Maybe they'll be the last who jumps up on Openstep... "
    11. Re:Interesting by Wumpus · · Score: 1
      most other callback messages can only start executing at a point predefined by that process.

      You said it yourself - most. The guy who found the WM_TIMER exploit claims there's more along those lines that he was able to exploit. I remember that there were other similar messages, but I don't remember the specifics. It's been years since I've done anything serious with Win32.
      Why can't Win32 be sandboxed? They put DOS apps into NTVDM, Win16 apps run in wowexec, why not run Win32 in a layer of its own? Mac did it with classic.

      Of course they can, but that would amount to rewriting the OS (the OS is more than just the kernel), because much of the OS talks to Win32, and that would have to change. Your example illustrates this - Apple sandboxed classic, but it paid the price - they did rewrite the OS.

      Also, I'm not sure that "sandboxing" Win16 and DOS was the proper term. They provided the ABI required by those apps, but didn't do much in the way of securing them, and trapping attempts to compromise the system. This wasn't a sandbox in the sense that the JVM is a sandbox, for example.
      But the point is that whatever problems there are presently in windows, the solution does not require rewriting everything from scratch.

      Literally, you're right - nothing ever requires reqriting "everything" from scratch. You can always reuse bits and pieces, at the very least. But the fact is that you're describing Microsoft's effort to rearchitect Windows in a way that amounts to a rewrite, in the sense that it'll take years, a lot of effort, and a great risk.
  78. Re:Is my computer posessed by Anonymous Coward · · Score: 0

    > Is my computer possessed?

    yes.

  79. Here by plj · · Score: 1

    The one slide that describes everything is available here. ;-)

    (Converted to PDF, though. Distributed under these terms.)

    --
    “Wait for Hurd if you want something real” –Linus
  80. Re:Is my computer posessed by Anonymous Coward · · Score: 0

    No, you just chose a shitty OS.

  81. OSX is weak - here is some homework. by emil · · Score: 0, Troll

    Execute the following in a terminal on your OSX system, and you will see:

    % ls -ld /
    drwxrwxr-t 29 root admin 986 Dec 11 16:25 /

    At least on 10.2, the root directory is writable by the admin group.

    Furthermore, when the OSX installer creates the first user on the system, this user is automatically added to said admin group. This means that a Joe Blow (l)user can write to the root directory (bearing the sticky bit limitations in mind).

    Apple has circumvented the traditional UNIX security mechanisms, and added this "admin" functionality that really doesn't fit within the BSD environment. UNIX has already been vulnerable to an avalanche of buffer overflow vulnerabilities over the years; weakening a security model that has already had significant difficulties is a questionable practice.

    Apple's policies on OS upgrades and patches are also not entirely to my liking.

    Personally, I would avoid OSX on a critical system. Sun would be roasted alive if they tried something like a writable root directory in Solaris.

    1. Re:OSX is weak - here is some homework. by phliar · · Score: 2, Interesting
      % ls -ld /
      drwxrwxr-t 29 root admin 986 Dec 11 16:25 /
      This means that a Joe Blow (l)user can write to the root directory (bearing the sticky bit limitations in mind).
      Wow!!!

      Are you going to explain why Joe Blow's ability to create files in the root directory is a security risk, since he can only remove files that he himself owns? I hope you're not just trying to hide behind "sticky bit" jargon and lofty claims of "weakening a security model that has already had significant difficulties."

      --
      Unlimited growth == Cancer.
    2. Re:OSX is weak - here is some homework. by jceaser · · Score: 2, Informative

      So what if root is readable by admins. The /System folder is much more secure as is /private which is much more important.

      ls -ld /System
      drwxr-xr-x 4 root wheel 136 12 Sep 16:41 /System

      ls -ld /private/
      drwxr-xr-x 5 root wheel 170 14 Dec 13:31 /private

      /private, as you know, is where apple keeps etc, tmp, and var.

      Also, the standard gui installer forces a su password from the user before writing to /System or /Library which seams very reasonable to me.

      O, and if you were woried that someone could swap your commands with another:

      ls -ld /usr/bin
      drwxr-xr-x 652 root wheel 22168 14 Dec 13:24 /usr/bin

      ls -ld /sbin
      drwxr-xr-x 61 root wheel 2074 14 Dec 13:12 /sbin

      ls -ld /usr/sbin
      drwxr-xr-x 201 root wheel 6834 14 Dec 13:20 /usr/sbin

      Only root belongs to wheel.

      So as I hope you can see, it really does not matter what root is, so long as the important directories have the correct settings.

    3. Re:OSX is weak - here is some homework. by pHDNgell · · Score: 4, Informative

      The original point was about / being writable. The problem is that if / is writable (but not sticky), then it'd be possible to do this:

      cp -r etc myetc; mv etc etc.old ; mv myetc etc

      And then you control etc.

      However, due to the sticky bit:

      dustin2wti:/tmp/test 520% ls -ld . etc
      drwxrwxr-t 3 root admin 102 15 Dec 14:10 ./
      drwxr-xr-x 2 root wheel 68 15 Dec 14:10 etc/
      dustin2wti:/tmp/test 521% mv etc newetc
      mv: rename etc to newetc: Operation not permitted

      (because of the sticky bit and my lack of ownership over etc)

      Remember, renames are *directory* modifications, not file modifications. The sticky bit fills in the difference.

      --
      -- The world is watching America, and America is watching TV.
    4. Re:OSX is weak - here is some homework. by prockcore · · Score: 1


      dustin2wti:/tmp/test 520% ls -ld . etc
      drwxrwxr-t 3 root admin 102 15 Dec 14:10 ./
      drwxr-xr-x 2 root wheel 68 15 Dec 14:10 etc/
      dustin2wti:/tmp/test 521% mv etc newetc
      mv: rename etc to newetc: Operation not permitted


      Your test failed to take into account one thing:

      ls -ld /etc
      lrwxrwx-t 1 root admin 11 Dec 15 15:31 /etc -> private/etc /etc is a symbolic link.

    5. Re:OSX is weak - here is some homework. by fr0dicus · · Score: 1

      Not that there's very much in /etc anyway.

    6. Re:OSX is weak - here is some homework. by Anonymous Coward · · Score: 0

      I just did.
      drwxr-xr-x 58 root admin 1972 5 Dec 18:05 /

      And those settings aren't what I have by default.
      On mine Group write is disabled only read and execute are enabled. How many OX boxes did you test this on to get a feel for average?

    7. Re:OSX is weak - here is some homework. by joelhayhurst · · Score: 1

      I did a fresh format install of Panther on my machine, and this is what it says:

      chappi:/ joel$ ls -ld / drwxrwxr-t 34 503 staff 1156 16 Dec 03:43 /

      The date is because I was mucking around with it (I chowned it to root:admin to test this stuff) but mine was definitely set to 503:staff before.

      Could this possibly be related to me mounting this partition in Gentoo? Or is this normal for a Panther install?

    8. Re:OSX is weak - here is some homework. by Anonymous Coward · · Score: 0
      Furthermore, when the OSX installer creates the first user on the system, this user is automatically added to said admin group.

      And what is the first user created on a Linux install? Gosh.. it's root! And root has even more access then the Admin group in OS/X... and (horrors) you get to set root's password on install!!! Man, Linux is super insecure!

      Hint - Get a clue.

  82. Re:Don't always assume a smear campaing by all+your+mwbassguy+a · · Score: 3, Informative

    Macs CAN get viruses
    which viruses would these be? there are still no virii that attack mac os x.

  83. Re:Here We Go Again ... by Anonymous Coward · · Score: 0

    WTF? Are you comparing Linux to Mac OS X now? Come on, at least have an argument worth arguing over! WIth Linux, where are the applications? What about a usable GUI? How about kick ass hardware? Linux has none of the above, huh? GOtta love it when the Linux shitheads come out of the woodwork to denounce Mac "zealots" but ignore their own idiotic zealotry to do it.

  84. Re:is it true by Anonymous Coward · · Score: 0

    No, mac use is open to all homosexuals

  85. Re:Don't always assume a smear campaing by thebatlab · · Score: 1

    B/c the point I was making wasn't directly tied to the content as much as people seem to think it was. That the rebuttal simply attributed what the orignal author said to be jealous zealotry and etc. can simply be explained by misinformation and lack of knowledge on the original authors part. I thought my post made it clear what it was about about but if not, there it is in black and white.

  86. Oh, but wonderful Microsoft... by HarveyBirdman · · Score: 1

    ...will release a secure operasting system Real Soon Now! So what if their last 95,102 attempts failed. They have said they are going to get serious about it! So there!!!!!

    --
    --- Ban humanity.
    1. Re:Oh, but wonderful Microsoft... by Anonymous Coward · · Score: 0

      So what if their last 95,102 attempts failed.

      Closer to six or seven, really, but hey, whatever.

  87. Some confusion in labeling by writertype · · Score: 1
    Part of the concern here seems to be how the article was labeled. In the ABCNews.com piece originally cited, a PC Magazine opinion column written by Lance was defined as "commentary". At the original PC Magazine link here, the piece is part of the "opinions" section.

    Personally, I feel like the word "commentary" implies that the text will be more analytical, akin to a news analysis piece, than merely an "opinion". But that's just my opin-- well, you get the idea.

  88. Re:Don't always assume a smear campaing by thebatlab · · Score: 1

    "See, that wasn't too hard, was it?"

    Nope, it was just unecessary to the point I was trying to make.

  89. Re:Don't always assume a smear campaing by proj_2501 · · Score: 1

    usenet's an OS now? :)

  90. Apple doesn't want to support 100+ video cards... by emil · · Score: 0, Offtopic

    ...or the equivalent number of ethernet cards, SCSI controllers, supported chipsets, etc. OSX can be stable because the hardware platform is under control.

    Apple is also organized as a hardware company. They would have to sell much, much more software to stay alive.

    They would probably die in the conversion to x86, and they would end up producing an OS than ran on a small subset of the available systems anyway.

    And as you can get an OSX-capable system for under $100, why complain? The cost to try it out is negligable.

  91. Re:Don't always assume a smear campaing by thebatlab · · Score: 1

    Tone absolutely has a lot to do with it. However you can't safely assume more malice out of your example. Some people are just more blunt than others and don't doctor up their posts in hopes that most people won't be offended. They either don't care or don't realize that their tone can put people off sometimes.

    You can make a reasonably justified assumption of malice out of the tone of the first article but you can't discount the fact that his malice is tied to lack of knowledge which is the point of my post.

    Never let your enemies anger you and never hate your enemies. And don't always count people with differing opinions as your enemies.

  92. That was a really great article. by notque · · Score: 1, Troll

    And after that article, I'm thinking that my next computer purchase might be a Mac.

    Egads.

    --
    http://use.perl.org
  93. Re:Here We Go Again ... by Anonymous Coward · · Score: 0

    Oh yeah.. Two replies from AC's and your point is proven, right?

    You really AREN'T a smart guy, are ya? Not at all.

    Unless... Of course! Lance! It's you!

    Cheers, chubbs!

  94. m$ champ wrote like a typical m$ paid copy writer by kraksmoka · · Score: 2, Insightful

    notice how the pro PC article just rails on and on about the security flaw, but doesn't mention that there isn't any malware going around to exploit it like in windoze. and how it was fixed promptly within a week. and even if there was malware, how far could it really go in a *nix environment????

    --
    "You never want a serious crisis to go to waste." - Rahm Emanuel
  95. Makes me wonder... by zungu · · Score: 1

    Somedays I wonder if the bad hackers have given MS-windows undue attention, and hence it has a larger share of security attacks. It seems that OSX or and any *nix hasn't received the kind attention of bad hackers and hence are apparently more "secure"!!!

  96. Re:Don't always assume a smear campaing by Nugget · · Score: 1

    The advice you were given is still wise and still stands. Why bother to comment on a situation you admittedly know nothing about? Do you honestly think you've added anything of value to this discussion?

  97. Re:Don't always assume a smear campaing by anachattak · · Score: 1
    there are still no virii that attack mac os x.

    Just because there hasn't been a Mac OS X virus YET doesn't mean that there WON'T be one. The functional part of the sentence (read it again) is that "Macs CAN [expressing potential] get viruses". Read my original posting above and think about it: You bought ENHANCED SECURITY, not COMPLETE SECURITY (currently not available on any market). True: the Mac OS is much more security conscious than Windows, but that doesn't mean that it doesn't have its own vulnerabilities. Mac Fan(atic)s and the assorted zealots need to recognize that their systems may still be vulnerable and that while they can probably sleep easier at night than Windows users, they shouldn't buy into the marketing hype of the Mac "image" and get complacent about OS security. Luckily for all of you, there are folks out there finding the Mac OS vulnerabilities and making sure that they are secured, so that you can have as little in common with Windows users as possible.

  98. Re:Don't always assume a smear campaing by Nugget · · Score: 1

    As near as I can tell, your point can be rephrased as follows:

    "I've never read the article you're talking about, but you have to admit that your interpretation might be inaccurate."

    While this is technically true, it's laughable at best and quite content-free.

  99. Re:Don't always assume a smear campaing by thebatlab · · Score: 1

    Never once did I admit to knowing nothing. Simply that I hadn't fully read the articles. That doesn't mean I hadn't read the articles at all. It means that I felt I hadn't read them well enough to make a complete decision on whether author a was just running his mouth or whether he actually had a good point or whether he just thought he had a good point.

    I don't know if I added anything of value to the discussion but I do know I said what I wanted to say and that's enough for me. That the original post generated some extra discussion is also a bonus. I'd rather a post of mine get -1: Flamebait and have 50 responses, half of them being interesting ones than get a post modded to +5: anything and have no responses at all to it.

  100. Re:hes totally wrong by Anonymous Coward · · Score: 0

    Jamie? Is that you?

  101. Factual Error by skinfitz · · Score: 1

    "...Unix-based Mac OS X system firewall simple enough protection for most users -- is enabled by default (in Mac OSX Server)..."

    Actually, in all versions of server up to and including Jaguar, no, it isn't.

    Not upgraded our XServe to Panther yet so I can't speak for that - anyone know if this is the default (for Panther SERVER)?

    Panther Workstation does not start it by default. (Well not on my PowerBook after upgrade from Jaguar it didn't anyway).

    1. Re:Factual Error by norkakn · · Score: 2, Informative

      Did you do a clean install?

      I think it uses your jaguar network settings when you do an upgrade or archive and install.

    2. Re:Factual Error by mehgul · · Score: 1

      No, you're totally right. I always clean install OS X (workstation, as you call it) and no version has the firewall on by default. It also struck me when I RTFA and I thought it was a pity because it makes the arguments weaker. But it is of course utterly simple to click on "start" in the firewall tab of the "sharing system preference".

  102. Summation of this thread by Anonymous Coward · · Score: 0

    Original article: "I have a microphone, and you don't, so YOU WILL LISTEN TO ME!"

    Rebuttal: "I too have a microphone, so you will listen to ME!"

  103. Has this bug happened before? by spitzak · · Score: 1

    Do you know if any system other than OS/X had this vulnerability? From my (rather quick) reading of this, it seems this is a natural and seemingly benificial result of DHCP design and that plenty of Unix systems would have had this written into them as well. But nobody has mentioned any. Is this bug really unique to Apple?

    1. Re:Has this bug happened before? by Zwoop · · Score: 1
      Well, DHCP is inherently insecure, so this is definitely not a MacOSX specific "bug" (but I personally don't consider it a bug). This is all well documented in the DHCP RFCs and docs, e.g. from RFC 2131:

      7. Security Considerations

      DHCP is built directly on UDP and IP which are as yet inherently
      insecure. Furthermore, DHCP is generally intended to make
      maintenance of remote and/or diskless hosts easier. While perhaps
      not impossible, configuring such hosts with passwords or keys may be
      difficult and inconvenient. Therefore, DHCP in its current form is
      quite insecure.

      Unauthorized DHCP servers may be easily set up. Such servers can
      then send false and potentially disruptive information to clients
      such as incorrect or duplicate IP addresses, incorrect routing
      information (including spoof routers, etc.), incorrect domain
      nameserver addresses (such as spoof nameservers), and so on.
      Clearly, once this seed information is in place, an attacker can
      further compromise affected systems.

      Malicious DHCP clients could masquerade as legitimate clients and
      retrieve information intended for those legitimate clients. Where
      dynamic allocation of resources is used, a malicious client could
      claim all resources for itself, thereby denying resources to
      legitimate clients.


      I think what makes MacOSX "unique" is that they use services traditionally not provided by DHCP (in this case, LDAP server information). Just like with NIS/YP, we have a tradeoff between ease of deployment (automatic service discovery) vs strong security. I know for a fact that way back, many YP/NIS deployments got hacked (in open networks, most commonly Universities) by simply pretending to be an NIS server. NIS+ addressed this problem (and others), and made it close to impossible to deploy and maintain. :-)

      I don't know what Apple will do to "secure" this, the natural solution seems to be to have the DHCP client limit which servers it will talk to (establish a trust relation). It could be done with something as simple as a DHCP server host list, or more likely using Kerberos tickets to verify the authenticity of the DHCP response (I'm no Kerberos expert, so don't quote me on that one). More than likely, it'll make deployment a bit harder that what it is now.

      -- Leif
  104. It's called a "commentary" by e2d2 · · Score: 1

    While the original article's criticism may not have come from "zealous hate", it certainly didn't come from impartial journalism. This and other statements like it definitely tinted it from simple reporting to an apparent attack, complete with the subliminal childish prat-calls.


    It's called a "commentary"

    (
    Commentary
    By Lance Ulanoff
    PC Magazine
    )

    It drives eyeballs to the article. It's not like he's writing under for Associated Press about war crimes in Africa so let's please leave our expectations for impartial journalism at the door.

  105. Everything is relational.. by msimm · · Score: 4, Funny

    Its brilliant! Windows safer by design will prove that everyone is at least as insecure as they are! Bammo! Acceptably secure operating system.

    I smell a Monty Python skit in here somewhere!

    --
    Quack, quack.
  106. Re:Don't always assume a smear campaing by thebatlab · · Score: 1

    How about I rephrase it in a short burst for you straight from the horses mouth.

    "I have not fully read the articles enough to feel I can make a judgement on the original authors intent and as such am taking the viewpoint that the original author may have just been ill-informed rather than the rebuttal authors viewpoint seems to be as his rebuttal ".

    Now, summed up that shortly, it doesn't completely say what I wanted to say but since you insist on summing things up, there's the best I can do for right now.

  107. why? by alienzed · · Score: 1

    hehe banner ads. you crack me up!

    --
    Never say never. Ah!! I did it again!
  108. Hubba Hubba Hubba Who Do You Trust? by Uosdwis · · Score: 1

    Me? I'm giving away free money!
    And where, and where is the Batman!?
    He's at home washing his tights

    So not anyone who flies balloons!

  109. Re:Don't always assume a smear campaing by Anonymous Coward · · Score: 0

    Perhaps for the unintentional irony of saying that some people are misinformed and "like spewing their mouths off" and then, two sentences later, admitting to being uninformed. Comedy gold!

  110. Re:So full of shit by Jim_Maryland · · Score: 1

    OK...can agree that Win32 systems hold the market dominance at home, but in the corporate world you'll find a mixture of systems with critical systems being non-Win32 (in favor of *NIX, Mainframe, etc...).


    If what you say is true that Win32 systems are popular, then it should have the resources to develop a quality product that can't be exploited by a 12 year old with some free time on their hands.

  111. Favorite line from article by Anonymous Coward · · Score: 0

    "Who's crowing now?"

  112. Re:Audit. WAS: Re:trust by Malor · · Score: 2, Funny

    Stay alert!
    Trust no one!
    Keep your laser handy!

    Trust The Computer.
    The Computer is your friend.

  113. Do Blatent lies need rebuttal? by Bill,+Shooter+of+Bul · · Score: 1

    I guess that is the question. I don't think that they do, but after thinking about it I think that History has shown us that they do. Ok, but how can you get your rebuttal heard without starting a flame war? Looking at our political system, and everyone elses for that matter, I don't know if anyone has ever figured that out. Stupid Society.

    --
    Well.. maybe. Or Maybe not. But Definitely not sort of.
  114. You're confusing 2 things here by freeweed · · Score: 2, Insightful

    I get the feeling that merely suggesting that Mac OS X feels less pain from viruses, trojans, and other nasties in part because it has a smaller market share would result in this sort of response

    So is Mac OS X less of a target because of smaller market share? Yes.

    The original authour, like yourself, is confusing 2 things here, and this is why you see so many rebuttals to these sort of comments. A larger market share makes anything a bigger target. Duh. Anyone can figure that out. The problem is, it's a meaningless statement. People get so uppity about it because a bigger target != less secure.

    The fact of the matter is, being a bigger target does not mean you're going to be compromised more often, which is what we're worried about when we talk security. If it did, Apache would be spitting out Code Reds and Nimdas every other month. Being a bigger target simply means people are going to TRY to compromise you more often.

    Remember kids, we don't evaluate the security of something based on attempts. We evaluate it based on SUCCESSFUL attempts. This is why the "if Linux/Unix/BSD/OSX/Commodore 64 had a bigger market, it would be as insecure as Windows" argument is a fallacy, and why it gets rebutted every time.

    --
    Endless arguments over trivial contradictions in books written by ignorant savages to explain thunder in the dark.
    1. Re:You're confusing 2 things here by Anonymous Coward · · Score: 0

      Well said!

      A system is secure or not by virtue of its design.

      It apparently comes as a surprise to some people that more or fewer units in the field does not change the design of the system. An increase in market share will not magically make your system any more or less vulnerable than it already is.

      Also remember that it just takes one successful incident to compromise your system. So it really doesn't matter whether your system is being probed for some particular vulnerability once a minute or once a month.

      What matters is whether or not your system is designed for security. Brian Valentine says that Microsoft systems are not designed for security. I agree with his assessment.

  115. Author's Bio by Anonymous Coward · · Score: 0

    http://www.pcmag.com/author_bio/0,3055,a=204,00.as p

  116. Re:Don't always assume a smear campaing by azav · · Score: 5, Insightful

    Macs CAN get virii. True. However, I was one of the first ten people in the world to identify the mac WDEF virus in 1990-1991. I've followed the virus trail since 1989 to this day on macs and pcs. I even did virus protection for fortune 500 companies once.

    PCs are open holes with regards to virii.

    Macs are a dream in this respect. Even the old OS 9 & lesser.

    Obscurity DOES play a part. A small part. The win 95/98 verisons of windows that are STILL being used are horrors. The newer versions are much better (Me, 2000, XP) but still, the win computer ships with the doors unlocked and open. And the solutions made to close them are subpar. What if I WANT to email a .exe to a coworker?

    I could regail you with tales of the reocurring Scsvr/brasil/ops32 virus at our old office but and all the times our pcs went down but I won't. The time wasted cost us enough.

    The original reporter is a bitter man who is upset that the one part of the mac he chooses to address is much better than the same area on the pc and is despirate to "fight back" and say "nyah, nyah, I tooold you" to the mac crowd, painting them as elitist pinkie pointing beret toting espresso drinkers.

    We need more rebuttals like the one that started this thread. I know many who claim that "less macs = less mac virii you stooge" without closely examining the situation.

    At last check, there were about 60 mac virii. At most 100.
    How many win virii are there out there? 50 thousand? 60 thousand?

    The more the correct message gets published by competent professionals, the less win/mac virii FUD will be going around.

    Cheers,

    --
    - Zav - Imagine a Beowulf cluster of insensitive clods...
  117. I said it... by daveschroeder · · Score: 4, Insightful

    ...once, Apple said it, and advertized it, but I'll say it again:

    This isn't so much of a root vulnerability as a default configuration that trusts the integrity of the local network services. This functionality has been around since NeXTSTEP, and is designed to allow for auto-configuration of new servers/machines brought into the network. The quick 'fix' for the vast majority of users who choose to implement it is to uncheck LDAPv3 and NetInfo altogether in Directory Access. Or, if LDAP services are used, just uncheck 'Use DHCP-supplied LDAP Server' in LDAPv3. ... One could argue that these features should be off by default, but if they are, it kind of wrecks the whole auto-configuration scheme. [There is a certain level of implicit trust of the local network that is assumed.]

    This functionality - yes, functionality - has been in Mac OS X and its predecessors for YEARS. Just because all of a sudden someone paints it as a root exploit does not make it so. This is nothing like the standard fare of Windows remote exploits, some of which can be exploited against unpatched machines from any location on earth, at will, remotely, at any time, against any unprotected vulnerable machine. This "exploit" requires that a roque DHCP server be set up on your local network (!), and that a machine be rebooted (or otherwise perform a DHCP request) in this malicious environment. I repeat: just calling something a root exploit does not make it so.

    Perhaps it's time to have a larger discussion about how much you can really trust your local network infrastructure services, be they in a home environment or in a corporate setting, because that's what this is really about.

    Should Mac OS X have this default behavior?

    What are the tradeoffs?

    And so on.

    I just find the distinct lack of understanding of this issue astounding.

    (Note: and no, this isn't an issue of Apple glossing over something by calling something a "feature" when it's really an "exploit", as you could argue for some of MS's exploits. This really is a feature, and one that can be taken advantage of by rogue services on your network...like just about anything can in one way or another. If you're being affected by this so-called "exploit", you've got bigger problems on your hands...)

  118. Windows can be a trusted environment. by cthrall · · Score: 1

    Having been through the pain of using Authenticode to sign ActiveX controls and creating Windows Install packages, I can tell you the security built into Windows can work if you configure it correctly. Having been hit with seven virii on my home machine, I can tell you the security built into Windows can work IF YOU CONFIGURE it correctly. :)

    Windows Updates shouldn't reset security settings, that's obvious. But I've seen Linux defended with comments like "well, the default settings on that distro start all services known to man," etc. If you don't use a preview window in Outlook, you're halfway there. Don't run with admin privs.

    Granted, the author did more work than the article he was rebutting...the author of the original article really sounds like a jackass. But it comes down to the same thing: Google for Windows security tips and you can have a secure system.

    1. Re:Windows can be a trusted environment. by cthrall · · Score: 1

      > Unlike Windows, Mac OS X requires an administrator
      > password to change certain configurations, run the
      > system updater, and when installing new software.

      He's even more mis-informed than I thought. Windows can deny users the ability to "change certain configurations, run the system updater, and...install new software."

      In a controlled environment, Windows admins can install trusted packages onto user's machines remotely, removing the need for regular users to do so.

  119. Re:Don't always assume a smear campaing by Casualposter · · Score: 1

    I disagree. And yes, I read both articles.

    I thought the PC magazine article was about as useful as the Viagra Spam in my Inbox. I use Linux, MacOS X, and Windows XP Pro.

    I've had as many BSOD's on my XP (1 so far) as I have for my Mac OS X. I think that they are both useful Systems. BUT, I dread the problems of the Windows world. I just don't have them in the MAC world. Viruses and worms and security breeches seemingly galor.

    The tone of the PC mag article was that of a guy bragging about how shitty your new car is because the rear view mirror got knocked off. A minor security hole that could be fixed without a patch by following some instructions provided by Apple. (And yes I read up on the security issue) It wasn't about how the MAC community (there is such a thing?) is in need of an attitude adjustment so much as it was a "HA HA! Looks who's in the shit now!!!" article. It was designed to provoke and it did.

    I figured that somebody would calmly and precisely explain to Mr. Pot that, yes the Kettle is black in places too, but that the pot is all black, crusty, in need of an overhaul, and leaks frequently. And from the Cook's point of view, the kettle is in much better shape.

    --
    Creative Spelling Copyright (2002). May use without Persimmons
  120. Re: Technologists by Anonymous Coward · · Score: 0

    I am a technologist (biotechnology, genetic engineering and the like), and i can tell you that I've learned alot in the three and a half years I spent in school to get that title. What exactly are you useful for? Your attitude makes it difficult to take you seriously.

  121. Infantile prick by TheMonkeyDepartment · · Score: 1

    Lance Ulanoff's original article was utterly infantile. This was a nicely-written rebuttal, but the obviously ignorant, frustratingly boneheaded Ulanoff will probably not get the point.

  122. Confucius say .... by Anonymous Coward · · Score: 0

    Mac Elite man with hand in pocket feel cocky all day!

  123. What I think is funny... by dfj225 · · Score: 3, Insightful

    Is how many people, when they write about OS X credit Apple with coming up with the secure design or other features. If anyone should be credited, it should be the people who develop FreeBSD, because that is the real reason why OS X is secure.

    --
    SIGFAULT
    1. Re:What I think is funny... by sakusha · · Score: 3, Insightful

      You are right, BSD developers deserve credit. But you missed one extremely obvious point: that includes Apple. Apple's programmers contributing BSD code back to the source tree. Apple's efforts have brought more users and more programmers to BSD than ever before. Apple is the largest Unix vendor in the world.

  124. Re:is it true by Anonymous Coward · · Score: 0

    No, it's also popular with artsy bi chicks.

  125. Admin privileges easy to get, though... by Anonymous Coward · · Score: 0

    Fornos' analysis is a bit flawed in the aspect of admin privileges, I think. Just last week, I needed to fix something on a Mac that I didn't have admin privilege for. It took only 5 minutes (plus physical control of the machine) to give my (network) account admin privileges.

  126. correction for the illiterate by i18rabbit · · Score: 0, Troll

    "This is a fundamental point of epistomology."

    Actually, it's a fundamental point of
    "epistemology" - for those of us who are
    illiterate and need correct spelling to
    look up and determine the meaning of
    such highbrow wordings.

    1. Re:correction for the illiterate by hellfire · · Score: 2, Insightful

      Thank you... more evidence that slashdot needs a flame resistant spell checker

      Ever think that maybe this was just a typo? They happen yanno. Not every mistake is made by a "low brow" trying to sound fancy. Some philosophers are just not good spellers :)

      --

      "All great wisdom is contained in .signature files"

  127. Re:Audit. WAS: Re:trust by sensate_mass · · Score: 1

    LOL

    Funny how that computer seemed to have pretty good security...

    "I'm not paranoid because they're out to get me so much as the fact that my last name is 9."

    --
    --- Submission is feudal.
  128. Re:Mac Zealots or AnitMac Zealots--not just OSes by OECD · · Score: 2, Interesting

    The only fanatics I've ran accross in the MacOSX World are the AntiMac Fanatics.

    There's some kind of fundamental truth there. For example: I was a vegetarian for a decade, and during that time I noticed there was a type of person who looked upon my eating habits as a personal attack. These people would try to drag me into an argument about how I wasn't enough protein, etc. I realized I couldn't win: If I shrug it off, I'm a mindless cultist. If I try to disabuse them of their notions, I'm a fanatic.

    Later I started eating meat and bought a Mac, and now I run into the OS version of these people.

    --
    One man's -1 Flamebait is another man's +5 Funny.
  129. Yeah, if it's in a vault and not networked. by Anonymous Coward · · Score: 0

    In a controlled environment, Windows admins can install trusted packages onto user's machines remotely, removing the need for regular users to do so.

    Right. But the biggest problems on the net today stem from the home Windows PCs that n00bs run with a single user account that has admin rights.

    Having to seesaw between a limited-privilege user account and an admin account is far too much hassle for people who can't even be bothered to click a button to turn on their built-in firewall.

    You know how I spent my day today? Installing Spybot Search & Destroy on about 50 Windows 2000 workstations at a client my company just picked up. Those machines were utterly infested with all kinds of shit that was surrepetitously installed by God knows what. The most infested machine had 536(!) different tracking cookies, adware/spyware items, and porn dialers scattered around/buried on it. There was so much shit starting up in the background at boot time that it was about 7 minutes from I pressed the power button until I could actually DO something on the machine-- this on hardware that should boot Win2k in about 2 minutes. That kind of shit simply cannot happen on a Mac.

  130. Re:Don't always assume a smear campaing by sakusha · · Score: 0, Flamebait

    Don't spread more FUD. You claim there are 60 to 100 "mac virii." What you really meant is that there were viruses for MacOS 9. There are NO known MacOS X viruses.

  131. New Mac OS X vulnerability... Buffer overflow/priv by joebeone · · Score: 2, Interesting
    Sorry if this is redundant... new vulnerability posted to bugtraq... and you got to love the banter ("It appears that parts of MacOSX that didn't come from BSD are not very well written and have significant security issues."):

    http://www.securityfocus.com/archive/1/347578

  132. Re:Don't always assume a smear campaing by Anonymous Coward · · Score: 0

    You have gotten several mac zealots to throw their mod points away on your post and the replies chastising you for considering the possibility that the original person who DARED to suggest the Mac is not the most perfect creation we have ever seen was not an evil henchman of Bill Gates! We thank you for your service. Way to take one for the team. ;)

  133. You're a fucken idiot by Negativeions101 · · Score: 1

    Get a life pal. What's the hell is wrong with you people!? You're a fucken retard if you're not going to take him seriousily because of his "name-calling". Ulanoff is clearly an idiot. He deserves to be called names. Besides, he wasn't even name calling. He said Ulanoff was whining, etc. He didn't call him any names. Can't you just reveal in the greatness of the rebuttal instead of looking at something wrong with it you pretentious assholes. Eat dicks... all of you.

    --

    I'm not anti-microsoft. I'm anti-bullshit. Which means I'm anti-microsoft.
  134. True to an extent by siskbc · · Score: 1
    Most of the security problems I've seen come from moron users running questionable applications. If the e-mail blast from ass-munch marketing had a mac version of their software, spyware and trojans would be just as prevalent on the Mac OS as it is in Windows; but when 90%+ of the machines on the other end are all going to be Windows, you don't write another version.

    Although for a good linux/mac system, none of that junk would execute with priveleges, meaning that the most it could do would be to spew stuff without damaging anything locally. I'm also not sure what Mac's better firewall system and such would prevent from running.

    I tell ya, tho, I know what you're saying. The bane of my existence on the few machines I take care of at work is the morons who install that frigging adware crap.

    --

    -Looking for a job as a materials chemist or multivariat

  135. A microsoft employee posted on Slashdot!!!!!!!!!! by Negativeions101 · · Score: 0, Flamebait

    This guy obviously works at MS. Kill him!

    --

    I'm not anti-microsoft. I'm anti-bullshit. Which means I'm anti-microsoft.
  136. Re:Don't always assume a smear campaing by Paradox · · Score: 1

    Umm.

    I'm just curious, this is like the famous stopped watch at the train station problem.

    How would a Mac OS X machine get a virus. Do you know? What vulnerbilities in the system would permit it to gain one? How you would go about constructing one?

    Yes, it is possible. Yes, I know how. I'm curious if you are basing your statement off of anything other than an apologist mantra. I see a lot of that around here.

    "I'm not a zealot, BUT...."

    --
    Slashdot. It's Not For Common Sense
  137. security through obscurity by Anonymous Coward · · Score: 0

    "security through obscurity" - what Lance is referring to toward the end of his article - doesn't work.

    Just a reminder to everyone of why this fundamentally matters. The point is that if security depends on the secrecy of the mechanism, then any exposure of that mechanism puts all users of the mechanism at risk.

    If only the secrecy of the key is important to security, then the exposure of a key is only a risk to the users of that particular key. Users of other keys are not affected.

    Auguste Kerchoffs discussed this principle in 1883, so it's not exactly news. But it seems that senior people at Microsoft are still actively ignoring it in their quest to promote their software.

    Closed source has no fundamental security advantages over open source. The best that we as security experts can can say is that it may offer some transient advantage, but at a very high cost if it is ever exposed or reverse engineered.

  138. Windows security by suitti · · Score: 1
    Nothing will ever be totally secure.

    Windows is better than nothing.

    ...from which we can conclude that...

    Windows will be better than totally secure!

    --
    -- Stephen.
  139. Re:You didn't know? by bursch-X · · Score: 1

    Usenet is all and everything. The Matrix has you.

    --
    There are two rules for success:
    1. Never tell everything you know.
  140. google stats = skewed by green+pizza · · Score: 1

    That would be 38% according to Google, by the way. That study you're misquoting only surveyed a small sample of a specific market segment.

    Ugh, how many times to people have to explain this... google browser stats are a very poor meter of OS distribution... for two reasons. First of all, the average work PC sits in your dentist's office or your architect's drafing room. It's not often used for web searching, that's generally done at home or in businesses/schools that do a lot of research. Secondly, google users tend to a more up to date with technology than the average computer user. They don't have msn.com set as their home page, no are they using the same computer they "invested in" six years ago.

    1. Re:google stats = skewed by spectecjr · · Score: 1

      First of all, the average work PC sits in your dentist's office or your architect's drafing room. It's not often used for web searching, that's generally done at home or in businesses/schools that do a lot of research.

      Obviously you've not actually been out in the real world much, where pretty much everyone and their dog surfs the web at some point or other each and every day, from work. Including receptionists, office workers, people in cubicles, etc etc etc etc etc. And yes, receptionists in doctors and dentists offices do indeed surf the web.

      --
      Coming soon - pyrogyra
    2. Re:google stats = skewed by green+pizza · · Score: 1

      Obviously you've not actually been out in the real world much, where pretty much everyone and their dog surfs the web at some point or other each and every day, from work. Including receptionists, office workers, people in cubicles, etc etc etc etc etc. And yes, receptionists in doctors and dentists offices do indeed surf the web.

      I have indeed seen this... it's one of the reasons why I have to wait so long for the staff at my public library to check my books out.

      My point is they're not all using XP. And they're not all using Google either. My coworkers, the guy that runs the neighborhood computer store, and the staff of the local stereo shop all use recent computers and most use Google to search. Outside of the geek/semigeek community, older machines, older versions of Windows, and the MSN and Yahoo search engines rule the roost.

      The idea that most people use Win2K or WinXP and do so on a 750 MHz+ computer is insane. It's more like Win98 and a PII/350, on a good day. Especially in offices. Things are a bit better at home, where junior bugs mom and dad for an upgraded machine to run the latest wiz-bang game.

  141. Re: Technologists by andynz · · Score: 1
    Sorry, I have to agree with the original poster with regard to the technologist label.

    I have a Bachelor of Technology and would never call myself a technologist. I am also entitled to call myself an engineer but don't bother thanks to IT companies ruining the term (would you like fries with your MCSE?).

  142. Re:So full of shit by Anonymous Coward · · Score: 1, Insightful

    Apache runs 67%, whereas IIS runs 22% of all webservers, according to netcraft. That's why we hear about so many critical Apache vulnarablilities every couple of months, right?

  143. Mac OS X buffer overflow/privilege escalation by MacDork · · Score: 1

    Well, if default settings in OS X made Lance Ulanoff excited, this is going to give him wet dreams... SecurityFocus's Bugtraq mailing list just posted this. The message seems to indicate other exploits exist but were not mentioned. The exploit in question appears to deal with Apple's ISO 9660 file system implementation. No word on whether "Max" alerted Apple or anyone outside of the Bugtraq mailing list though.

    1. Re:Mac OS X buffer overflow/privilege escalation by Anonymous Coward · · Score: 0

      That's not a remote exploit, though, it's just yet another buffer overflow that can give you root if you can get in as any user...which are, unfortunately, still common in most Unix systems.

      Remote exploits, which are the worst, are attacks that you can actively perform against a machine that's just "there", connected to a network that you can access. The MSWin Blaster problem was a direct remote attack. In the 80s and 90s, Unix systems had plenty of problems with remote attacks, but they are becoming more rare as fewer of the traditional services are enabled.

      I'm reasonably confident that MacOS X doesn't have any similar remote exploits by default, considering that it doesn't listen to any external ports.

  144. Re:Audit. WAS: Re:trust by Anonymous Coward · · Score: 0

    Don't trust vendors that won't let you audit their code.

    Open source is 100% audit friendly.

    Mind you, a proper Audit means Auditing everything.

    I wouldn't want to be the sucker that has to audit the whole damn Kernel, most of userspace, gcc, libc .. *grin*

  145. That Is a Local Vulnerability, Not Remote by good+soldier+svejk · · Score: 1

    It requires a local user to initiate the process. A remote host can't execute the attack on its own.

    --
    It is cowardly, and a betrayal of whatever it means to be a Jew, to act as a white man

    -James Baldwin
    1. Re:That Is a Local Vulnerability, Not Remote by Trurl's+Machine · · Score: 1

      But the "remote host" can send an email with binary attachment to the "local user". If the local user receives it with the default mail application of the MacOS 9 (obviously, Microsoft Outlook), the application will process the attachment in the same way as described above - unpack the archive, mount the image, launch the QuickTime Autostart procedure. And you get the same result.

      Obviously, there is a very easy "patch" for this vulnerability - just disable the damned Autostart option in QuickTime preferences. But it's really annoying that it is enabled in a vanilla configuration. What were they thinking?

    2. Re:That Is a Local Vulnerability, Not Remote by good+soldier+svejk · · Score: 1

      The vulnerability is still local and relies on user action. And of course, it will only work with Outlook Express, Outlook or Entourage. But you are right that it is ridiculous that they left the defaults this way.

      --
      It is cowardly, and a betrayal of whatever it means to be a Jew, to act as a white man

      -James Baldwin
    3. Re:That Is a Local Vulnerability, Not Remote by MagnusDredd · · Score: 1

      If the machine you are talking about is a webserver, there sure as hell better not be anyone checking their personal or webmaster email on the machine. Or browsing the web for that matter...

      With OS 9 servers, you remove EVERYTHING not neccesary to the task at hand.

      No web browsers, no paint apps, no quicktime apps, no email clients, no video conferencing apps, no chat clients, nothing...

      The only thing that should be on the machine is the server software, a few utilities, and AppleTalk on a separate card on an internal network for uploading things.

      note: If the machine in question is not running email services, there is no "local user" as far as email is concerned. Unix rules, but the paradym is not even remotely like that of MacOS 9. Most OS 9 servers are single use machines.

  146. Re:So full of shit by Anonymous Coward · · Score: 0

    I remember an old saying that went something like this:

    Microsoft Windows is a 32 bit operating environment based on a 16 bit operating systems for a 8 bit processor developed from a 4 bit calculator by a 2 bit company which doesn't make 1 bit of sense.

    Not quite the original, but you get the idea!

  147. Re:Can't beat BSD! by Anonymous Coward · · Score: 0

    And the $30-$50 a month ISP charge since you have to be online all the time to get the weekly patch.

  148. Re:Mac Zealots or AnitMac Zealots--not just OSes by GnarlyNome · · Score: 1

    See what eaing meat brought you to using a Mac

    --
    Diplomacy is the art of saying "Nice doggie" until you can find a rock. Will Rogers
  149. Re:New Mac OS X vulnerability... Buffer overflow/p by Anonymous Coward · · Score: 0

    I'm get a permission denial.
    Maybe they fixed the problem?

  150. Re:Don't always assume a smear campaign by azav · · Score: 1

    I meant the "collective mac OSes" from day one 'till today since I was comparing mac virii to win virii on the "collective windows OSes".

    It would be unfair to compare OS X to all windows versions. There are old macs not running OS X out there as there are old win boxes running 98 & the like.

    It would be interesing to compare modern windows OS virii to modern mac OS virii. But I don't know where to start on the win side.

    There are virii for mac OS X IF you count the MS word macro viruses. But as you mentioned, I don't know of any OS level viruses for OS X. Wonder if any unix worms might count?

    --
    - Zav - Imagine a Beowulf cluster of insensitive clods...
  151. Re:is it true by Anonymous Coward · · Score: 0

    There are no homosexuals, only homosexual acts, like what I did to your daddy last night.

  152. Re:Don't always assume a smear campaign by sakusha · · Score: 1

    It is equally unfair to compare MacOS X to OS 9, they are different OSes. OS 9 is officially dead, just like Win95. I won't count Win95-specific viruses (if there is such a thing) against WinXP, so don't count OS9 viruses against OS X.

    Unix worms have never hit MacOS X. Macro viruses don't count, they can't affect anything beyond the document. Most OS X users don't even have MSOffice or MSWord. And even if they did, the OS X version of Office is AFAIK the first version to have macro virus protection and have it turned on by default. It's a dead issue.

    And while I'm being nitpicky here, FYI the plural of virus is viruses, not virii.

  153. Transpose this to politics by ianscot · · Score: 1
    This seriously isn't meant as a troll; I'm basically agreeing in general but not in specific with the parent post -- but take a look at the way this sort of "opinion piece - rebuttal" dialog goes in the political realm, and you get a sense of why this guy responded as he did. It isn't just that he was pissed off, it's that sometimes you have to puncture the hot air balloon a bit.

    Take Ann Coulter -- not to pick sides, but just as the best example of this phenomenon that occurs to me. Coulter makes a big, long rant about how the New York Times didn't even cover Dale Earnhardt's death until days later into the centerpiece of one of her books. The Times, she says, didn't even run a story until days later, when they ran a snooty piece about how the Wal-Mart was silent in mourning. And so on. She's running down the Times in every possible way for its arrogance and elitism, and so on.

    Al Franken, in his recent book, points out that this would be a great example for Ann to use, if only it were true. And he photocopies the front page of the Times the day after Earnhardt's death -- on which they ran a very large headline about the accident and Earnhardt's life.

    Now, does it rank as a horrible insult and a discredit to his position that Franken includes Coulter among his list of "Liars"? Does it really discredit this guy's arguments when he describes the PC Magazine column by saying it "epitomizes the concept of yellow journalism"? To my mind, not if he makes that specific charge into more than a name. And he does -- he demonstrates how the PC Mag. article proceeded from its biases and manipulated the reader, seemingly out of malice and to promote a certain POV for its own sake.

    Reading both opinion columns, this rebuttal was well within bounds. At most he fed a troll, but you know, a published troll is somehow fairer game than just anyone's /. post.

    --
    "Fundamentalism" isn't about divine morality. It's about human authority.
  154. Re: Technologists by Anonymous Coward · · Score: 0

    I suppose that things could be different for you CS folks, what with everyone and their dog having some kind of certification.

  155. Re:Don't always assume a smear campaign by azav · · Score: 1

    You seem to be off base here. Win 98 is supposed to be officially dead as well. But people still use it. I used OS 9 on Sunday and have a SCSI interface laptop running the speedy 8.5. My PC has win 98. My old office machine has 2000.

    I do not have data to compare older mac OSes and older win OSes with regards to virus strains and I do not have the data to compare the new versions of each OS similarly. Therefore I can not honestly do a comparison at that depth. The only fair approach I can do is to approach the problem as a whole mac OS vs whole win OS issue. THAT SAID, both OS 9 and OS X have drastically lower numbers of viruses written for them. I'm sure we both agree on that.

    You are wrong about macro viruses. A word glossary macro virus can (and has for me) disabled printing and saving for ANY opened word doc. This would definately be a problem for someone running classic on OS X.

    Classic is for OS 9. Classis is still supported. You referring to it as a "dead" is incorrect. Apple still supports it through classic. In fact, the company producing Onadyme only has an OS 9 version. "I'm not dead yet".

    The pural of virus is viruses in some cases and virii in others. My biology backgorund is showing. I'll tuck it in next time.

    Virii = multiple strains.
    Viruses = more than one of the same strain.

    At least that's as I was taught in biology.

    Cheers,

    --
    - Zav - Imagine a Beowulf cluster of insensitive clods...
  156. Re: Technologists by Kplusplus · · Score: 1

    You must mean the IT folk, last I checked there was no CS in a can degree out there.

    --
    -"I'm one of those Mac people that will break a bottle on the bar and hold it to your throat for bad-mouthing my system"
  157. Re:hes totally wrong by ragecgi · · Score: 1

    Exactly. IE rocks in that regard imho.

    /*BEGIN self-thrashing RANT
    For the last year, IE has been our self-admitted"-"mac-zealot"-employers' only way of finding a Mac node on our network, OS9 & Panther mix. (ironicly xserv-run network btw)

    Plug'n-play-networking w/windows "out of the box" my arse.

    And unlike our Win boxes, IF you are lucky enough to find another Mac on the network, you need a pass/user combo to access a dir.
    Normal I know, but annoying, and costly in a production environ.
    Everytime a win box wants to grab anything off another Mac machine, the Mac user has to setup a separate pseudo-shared pass/user protected folder, and copy the files there for us to grab.
    On Windows, you right-click (no way! a multi-button mouse??? hehe.. yeah, a troll I know:) on any folder and make it shared.

    And of story.

    If any Mac folk wish to tell me wtf our "Mac-network-guy" is doing wrong, I'd be happy to tell him:)
    Out of the box, a Mac can see others just fine. NOT the other way around as advertised by Apple MANY, MANY times.
    (at least that was the bs our boss bought from his sales-retard at the Apple store)
    END RANT*/

  158. OS X sounds really neat by adept256 · · Score: 1

    Where can I get a copy for my PC? Oh... You need a mac to run it... If mac users are so unhappy with windows why don't they uninstall it and use OS X? Ahh... You can't get Windows XP for a mac... What the hell are they arguing about then?

    --

    I ran a benchmark on my quantum computer, now I can't find it anywhere!
  159. Re:hes totally wrong by Minna+Kirai · · Score: 1

    That syntax is wrong. You won't get any answers- nobody will read /*text inside comments*/. It's by definition irrelevant to the actual behavior of the program, so we just /*tune it out*/