m0wdg
Posts: 1
Joined: Sat Jan 07, 2017 1:21 am

Authorised Users in Raspbian GUI

Sat Jan 07, 2017 1:34 am

Evening all,

Got what should be an easy problem to solve, but its being a pain to solve!

I have created a fresh account on the Pi, and added it to the same groups as the Pi user (except the Pi Group as this is user specific...). This enables me to so sudo commands at the terminal, so I can install and remove programs, plus shutdown and restart at the terminal - all OK so far...

My issue is when I try and install or remove packages or shutdown from Raspbian GUI... I always have a pop up stating that I am not an authorised user, and that i should authorise with one of the following accounts:- root, pi... now given that my own account has sudo privileges, why can I not select my own account to authorise with?

Before anyone says I should just use the pi account, I have disabled the account (rather than deleting, as I have read somewhere that some stuff is linked to the pi account and needs it - I want to have the option to unlock the pi account if i need to). The reason behind this is security based... everyone knows the pi account exists, and knowing the details of a user account is half the battle in gaining access to a computer system!

Oh, and I haven't given my own account password-less sudo access - I am a bit paranoid when it comes to IT security... at least that way I need to provide my password every time to modify stuff...

TIA,

Dave

User avatar
jojopi
Posts: 3274
Joined: Tue Oct 11, 2011 8:38 pm

Re: Authorised Users in Raspbian GUI

Sat Jan 07, 2017 4:09 am

The GUI uses polkit for privileged tasks, rather than sudo. (Except for some bits of RPF PIXEL, such as piclone, which erroneously uses sudo internally and probably will never work for passworded sudo users.)

Do you have a file /etc/polkit-1/localauthority.conf.d/51-debian-sudo.conf that says:

Code: Select all

[Configuration]
AdminIdentities=unix-group:sudo
If not, does it help to create that file, and then log in again?

Return to “Troubleshooting”