pam_usb causes infinite loop in tty

[TheScientist101]

Hello,
I installed pam_usb and it was working fine with lightdm, but when I tried to login to tty to fix something I found that pam_usb was causing an infinite loop. I could login when I removed the line, but any form of pam_usb was asking me to login again. I also use arch btw, if that might be the problem.
Thanks,
Urjith Mishra

[mcdope]

Could you provide your authentication log for such a failed login? On ubuntu that would be /var/log/auth.log, not sure what it is on arch.

Also, how have you installed? From source, AUR, something else? Using current version I assume?

[TheScientist101]

I compiled it about 2 weeks ago, but I can't find any "releases". I don't know what the commit was. I will try to install the latest commit and try again.

[mcdope]

2 weeks ago should have been the latest commit i guess. the log is more important :)

[mcdope]

Hmmm, actually I can reproduce that on my main machine. But the log is showing a successful authentication... Interesting...

I can even briefly see the MOTD and a prompt, but session is closed again. If I disable pamusb this doesnt happen, but its really weird since the whole PAM stuff is done at that time...

[TheScientist101]

The log says this, let me know if I should hide something in the logs.

Apr 02 10:20:50 iusearchbtw login[141626]: pam_unix(login:session): session opened for user urjith(uid=1000) by LOGIN(uid=0)
Apr 02 10:20:50 iusearchbtw login[141626]: pam_env(login:session): deprecated reading of user environment enabled
Apr 02 10:20:50 iusearchbtw login[141626]: pam_unix(login:session): session closed for user urjith

I ran journalctl SYSLOG_IDENTIFIER=login

[mcdope]

Sorry for the silence, got some problems keeping up with my life 😅

(Workaround tip -->) What I can say so far is that it works if you disable deny_remote. (<-- Workaround tip)

So it's for sure related to local check, but haven't found the actual source.

[mcdope]

Please give https://www.dropbox.com/s/9hkro5bmhxtk9r6/libpam-usb_0.8.1_issue115_ttylogin_amd64.deb?dl=0 a try

This build circumvents the problem by whitelisting tty logins as local.

[TheScientist101]

How can I install that on Arch? Sorry for the beginner question.

…

On Apr 30, 2022, at 9:27 AM, McDope ***@***.***> wrote:  Please give https://www.dropbox.com/s/9hkro5bmhxtk9r6/libpam-usb_0.8.1_issue115_ttylogin_amd64.deb?dl=0 a try This build circumvents the problem by whitelisting tty logins as local. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.

[mcdope]

How can I install that on Arch? Sorry for the beginner question.
…
On Apr 30, 2022, at 9:27 AM, McDope @.***> wrote:  Please give https://www.dropbox.com/s/9hkro5bmhxtk9r6/libpam-usb_0.8.1_issue115_ttylogin_amd64.deb?dl=0 a try This build circumvents the problem by whitelisting tty logins as local. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.

Sorry, my bad - forgot that you're on arch. You can built that version from branch issue-115-ttylogin

[mcdope]

If you don't say anything indicating otherwise I consider this fixed and will merge it tomorrow.

[TheScientist101]

Sorry, I’ve been caught up in exams. I’ll try it today and let you know.

On Sat, May 7, 2022 at 7:04 AM McDope ***@***.***> wrote: If you don't say anything indicating otherwise I consider this fixed and will merge it tomorrow. — Reply to this email directly, view it on GitHub <#115 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APZTJC5LGLP74D7GK5AS4MDVIZL35ANCNFSM5R4VSNYQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- Thanks, Urjith Mishra

[TheScientist101]

The PR fixed my issue. Unless you have anything to add, should I close the issue?

[mcdope]

Don't bother, it will be auto-closed when I merge the fix. Am Sa., 7. Mai 2022 um 16:47 Uhr schrieb TheScientist101 < ***@***.***>:

…

The PR fixed my issue. Unless you have anything to add, should I close it? — Reply to this email directly, view it on GitHub <#115 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAZI2U4OZDYIYPIBEQCS7ULVIZ7BTANCNFSM5R4VSNYQ> . You are receiving this because you were assigned.Message ID: ***@***.***>

[AlexOConnorHub]

I'll chime in and say that, when using the current release on arch, I had the same problem, and that the issue-115-ttylogin branch resolves the issue. (Just to say that the event is not isolated to just and that this solution works!)

[mcdope]

Thanks for the additional feedback, good to know. Am Sa., 7. Mai 2022 um 18:14 Uhr schrieb AlexOConnorHub < ***@***.***>:

…

I'll chime in and say that, when using the current release on arch, I had the same problem, and that the issue-115-ttylogin branch resolves the issue. (Just to say that the event is not isolated to just and that this solution works!) — Reply to this email directly, view it on GitHub <#115 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAZI2U3BIMCXYJSEVHJHZB3VI2JIBANCNFSM5R4VSNYQ> . You are receiving this because you were assigned.Message ID: ***@***.***>