Daniel JS
Forum Enthusiast
LOL!!! A standard (non-admin) user in OS X is fairly hobbled... but.. yes.. I do know what you're talkin' about...Sure. However, protecting the user from their own stupidity is not
something I realistically expect from any OS in my lifetime.
Which goes back to what I said before... are we placing a value on protecting the system... or protecting a user from himself?On an average OS X real-life volume there is valuable stuff that is
not permission-protected.
Ok.. so that we don't talk in circles... here's the actual alert:I am not sure what you mean by "summarily". So the demonstration
page only activated a script already present on any OS X system
whose effect was or included starting up Terminal?
http://secunia.com/advisories/11622/
Mac OS X v10.2.8 and Mac OS X v10.3.3 are both "immunized" against this. And... a healthy part of the problem with this exploit goes back to what you said about 'protecting the user from himself.' Ever since the first "QuickTime" autoplay exploit was detected in 1998.... its always been the case that users of any system should NEVER "auto" do ANYTHING post transfer from the internet. The exploit you referenced (same as the link I pasted above) only works if "open safe after downloading" is checked. Apple's fix? Change the default.
If the script in question was downloaded to the enduser's computer because the enduser permitted this process.. and the script was downloaded to a known directory (potentially, default desktop, etc) and the "open after downloading" was selected... then yes.. this script could execute and do something not very nice. BUT, you have a number of "ifs" to accomplish, first.OK, so only-just-downloaded scripts do not qualify as KNOWN LOCAL?
See the link I pasted earlier.. it describes it.I assume a single web page can both download a file and run a
remote perl process - can it not? Would be nice if you could
briefly comment on what makes a script KNOWN LOCAL.
Well.. just because someone wants to get force fed marketing information need not mean they're stupid... but even if you don't care about intrustion into your computer... certainly the issue of cookie "leaks" must be a consideration? Or are these the same people that think its ok walk into a suspect part of town with their cash plainly displayed in an money clip dangling from their neck?Again not sure what you mean here. "Yes" seems to indicateYes... but... why?I tend to think that a Mac
user should not be seen as doing something stupid when they enable
pop-ups and even click on them if they are so inclined.
agreement. Why?
And to that end, Mac OS X does an exemplary job... but there is always a price.. such as the information invasion issue I referenced above on cookie leaks. Many "reasonable" websites need cookie access... but many other websits take advantage of this information and intrude on privacy.Because I think it can be genuinely difficult to
differentiate between "safe" and "malicious" web content without
trying it out first, hence the user should be protected by the
software from technically harmful effects. Do you agree with the
quoted statement for a different reason?
1.) You're right.Little Snitch I think it was called.
2.) I typed my answer WAY too quickly.. and the end result was.. I botched a name that I knew.
Ah welll.. come on now... ;-)Nice, but I did not want it bad enough to pay €25.
As a software publisher... I gotta tell you.. I have a serious problem giving an end user THAT much control. It only leads to much bigger problems.My point was not so much about specifically
restricting network access but a more about a systematic approach
to letting the user determine what an application is or is not
allowed to do - play sounds, ask for current time, take over the
whole screen etc.
In a word, no.Sure, OS X knows no ActiveX. I wonder if some of the functionality
of all that wonderful stuff can still be retained without
compromising security.
-Daniel