I’ve run passwd
and sudo su; passwd
to change password for root and my account. Password is set correctly when using sudo
and su
but whenever I get prompted by pkexec
it accepts only the old password. I’ve rebooted my system to make sure it was not an issue.
Edit:
Solved
Turns out the password were changed for root account but not my user account. I think the reason is that there are no password quality requirements on root accounts, but there are on the default account in ubuntu. Changing the password from root account passwd user
worked fine.
sudo passwd myname
changes the password of the user myname and allows unsecure passwordspasswd
changes the password of the active user and disallows unsecure passwordssudo passwd
changes the password of the root accountsudo su; passwd
Super User Do Super User
If I’m not mistaken “su” stands for “switch user”, not " super user".
Yeah. It’s as dumb as
cat | grep
but people love it.… despite the added risk during that sudo/su switch.
Substitute User Do Substitute User*
su needs root’s password sudo su just needs your password
@Agility0971 Why didn’t passwd tell you the regular user password wasn’t actually changed? Isn’t that a much bigger issue?
hahaha It actually did, I found out shortly after initially posting this. I’m constantly reminded that I haven’t learned reading yet (documentation, datasheets, terminal output etc…)
I’ve ran
I’ve run
Great insight, really contributing to the community
thx
Good to see OP used
sudo su; passwd
(Yes, I know it is frowned upon by a lot of documentation, but I don’t care). I probably would findsudo passwd $USER
something that would need some careful typing in all the passwords to avoid confusion.I usually try to avoid bad habits like this but this time it was justified.
The Ubuntu laptop had to connect to company vpn. It were using
openconnect-network-manager-gnome
thingy to do that. Recently the company upgraded their vpn software which is sorta incompatible with openconnect and requires a modified user agent string for it to prompt for 2FA keys. package in ubuntu 22.04 is too old to modify that in the gui. I tried in the terminal manually, editing the config manually with vim and even dumping the config from my personal Arch laptop. We also tried proprietary Cisco AnyConnect but there is probably a server misconfiguration which causes the connection to drop and reconnect once a minute. In Ubuntu 24.04 it works given the user agent modification, and even though it was released a couple of weeks ago, LTS users don’t get the update before mid August. So the easiest solution was to take the software compile it in the VM and use it there. It’s a temporary solution but we had to have something working by the next morning. With such setup it’s an annoyance to have password prompts show up. On top of that the keyboard is kinda fucked and some characters register multiple times making the situation with passwords even worse.If you have a good idea what I could have tried let me know, love to hear new ideas.
The Ubuntu laptop had to connect to company vpn. It were using openconnect-network-manager-gnome thingy to do that. Recently the company upgraded their vpn software which is sorta incompatible with openconnect and requires a modified user agent string for it to prompt for 2FA keys. package in ubuntu 22.04 is too old to modify that in the gui.
If you have a good idea what I could have tried let me know, love to hear new ideas.
Hmm, tough one. Suggesting to post your question as a new post in relevant Lemmy /c/ or StackExchange and so on. Here as a not so new comment of a comment it will get little exposure I guess.
Yeah true, though it’s dealt with already. Time to put the lid back on that can.