Cannot use a symlink as a private keyring file
Submitted by Elias Toivanen
Link to original bug (#750526)
Description
Hi,
I store my Internet passwords in a separate keyring MySecrets
that I keep with the rest of my private files on a separate partition.
When I create a symbolic link of the keyring in ~/.local/share/keyrings and start Seahorse, I can access the keyring alright, but for some reason the keyrings folder is completely cluttered with symlinks of the form
MySecrets.keyring.temp-*
I did not take a count of these symlinks but there were probably thousands of them.
They all pointed to the true location of the keyring file. In addition, Seahorse creates a copy of the keyring file, which means that over time the two files will get out of sync.
The ideal fix would be that you'd allow the user to specify the location of the keyring file upon its creation.
This users' private keyrings will not get accidentally nuked when they upgrade their distro, etc.
Version: 3.16.x