Passwords/Logins not stored when using network drive
Hi @ all,
When using TB as a LDAP-User, logins.json and key4.db are NOT created on the (mounted) home directory.
here's my setup: Debian 12 with a local user as well as remote users, administrated via LDAP. PAM-login for local and ldap users has been setup and is working. Automounting of network drives is working. Each LDAP user has their home directory stored on a Fileserver and mounted upon login. All applications are working as intended except thunderbird.
So far I've tried to run gnupg locally instead of having it start a session from the (mounted) home directory, assuming that gnupg is the corresponding means of de/encryption. I've copied the profile of the local user to be used as the profile of the LDAP user, logins.json is completely ignored by TB.
Upon starting of TB, passwords are asked for and are remembered in the session. But passwords/logins are not stored and available for the next session.
Any ideas?
Chosen solution
Here's what worked for me in the end.
Create a new profile and migrate the following previous files from the OLD profile: logins.json,cert9.db,key9.db and pkcms11.txt
Simply overwrite the autopopulated files.
ONLY once all of these files were in place did the migration to a cifs-share work as intended.
Hope that helps.
I'd still be curious to read up on TB login encryption and storage system to "smarten-up".
Read this answer in context 👍 0All Replies (1)
Suluhisho teule
Here's what worked for me in the end.
Create a new profile and migrate the following previous files from the OLD profile: logins.json,cert9.db,key9.db and pkcms11.txt
Simply overwrite the autopopulated files.
ONLY once all of these files were in place did the migration to a cifs-share work as intended.
Hope that helps.
I'd still be curious to read up on TB login encryption and storage system to "smarten-up".