ecryptfs and the ecryptfs tools have stopped working correctly on recent
versions of Tumbleweed.

I noticed this because an existing ecryptfs Private directory could only be
seen after a local login.  ecryptfs-mount-private over ssh stopped working.

On investigation, it is no longer possible to do ecryptfs-setup-private for a
new user.


$ ecryptfs-setup-private 
Enter your login passphrase [roger]: 
Enter your mount passphrase [leave blank to generate one]: 

************************************************************************
YOU SHOULD RECORD YOUR MOUNT PASSPHRASE AND STORE IT IN A SAFE LOCATION.
  ecryptfs-unwrap-passphrase ~/.ecryptfs/wrapped-passphrase
THIS WILL BE REQUIRED IF YOU NEED TO RECOVER YOUR DATA AT A LATER TIME.
************************************************************************


Done configuring.

Testing mount/write/umount/read...
Inserted auth tok with sig [83ecc1d632221288] into the user session keyring
Inserted auth tok with sig [90e42628446d371b] into the user session keyring
mount: No such file or directory
ERROR:  Could not mount private ecryptfs directory

In the system logs we see:

2017-06-25T07:04:39.396038+01:00 [localhost] kernel: [140502.266628] Could not
find key with description: [90e42628446d371b]
2017-06-25T07:04:39.396052+01:00 [localhost] kernel: [140502.266630]
process_request_key_err: No key
2017-06-25T07:04:39.396054+01:00 [localhost] kernel: [140502.266631] Could not
find valid key in user session keyring for sig specified in mount option:
[90e42628446d371b]
2017-06-25T07:04:39.396056+01:00 [localhost] kernel: [140502.266631] One or
more global auth toks could not properly register; rc = [-2]
2017-06-25T07:04:39.396072+01:00 [localhost] kernel: [140502.266632] Error
parsing options; rc = [-2]

$ uname -r
4.11.6-1-default

$ grep VERSION_ID /etc/os-release
VERSION_ID="20170620"