You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The polkit dialog does not show which user is authenticating. This can cause user confusion, like in this review:
Finally, a security bug I mentioned in my last review remains and I was disappointed to see it lingers. Non-privileged accounts (regular user accounts) can perform administrative actions if they have the first user's password. This happens even when the regular user is not in the sudoer file and it allows guest users to install or remove software. This means if two users happen to have the same password (or similar ones and the user makes a typo) they can perform admin actions without being a privileged user. This seems like a design flaw and one that, while it probably can only be exploited in a few rare situations, makes me uncomfortable with the security settings on Solus.
Budgie version
10.9.2
Operating System
Solus 4
Steps to reproduce the issue
Have a system with one admin user ('Test User' below).
Create an additional user without admin privileges ('Temp' below).
Do something that requires admin privileges. Eg: unlock the users page in the settings, restart a service without sudo.
Get a password prompt for the admin user, without mentioning that it's for the admin user.
Actual result
Expected result
Show the authenticating user when authenticating. Examples of this:
Polkit on terminal:
GNOME:
Plasma:
Additional information
No response
The text was updated successfully, but these errors were encountered:
Description
The polkit dialog does not show which user is authenticating. This can cause user confusion, like in this review:
Budgie version
10.9.2
Operating System
Solus 4
Steps to reproduce the issue
Actual result
Expected result
Show the authenticating user when authenticating. Examples of this:
Polkit on terminal:
GNOME:
Plasma:
Additional information
No response
The text was updated successfully, but these errors were encountered: