• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: FSCopyObjectAsync: useless and crippled
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: FSCopyObjectAsync: useless and crippled


  • Subject: Re: FSCopyObjectAsync: useless and crippled
  • From: Mark Lilback <email@hidden>
  • Date: Mon, 16 May 2005 12:09:35 -0500

At 11:37 AM +0100 5/16/2005, Hamish Allan wrote:
So I would ask the people who would argue against a simple high-level file access authorization service -- do you really prefer the alternatives?

I did not find it that difficult to handle authentication using the MoreSecurity sample code Apple provides. I wrote a simple helper tool that is passed a dict of FilesToInstall, SymLinks, FilesToDelete, and PathsToCopy and then performs those actions.


I prefer this to a system API because I can then offer to install the files in /Library or ~/Library with the UI of my choice. And, I preflight the files so if they user already has permission to write to /Library, I don't ask for authorization. I really get annoyed when programs ask for authorization when I already have permission to write to all the locations I'd ever want a third-party application writing too (to me, that is the point of having file permissions).

However, I would like to see Authorization Services enhanced so you can ask for specific, common operations to be performed. That way, the details field in the authorization dialog can give real details -- what files are going to be installed, what permissions are going to be changed, etc.

But, I don't think there should be a single call that can copy files with root privileges. That makes it too easy for developers to just use that call instead of making a proper decision about if/where to install files based on the user's setup and preferences. As others have pointed out, users are becoming too well trained in always entering their password without question. I don't see it as too cumbersome to have to spend an afternoon working on code that will execute as root/admin -- hopefully that encourages finding solutions other than don't need root access.

Personally, I'm very reluctant to install a product using a non-Apple installer. With the Apple installer, I can jump to the command line and get a list of what is going to be installed. Thankfully, vise/stuffit installers are largely becoming a thing of the past (outside of Microsoft and Adobe).

--
__________________________________________________________________________
                         "The fetters imposed on liberty at home have ever
Mark J. Lilback           been forged out of the weapons provided for
<email@hidden>        defence against real, pretended, or imaginary
http://www.lilback.com/   dangers from abroad."  -- James Madison
_______________________________________________
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


References: 
 >Re: FSCopyObjectAsync: useless and crippled (From: Hamish Allan <email@hidden>)

  • Prev by Date: Re: NSManagedObjectContextObjectsDidChangeNotification in loaded nibs
  • Next by Date: Re: FSCopyObjectAsync: useless and crippled
  • Previous by thread: Re: FSCopyObjectAsync: useless and crippled
  • Next by thread: AXIsProcessTrusted / AXMakeProcessTrusted
  • Index(es):
    • Date
    • Thread