Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

QS and standard (non-admin) user #521

Closed
sanzoghenzo opened this issue Oct 25, 2011 · 5 comments
Closed

QS and standard (non-admin) user #521

sanzoghenzo opened this issue Oct 25, 2011 · 5 comments
Assignees
Milestone

Comments

@sanzoghenzo
Copy link

@sanzoghenzo sanzoghenzo commented Oct 25, 2011

For security reason I run my mac as standard user.
when I have to install an application (copy to App folder) I cannot use QS since it doesn't give me a dialog box in which I can put my admin name and password.
Same with auto update (i had to manually install the newer version).

Can you implement the authentication dialog for standard users?

@pjrobertson
Copy link
Member

@pjrobertson pjrobertson commented Oct 25, 2011

This has been mentioned before. It is something we most certainly plan on
implementing (I just came across it a few minutes ago, so definitely want to
include it!)

On 25 October 2011 17:38, sanzoghenzo <
reply@reply.github.com>wrote:

For security reason I run my mac as standard user.
when I have to install an application (copy to App folder) I cannot use QS
since it doesn't give me a dialog box in which I can put my admin name and
password.
Same with auto update (i had to manually install the newer version).

Can you implement the authentication dialog for standard users?

Reply to this email directly or view it on GitHub:
#521

@skurfer
Copy link
Member

@skurfer skurfer commented May 4, 2012

I ran into this a couple of days ago. The worst part is that it fails silently.

@pjrobertson
Copy link
Member

@pjrobertson pjrobertson commented May 4, 2012

I've had a rethink and, considering how difficult implementing an authentication dialogue is (I've looked into it, you have to mess about with low level security 'tasks') the best solution would be to test the permissions of /Applications.
If they are not writable by the user then the path to install should be changed to ~/Applications

Thoughts?

@skurfer
Copy link
Member

@skurfer skurfer commented May 4, 2012

This issue is larger than installing applications. See #28. It applies to any operation on a protected part of the filesystem.

@skurfer
Copy link
Member

@skurfer skurfer commented May 8, 2012

While testing things in Mountain Lion, I was reminded that the Command Line Tool prompts for admin privileges when you install it. See QSCommandLineToolPrefPane.m. Perhaps that could be adapted to other areas.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants