Friday Security Fun
rgraham writes "Apple has release a new security update for the Safari cookie bug. 'Security Update 2003-12-05 updates Safari to prevent unauthorized access to a user's cookies.' They also updated the article on how to 'Configure Directory Access to Protect Your Mac From a Malicious DHCP Server.'" We posted that the other day, but this time, pictures!
Never hand out cookies when on a Safari!
I'm switching to Fig Newtons.
Just don't allow cookies. (Yes, it seems too simple)
I think I think, therefore I think I am.
Along with this update, Steve Jobs announced today that OS 10.3.2 will include a small globe icon that will appear next to your system clock, helpfully reminding you that you have an update to install. While Jobs did acknowledge the fact that this feature has been in another operating system for years, he did point out that Apple's implementation will harness the power of Quartz Extreme to render fully three-dimensional, alpha-blended "Security Gnomes" that run around and patch your system twice a week. I'll still never Switch back though ;)
The update needs you to reboot the computer. *sigh* Why is that? This is a web browser we're talking about. Shouldn't it be enough quitting Safari + all applications that uses it's content rendering engine? As far as I know, Safari isn't integrated to the OS in any way like IE to Windows, so it shouldn't be neccesary to reboot the *whole* OS. On the other hand they effectively stop applications to interfere while updating and cause problems that way. Maybe it's some precautionary measure, but I don't think this should be neccesary...
BTW software updater was already automaticly fetching the update in the background while I read this. It's really nice when you don't have to wait while downloading them. I don't understand what's the big fuss of letting the OS fetch updates in the background, as long as it doesn't install them. I'm not sure but I think software update does only download the important updates...
I demand the Cone of Silence!
The knowledgebase article for 10.2.8 and for 10.3.1.
'For example, not from advertisers on those sites'
So reads the third cookie option in Safari, but it's not true. You'll find '.doubleclick.net' in there all the time, and I doubt any of you are wandering over to DoubleClick to check out the action.
And any domain for a cookie beginning with a '.' means 'any URL in that domain' - and that is NOT just 'from sites you navigate to'.
...and the cookies only last for the current session.
OmniWeb allows this in a site by site basis rather than across the board. So I can tell it to treat Slashdot cookies normally but trash Amazon ones after every session.
It's the one thing that could drag me back to OW but I also like my Safari tabs.
Please stop being so damn reasonable and honest, after all this is Slashdot.
There are two rules for success:
1. Never tell everything you know.
Just count the sheer number of stories Slashdot has on "Safari cookie bugs", and on the log-in page of Thinkgeek.com it specifically says that Safari users might have problems with their cookies. When I get my Mac 'net connected I'm gonna stick with Opera.
WINDOWS!? We don't need no steenkin' Windows!