Software Update Vulnerability
redmoss writes "I just saw this exploit for Software Update on Bugtraq. Quoting the discoverer Russell Harding: 'Mac OS X includes a software updating mechanism 'Software Update.' Software Update, when configured by default, checks weekly for new updates from Apple. HTTP is used with absolutely no authentication. Using well-known techniques, such as DNS Spoofing, or DNS Cache Poisoning, it is trivial to trick a user into installing a malicious program posing as an update from Apple.' Looks like people using Software Update need to be careful, as there is currently no workaround." Well, one workaround for this particular exploit is to not share a LAN with someone who would do that sort of thing.
Security updates should occur daily at minimum.
/. sigs are 255 chars.
surely, if you've had that sig for more than a few posts, you've been told this many many times already.
is that supposed to be some port of troll?
Credits: Big Dogs Cock
/. since 7/8/02
Trolling in the name of
Some of those that boot Suse
Are the same that bought XP
Some of those that boot Suse
Are the same that bought XP
Trolling in the name of
And now you run what they told you
And now you run what they told you
And now you run what they told you
95 is justified for running the games that you didn't buy
95 is justified for running the games that you didn't buy
Some of those that boot Suse
Are the same that bought XP
Some of those that boot Suse
Are the same that bought XP
And you run what they told you
Now your under control
And you run what they told you
Now your under control
And you run what they told you
Come on!
Fuck you I wont run what you tell me
Fuck you I wont run what you tell me
Fuck you I wont run what you tell me
Fuck you I wont run what you tell me
Motherfucker
Trolling
I like poop!
For fuck's sake you drooling idiots. DNS CACHE POISONING WAS PATCHED IN BIND FUCKING YEARS AGO. [bind 4.2.3 iirc]
(check out jizz.c, erect.c)
>Apple appears to have blundered
There is absolutely FUCK ALL apple can do about it short of rooting vulnerable DNSs and manually upgrading bind.
>a fix ASAP
do the hosts entry move someone else suggested, or whinge to your ISP to patch bind, if they haven't already [clue: they probably have]