gnome-keyring fails with home directory provided by sshfs, on login thousands of files are created

Hi, this is a long standing issue from the old bug tracker which got lost somehow. On systems where the home directories are provided by sshfs, gnome-keyring has to be disabled to make logins work reliably. If not, thousands (here 65000) of empty files like ''.local/share/keyrings/login.keyring.temp-899367567'' (with varying numbers) are generated. Problem seems to be the missing hardlink support of sshfs, which instead makes a copy of the file (with new inode number).

sshfs is particularly interesting for PXE booted live systems (fat clients), where the users have root permissions on the machines (or can bring their own). These setups are often used in student labs and schools. Host keys (for TLS encapsulated or kerberized NFS, for example) are not applicable and sshfs remains (to my knowledge) the only choice, as the user's ID is directly bound to the authentication (current smb 3.1.1. seems not to support unix extensions yet).

It would be great to be able to use gnome-keyring on sshfs-homes.

Many thanks for your work, best regards, Andi