On Fri, 5 Oct 2007, Timothy Clemans wrote: > Until there is a solid exploit for the Sage notebook I don't think > this is a big deal.
This is the worst software practice to EVER come out of Redmond. You should know better than that. With that attitude, you don't get started on a fix until an exploit has been *discovered* in the wild -- that discovery happens 6 months to a year after release. Then, it'll be another month before a fix is published, and another year to two before the install base (security n00bs like me) get around to upgrading to the secure edition. By that time, you've cross-infected your entire internal network, and you've assisted spammers and botnets in the infection of hundreds or thousands of other boxen. Read the articles I posted. NONE of the linux admins new that they'd been pwned, months after the fact. That's *scary*. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sage-devel" group. To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel?hl=en -~----------~----~----~----~------~----~------~--~---
