Replies

No, actually, you're the one who wants to bring up Windows. Nearly everybody else is discussing OSX here.

Intelligent discussion requires that both parties have some knowledge or experience of the topic discussed; you do not have ANY experience with OS-X. On the other hand, I have extensive experience on both platforms which makes me more qualified then you to have an opinion. You have repeatedly spouted nonsense about this issue. For example, you very first post on this thread, which I quote:

"Repeat after me: "OSX is se-currrrrrrrrrrrrrrrrrre....." BWAHAHAHAHAHAHAHAHAHAHAHAHA!"

Now THAT is really intelligent discourse. Your second post end with your first slur on THIS thread:

"The Mac bigots tend to ignore bad news.

Of course, you Windows bigots are always extremely polite? Strange, just one reply later you insult a person YOU invited to the party who very politely requested you remove him from your ping list: "I'll bet you don't want to be pinged. Ignorance is bliss."

Next. we find you actually responding in a proper discussive manner... but that doesn't last long... at the next post we have youi agreeing with mere speculation that is contrary to the facts and ending with another: " BWAHAHAHAHAHAHAHAHAHA!" of glee. I think we see you real motive for participating in these threads.

Now returning to your last posting:

"Good thing you're not using your Mac in a corporate LAN/WAN environment. Because if you were, you're vulnerable. "

First, someone on this hypothetical corporate LAN/WAN would have to have malicious motives to damage a corporate asset... and then decide he only wanted to attack the Macs on that environment (perhaps someone who is a Windows bigot?) and then to do it ONE COMPUTER AT A TIME.. Add the chance that once the work around was known, the corporate IT guys would not have bothered to change to two minor settings on the at risk computers, which will STILL work on the network normally with those settings changed.

No, Bush2k, this is not a real big worry in the Mac world.

Am I concerned? Yes. Am I worried? No.

My point in asking about the number of critical security issues in Windows has to do with your obsession with the few that may occur in OS-X. Consider Luke 6:41:

Why do you see the speck that is in your brother's eye, but do not notice the log that is in your own eye?

The relative numbers of security issues on Mac OS-X and on Windows are equivalent to the speck and log referred to in Luke, Work on your LOG and let the Mac users worry about their SPECK!

Intelligent discussion requires that both parties have some knowledge or experience of the topic discussed; you do not have ANY experience with OS-X.

Bzzzzzt! Wrong. I know BSD. You lose.

Of course, you Windows bigots are always extremely polite?

Straw argument. The issue wasn't politeness. It was ignoring bad news.

First, someone on this hypothetical corporate LAN/WAN would have to have malicious motives to damage a corporate asset...

Allow me to be the first to educate you: Most corporate hacks are *internal* jobs. Read When the Hacker is on the Inside.

... and then decide he only wanted to attack the Macs on that environment (perhaps someone who is a Windows bigot?) and then to do it ONE COMPUTER AT A TIME..

A malicious DHCP server doesn't have to target Macs exclusively. Where did you ever get that bogus idea? As for attacking one computer at a time, read about DHCP protocol. general_re does a good job of describing what the malicious server can do -- and it could be catastrophic. Read #47.

Add the chance that once the work around was known, the corporate IT guys would not have bothered to change to two minor settings on the at risk computers, which will STILL work on the network normally with those settings changed.

Any IT guy that would deploy a Mac in a corporate enterprise (I'm still searching for one) probably has no idea what this hack means -- or why it's dangerous -- so I wouldn't put too much faith in these sorts of things. Insider hackers could be working this weekend when the IT guys are stuffing themselves with turkey.