-
Notifications
You must be signed in to change notification settings - Fork 728
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mosh interacts poorly with PAM #529
Comments
Is your home directory on a networked filesystem (AFS, NFS, etc.) that requires authentication? Also, did you check that .viminfo didn't accidentally become owned by root (try ls -l .viminfo)? |
No. It's on a local hard disk. The home folder is encrypted with eCryptfs.
The file is not owned by root:
If the problem was file permission, I suppose the same error should have happened when I used ssh. |
I found the issue:
|
Ah, eCryptfs. What actually happens is that pam_ecryptfs maintains a session counter ( I don’t think that running a PAM session as a non-root user is a supported operation, so |
(As an example of the kind of amazing horrible things that go spectacularly wrong if you try to run a PAM session as non-root, I just filed LP #1323421 “pam_ecryptfs returns twice from fork in error conditions”.) |
Prevent auto unmount by deleting ~/.ecryptfs/auto-umount |
While running mosh 1.2.4a: This is with a totally empty but existing.profile, both in the encrypted and the unencrypted home-folder on remote. Why does the counter add one when disconnecting and subtract one when connecting? |
That’s not what’s going on. |
We'd still like to find a better fix for this, but tonight @eminence mentioned a half-decent workaround on #mosh: This won't work all the time, but when it does you still get most of the benefits of mosh. |
Ubuntu 12.04 with the latest updates, Vim version 7.3.429
Mosh server (Ubuntu, amd64), Version: 1.2.4-0
931precise1Mosh client (osx): 1.2.4 (installed via brew)
E138: Can't write viminfo file /home/my_account/.viminfo!
Any idea what is going on here?
The text was updated successfully, but these errors were encountered: