Gonzie,
I partially agree with you: dragging an app into /Applications
causes Finder to ask for your admin credentials, then _move_ (not
_copy_) the app to the new location, leaving the permissions of the
individual pieces the way they were.
This would potentially allow me to modify the app while it is in use
by another user of my computer, which could be a vector for malware:
Once you copy an app to /Applications, you could edit its permissions
to remove write access either on the command line with something like:
chmod -R -w "Google Notifier.app"
or using Get Info in the Finder.
But this doesn't fix the security hole, since malware could just
change the protections back.
This atttack scenario:
User 1 with the admin password could install an innocuous app, then
run some piece of malware (malA) that rewrites that app to be malware
(malB), which, when user 2 is using the machine, and runs what he
thinks is an innocuous app, then malwareB can work its will.
while, if ownership of the innocuous app had been changed to Admin at
install time, then malA couldn't modify it.
The real fix is to give up ownership. And you might as well give
ownership to the admin account, since the administrator account could
modify it no matter what you set the permissions to.
> some apps install with even worse permissions giving a writable area to all and sundry.
Yes, but some of those that do this do it because the app won't run
otherwise. File bug reports with the authors and wait for updates
before using them.
BUT this isn't AppMenuBoy's job.
* I really like drag installs - I think they are a key part of the
Macintosh experience.
* As a user, I just have a symbolic link in /Applications called "3rd
party Apps" that links to a folder of _my_ apps. That way I don't have
to worry that a system upgrade will blow away something not from Apple
that I care about.
* I don't want to be in the installer business.
* I don't want to be responsible for apps stopping working because I
changed their permissions. (The fact that the app was buggy in the
first place doesn't count: the user will see my program as breaking
their app.)
* As a user, I wouldn't trust an installer app I downloaded from some
random site on the net: What is it really doing?
On the other hand,
> I'd also like to see if possible when you clicked the dock icon it
> would open the application folder rather than bring the app into focus
Easy. Thanks, Will do. You know, I'm so used to clicking and holding
on AppMenuBoy's dock icon (or right clicking) that I didn't notice
that a simple single click doesn't bring up the menu.
Technical details: in response to a re-open apple event, send the
Finder an appleEvent to open and reveal the Applications window.
tell application "Finder"
open POSIX file "/Applications"
end tell
> but little idea if that's possible. oh and icons in the dock menu :)
I tried. You can see my frustration in the original source code: I
make the same system calls to build the dock menu as I do to build the
menu bar menu. In the menu in the menu bar, the icons work. In the
Dock menu, those same calls are ignored.