Re: FSCopyObjectAsync: useless and crippled
Re: FSCopyObjectAsync: useless and crippled
- Subject: Re: FSCopyObjectAsync: useless and crippled
- From: "Mark Munz (DevList)" <email@hidden>
- Date: Sun, 15 May 2005 22:49:21 -0500
On May 15, 2005, at 9:39 PM, Andreas Mayer wrote:
Am 16. Mai 2005 um 02:59 Uhr schrieb Mark Munz (DevList):
Well OK a user probably wouldn't copy a file into Library, but an
application that needs to install files in /Library/ definitely
would.
Why would any application *need* to install anything in /Library?
If it's only installed for the current user, ~/Library will do just
fine.
If the app is to be placed in /Applications - well, then you'll
need an installer anyway ...
The last thing I want to do is open my app to possible
exploitation because all I wanted to do was copy some files into /
Library
Again: Why would you want to do that? I really hate it when apps
require system wide installation.
It's been a while since I've addressed the issue in my code, but as I
recall there were problems when I tried running my BOA helper app
from inside my Contents folder (specifically, I believe users
couldn't update the application because it was in use).
I didn't want to require an installer for the user just so I could
install my BOA app, so I end up copying it to the ~/Library/ folder.
But I've had complaints that it should be in the /Library/ folder
because of the "size" (it's 1.2MB, which I don't think is a big deal,
but obviously my customers disagree).
So, in this case, copying to the ~/Library/ folder is less desirable
and according a specific administrator customer, a security risk
(apparently because the virus could modify the application -- since
the user has permission to write to it).
Thus, I would *need* to copy the BOA to the /Library/ folder.
If there is a better way to deal with this (that still keeps it
simple for the end user), I'd love to know. The biggest issue I had
was that the Finder won't let people replace the application with a
new version because the BOA is in use.
Yes, I could train the user to put the old file in the trash and then
copy over the new file. I could also use an installer. But that isn't
the Macintosh way.
Mark Munz
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden