Linked by Thom Holwerda on Thu 2nd Mar 2006 12:53 UTC, submitted by Moulinneuf
Mac OS X Apple on Wednesday released Security Update 2006-001, available for download through Software Update system preference pane and from Apple's Downloads Web page. The update addresses a recently reported exploit that left Safari users vulnerable to malicious shell scripts, corrects a vulnerability in Apple's Mail software, and also changes the way iChat handles file transfers to help prevent the Leap-A malware.
Thread beginning with comment 100728
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: What not going to wait.
by Kroc on Thu 2nd Mar 2006 14:16 UTC in reply to "What not going to wait."
Kroc
Member since:
2005-11-10

Or even better, if a virus utilising the exploit had a payload date, release the patch _after_ that date. I thought Apple were supposed to be professional, only Microsoft are professional enough to stick to patch cycles no matter what, and release a fix after the payload has already been dropped.

Reply Parent Bookmark Score: 2

RE[2]: What not going to wait.
by n4cer on Thu 2nd Mar 2006 15:23 in reply to "RE: What not going to wait."
n4cer Member since:
2005-07-06

Or even better, if a virus utilising the exploit had a payload date, release the patch _after_ that date. I thought Apple were supposed to be professional, only Microsoft are professional enough to stick to patch cycles no matter what, and release a fix after the payload has already been dropped.

1) Microsoft's patch schedule was implemented at the request of their customers.

2) Microsoft has reserved the right to, and has broken from their patch schedule on several occassions if the vunerability was critical and the possibility of exploit was high.

Reply Parent Bookmark Score: 5

RE[3]: What not going to wait.
by Tom K on Thu 2nd Mar 2006 21:09 in reply to "RE[2]: What not going to wait."
Tom K Member since:
2005-07-06

Way to b*tch-slap the FSF/GNU trolls. :-D

Reply Parent Bookmark Score: 1

RE[3]: What not going to wait.
by kfet on Sat 4th Mar 2006 03:59 in reply to "RE[2]: What not going to wait."
kfet Member since:
2005-07-06

1) Microsoft's patch schedule was implemented at the request of their customers.

2) Microsoft has reserved the right to, and has broken from their patch schedule on several occassions if the vunerability was critical and the possibility of exploit was high.


No patch schedule pedictability justifies a critical vulnerability's intentionial delay. OP refers to a real example of MS letting knowingly their users out in the cold up until after the X hit the Y.

Reply Parent Bookmark Score: 1