Error in documentation and in pamusb-unlock-keyring-gnome

[ACR36940]

Understood

Yes, this is not a bug report / support request

Text

In the documentation, on the getting started document the section:
Auto-unlock your GNOME keyring
Says
create .keyring_unlock_password in ~/.pamusb/

This don't work.
In the code of pamusb-unlock-keyring-gnome says:

# Check if password file exists, first try $HOME then the auth device
 if [ ! -f ~/.keyring_unlock_password ]; then
     logger -p local0.notice -t ${0##*/}[$$] No password file found, exiting.
     exit 0
 fi

pamusb-unlock-keyring-gnome only checks in the user $HOME in the stable version 0.8.5 location changes in new revisions to .pamusb dir.

[mcdope]

Intended behaviour. Just never updated the doc, will do somewhen. On Vacation for the next 4 weeks. Am Mo., 14. Juli 2025 um 21:03 Uhr schrieb ACR36940 < ***@***.***>:

…

*ACR36940* created an issue (mcdope/pam_usb#272) <#272> Understood Yes, this is not a bug report / support request Text In the documentation, on the getting started document the section: *Auto-unlock your GNOME keyring* Says create .keyring_unlock_password in ~/.pamusb/ This don't work. In the code of pamusb-unlock-keyring-gnome says: ` Check if password file exists, first try $HOME then the auth device if [ ! -f ~/.keyring_unlock_password ]; then logger -p local0.notice -t ${0##*/}[$$] No password file found, exiting. exit 0 fi ` pamusb-unlock-keyring-gnome only checks in the user $HOME — Reply to this email directly, view it on GitHub <#272>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAZI2U6DUGWG2LDI3LVVMPD3IP5JLAVCNFSM6AAAAACBP3XY76VHI2DSMVQWIX3LMV43ASLTON2WKOZTGIZDSNZTHAZTCNI> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[mcdope]

In case you wonder: I removed that because the risk would be too high if the drive is lost. It would expose your plaintext password to whoever finds it. Am Mo., 14. Juli 2025 um 21:13 Uhr schrieb Tobias Bäumer < ***@***.***>:

…

Intended behaviour. Just never updated the doc, will do somewhen. On Vacation for the next 4 weeks. Am Mo., 14. Juli 2025 um 21:03 Uhr schrieb ACR36940 < ***@***.***>: > *ACR36940* created an issue (mcdope/pam_usb#272) > <#272> > Understood > > Yes, this is not a bug report / support request > Text > > In the documentation, on the getting started document the section: > *Auto-unlock your GNOME keyring* > Says > create .keyring_unlock_password in ~/.pamusb/ > > This don't work. > In the code of pamusb-unlock-keyring-gnome says: > ` > Check if password file exists, first try $HOME then the auth device > > if [ ! -f ~/.keyring_unlock_password ]; then > logger -p local0.notice -t ${0##*/}[$$] No password file found, exiting. > exit 0 > fi > ` > pamusb-unlock-keyring-gnome only checks in the user $HOME > > — > Reply to this email directly, view it on GitHub > <#272>, or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAZI2U6DUGWG2LDI3LVVMPD3IP5JLAVCNFSM6AAAAACBP3XY76VHI2DSMVQWIX3LMV43ASLTON2WKOZTGIZDSNZTHAZTCNI> > . > You are receiving this because you are subscribed to this thread.Message > ID: ***@***.***> >

[ACR36940]

Ok.
Moving the .keyring_unlock_password file to .pamusb will cause problems with some users.
Checking "Pamusb pad checking failed" in Google
The Gemini resume says remove .pamusb, the first two results said the same.
Maybe put a warning in the docs?

[ACR36940]

Umm.
The wiki says
create .keyring_unlock_password in ~/.pamusb/
In [pam_usb/doc/QUICKSTART says
* create .keyring_unlock_password in your home directory
Seems that wiki and source are not synchronized