Take a look at this. This really makes me really mad.
http://news.com.com/2061-10793_3-6144833.html?tag=tb
I hope they reconsider.
http://news.com.com/2061-10793_3-6144833.html?tag=tb
I hope they reconsider.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Scary stuff will happen in January with OS X
- Thread starter frozencarbonite
- Start date
- Sort by reaction score
- Status
Yeah, whatever. There is no 100% secure OS whether it is OS X or GNU/Linux...security is a process and not a product.
So yeah, bring it on
So yeah, bring it on
Well I just hope that apple stays on top of keeping up with security updates as they find things.
No, because that would leave us less secure. Documenting security vulnerabilities and giving the data over to Apple means that they will HOPEFULLY do something about it, instead of leaving John GOOBER to FUD it.
Considering that we are just in the sixth year of the "Century of Windows Bugs", I am not too concerned.
It certainly seems that there are an awful lot of people out there who just can't stand it, because the Mac is such a secure system when compared to others.
If these people were reputable, respected computer scientists and engineers, they would do what reputable and respected scientists and engineers do: When they find a security flaw, in any operating system, they document it. Then they notify Apple, Red Hat, or Microsoft, and tell them. They say "this is what we did, and this is how we did it", supported with their lab notes and documentation. At least, this is what I was taught. Is this way of thinking outmoded today?
If these people were reputable, respected computer scientists and engineers, they would do what reputable and respected scientists and engineers do: When they find a security flaw, in any operating system, they document it. Then they notify Apple, Red Hat, or Microsoft, and tell them. They say "this is what we did, and this is how we did it", supported with their lab notes and documentation. At least, this is what I was taught. Is this way of thinking outmoded today?
Hopefully they'll screw up someone important's system and will get sued.
Do something like this WITH APPLE, not out in public where you jeopardize people's work as a consequence of your little crusade.
Do something like this WITH APPLE, not out in public where you jeopardize people's work as a consequence of your little crusade.
it needs to be done, to keep OS X the most secure system ever made. But i do agree that it needs to be something kept private between the people doing it and with Apple. If Apple fail to fix up the bugs, release a few to the public. that should get their attention.
Why not report it to Apple. Most people know that a OS cannot be 100% secure. What will they gain out of it? Unless they are Windows fanboys that long for the virus-free days or they just want to make friends within the Microsoft community, they won't gain a thing.
It's a hacker thing. They want to prove how smart they are first. But they are publishing the results, which is rather white hat of them.
I think you guys have missed the point, they are releasing them to the public first, to give Apple motivation to fix the issues, they want to put pressure on apple to get coding faster.
It's only really the tip of the ice burg.
If these guys just found some bugs, told apple and no one else it's unlikely that apple would do anything against it.
Also, this raises there profiles giving them enlarged e-penis .
It's only really the tip of the ice burg.
If these guys just found some bugs, told apple and no one else it's unlikely that apple would do anything against it.
Also, this raises there profiles giving them enlarged e-penis .
I hear it will increase spyware and pop-up problems for Macs and cause everyone's AIM buddy lists to become incompatible.
They're not hacking someone else's computer. Their using "fuzzing" software to throw the kernel some curveballs and see how it reacts to unusual inputs, and if any of that behavior can become a security risk.
- Status