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
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
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: openssh (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1377924
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
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 Kernel
Packages, which is subscribed to linux in 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
7 matches
Mail list logo
