Bug 11403 - Incorrect info displayed when running pkexec in a real terminal.
Summary: Incorrect info displayed when running pkexec in a real terminal.
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 3
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Nicolas Lécureuil
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-10-08 00:27 CEST by Dave Hodgins
Modified: 2015-03-31 16:06 CEST (History)
0 users

See Also:
Source RPM: polkit-0.107-6.1.mga3.src.rpm
CVE:
Status comment:


Attachments

Description Dave Hodgins 2013-10-08 00:27:55 CEST
While testing a script I'm working on, I used alt+ctrl+f2 to switch to
tty2, logged in as a tester id, then ran the script, but pkexec incorrectly
displayed that it was authenticating as the user on tty1, instead of as root.

Output of the id command
uid=501(tester) gid=501(tester) groups=501(tester)

Output of grep 501 /etc/passwd etc/group
/etc/passwd:tester:x:501:501:tester:/home/tester:/bin/bash
/etc/group:tester:x:501:

The script being executed ...
#!/bin/bash
pkexec '/usr/sbin/copyiso2usb' "$@"

The incorrect info displayed just before the line with Password:
Authenticating as: David W. Hodgins (dave)

In cauldron (at least under virtualbox), it correctly displays
Authenticating as: root


Reproducible: 

Steps to Reproduce:
Comment 1 Dave Hodgins 2013-10-08 00:29:02 CEST
Forgot to mention, pkexec works ok, it's just the info displayed that is
incorrect.
Comment 2 Marja Van Waes 2015-03-31 16:06:26 CEST
Mageia 3 changed to end-of-life (EOL) status 4 months ago.
http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ 

Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.