Description of problem: Hi. This is an odd one. It's not something everybody will do obviously but it's useful when doing QA. When running MageiaUpdate as a normal user, using remote X over ssh, it brings up an authentication box as normal asking for the user password. It wont accept the password though. /var/log/auth.log shows.. Nov 12 08:51:00 mega userhelper[15777]: pam_tcb(mageiaupdate:auth): Authentication passed for claire from claire(uid=500) Nov 12 08:51:05 mega userhelper[15777]: pam_tcb(mageiaupdate:auth): conversation failed Nov 12 08:51:05 mega userhelper[15777]: pam_tcb(mageiaupdate:auth): Unable to obtain a password It's easy to dismiss it as just a quirk of using remote X over ssh but when I use mcc instead and it asks for the root password it authenticates with no problems. Nov 12 08:57:22 mega userhelper[19615]: pam_tcb(simple_root_authen:auth): Authentication passed for root from claire(uid=500) Nov 12 08:57:22 mega userhelper[19620]: running '/usr/sbin/drakconf.real ' with root privileges on behalf of 'claire' I'm not sure if this is an issue with MageiaUpdate or pam_tcb or just a configuration problem.
Source RPM: MageiaUpdate pam_tcb => mgaonline, pam
cc'ing some mgaonline and pam committers @ Claire I supppose this bug is still valid?
Keywords: (none) => NEEDINFOCC: (none) => dmorganec, mageia, mageia, marja11, thierry.vignaud, tmb
Actually no, it looks like something we've updated has fixed this. Thanks Marja, I'll close it.
Status: NEW => RESOLVEDResolution: (none) => FIXED
Reopening as this is still an issue. Not sure why it worked before - unless I didn't check it properly :\ MageiaUpdate as normal user over ssh, unable to auth.
Status: RESOLVED => REOPENEDResolution: FIXED => (none)
I can reproduce with rpmdrake, but it works with drakconf (in cauldron)
Keywords: NEEDINFO => (none)
After you connect, as a regular user try "sudo /usr/sbin/MageiaUpdate".
CC: (none) => davidwhodgins
$ su -c "MageiaUpdate" - works, but as with sudo it effectively starts MageiaUpdate as root. The problem is that it should be able to be started as non-root, asking for the normal user password. Locally that works fine but over ssh for some reason it fails.
This is working again today! I've no idea why it sometimes works and sometimes doesn't. I can't reproduce the behaviour now. I think I'll close this again and if it happens again do some further digging before reopening.
Status: REOPENED => RESOLVEDResolution: (none) => INVALID