pamu2fcfg fails to run, missing getlogin

Bug #1804540 reported by Kenneth Finnegan
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Raspbian
New
Undecided
Unassigned

Bug Description

Trying to run the pamu2fcfg tool (1.0.4-2) to pair a U2F token to my Raspberry Pi, it returns with the error message "getlogin: No such file or directory"

pi@u2fdemo:~ $ sudo apt install pamu2fcfg
[SNIP]
pi@u2fdemo:~ $ pamu2fcfg -d
getlogin: No such file or directory
pi@u2fdemo:~ $

It seems this package is lacking some dependency to pull in the getlogin command.

Revision history for this message
Nikita Koval (nikodll) wrote :

Can reproduce the bug on [classic] bionic where LDAP authentication is used, but on 18.10 everything works flawlessly with standard user auth.

Revision history for this message
Nikita Koval (nikodll) wrote :

Additional info:
On bionic + LDAP (where I can reproduce the bug) the "logname" command returns:
> logname: no login name
on 18.10 (where I cannot reproduce it) the "logname" command returns my username. So I don't think the problem is with dependencies, but rather some specifics of how login name is retrieved for different authentication types.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.