Issue happens if running in tmux.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1377924
Title:
ecryptfs fails to mount (Unable to link the KEY_SPEC_USER_KEYRING into
the KEY_SPEC_SESSION_KEYRING)
I have fixed my problem with screen + private by reading this question.
http://askubuntu.com/questions/240555/how-to-prevent-ecryptfs-from-
umounting-home-if-tmux-is-still-running
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Just using ssh is not a solution.
I have long running commands (sessions) that need to run in "screen" (tmux) and
also need access to files from Private.
After the ssh connection closes the Private will unmount.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Just using ssh and all the ecryptfs problems are gone.
I think ecrypfts should provide a better explanation, when it cant
access the keyring.
Kernel:
4.4.1-040401-generic #201601311534 SMP Sun Jan 31 20:36:43 UTC 2016 x86_64
x86_64 x86_64 GNU/Linux
--
You received this bug notification
Just using ssh and all the ecryptfs problems are gone.
I think ecrypfts should provide a better explanation, when it cant
access the keyring.
Kernel:
4.4.1-040401-generic #201601311534 SMP Sun Jan 31 20:36:43 UTC 2016 x86_64
x86_64 x86_64 GNU/Linux
--
You received this bug notification
Just hit it with mosh session.
"Unable to link the KEY_SPEC_USER_KEYRING into the
KEY_SPEC_SESSION_KEYRING; there is something wrong with your kernel
keyring. Did you build key retention support into your kernel?"
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Just hit it with mosh session.
"Unable to link the KEY_SPEC_USER_KEYRING into the
KEY_SPEC_SESSION_KEYRING; there is something wrong with your kernel
keyring. Did you build key retention support into your kernel?"
--
You received this bug notification because you are a member of Ubuntu
Server
@joseph spitz (josephgrey)
The same happens to me inside Byobu (tmux), with Ubuntu 14.10, Kernel
3.6.0-34
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1377924
Title:
ecryptfs fails to mount
@joseph spitz (josephgrey)
The same happens to me inside Byobu (tmux), with Ubuntu 14.10, Kernel
3.6.0-34
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1377924
Title:
ecryptfs
@josephgrey I encountered the same situation, not working inside tmux.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1377924
Title:
ecryptfs fails to mount (Unable to link the KEY_SPEC_USER_KEYRING
@josephgrey I encountered the same situation, not working inside tmux.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1377924
Title:
ecryptfs fails to mount (Unable to link the
The reason for the failure seems to be in default configuration of PAM
for SSH.
If I understand correctly, PAM is configured to enforce session keys revocation
upon termination of parent SSHD process:
--- /etc/pam.d/sshd ---
...
# Create a new session keyring.
sessionoptional
This config file belongs to ssh, not to pam.
** Changed in: pam (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1377924
Title:
ecryptfs
The reason for the failure seems to be in default configuration of PAM
for SSH.
If I understand correctly, PAM is configured to enforce session keys revocation
upon termination of parent SSHD process:
--- /etc/pam.d/sshd ---
...
# Create a new session keyring.
sessionoptional
This config file belongs to ssh, not to pam.
** Changed in: pam (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1377924
Title:
ecryptfs fails to mount
** No longer affects: apparmor
** Also affects: openssh (Ubuntu)
Importance: Undecided
Status: New
** Also affects: apparmor (Ubuntu)
Importance: Undecided
Status: New
** Tags added: ssh x2go
--
You received this bug notification because you are a member of Ubuntu
Server
I am also getting this error, and like Eugene says, it seems to be
dependent on the environment in which the mount command is executed.
I attempted to mount from inside a tmux session, and the mount failed.
I detached from the tmux session, issued the very same mount command in
a plain ssh
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apparmor (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: openssh (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
I've learned that the issue is not related to kernel version but caused
by environment under which mount is executed.
On my systems (14.04), it fails when executed inside x2go session but
manages to operate when connected via physical VT or SSH.
May be it's related to apparmor, but how x2go and
** No longer affects: apparmor
** Also affects: openssh (Ubuntu)
Importance: Undecided
Status: New
** Also affects: apparmor (Ubuntu)
Importance: Undecided
Status: New
** Tags added: ssh x2go
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I am also getting this error, and like Eugene says, it seems to be
dependent on the environment in which the mount command is executed.
I attempted to mount from inside a tmux session, and the mount failed.
I detached from the tmux session, issued the very same mount command in
a plain ssh
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apparmor (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1377924
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: openssh (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1377924
Title:
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.17 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
Does this issue go away if you boot an earlier kernel version?
** Changed in: linux (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1377924
Title:
ecryptfs
26 matches
Mail list logo
