This bug was fixed in the package pam - 1.1.8-3.2ubuntu2.3
---------------
pam (1.1.8-3.2ubuntu2.3) xenial; urgency=medium
* Move patch fixing LP: #1666203 from debian/patches to
debian/patches-applied so it actually gets applied.
* debian/libpam-modules.postinst: Add /snap/bin to $PATH in
/etc/environment. (LP: #1659719)
pam (1.1.8-3.2ubuntu2.2) xenial; urgency=medium
* Fix: pam_tty_audit failed in pam_open_session (LP: #1666203)
-- Michael Hudson-Doyle <[email protected]> Thu, 01 Oct 2020
10:03:21 +1300
** Changed in: pam (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1659719
Title:
ssh can't call a binary from a snap without the full path
Status in Snappy:
Fix Committed
Status in livecd-rootfs package in Ubuntu:
Fix Released
Status in openssh package in Ubuntu:
Confirmed
Status in pam package in Ubuntu:
Fix Released
Status in livecd-rootfs source package in Xenial:
New
Status in openssh source package in Xenial:
Won't Fix
Status in pam source package in Xenial:
Fix Released
Status in livecd-rootfs source package in Bionic:
New
Status in openssh source package in Bionic:
Won't Fix
Status in pam source package in Bionic:
Fix Released
Status in livecd-rootfs source package in Focal:
New
Status in openssh source package in Focal:
Won't Fix
Status in pam source package in Focal:
Fix Released
Status in livecd-rootfs source package in Groovy:
Fix Released
Status in openssh source package in Groovy:
Confirmed
Status in pam source package in Groovy:
Fix Released
Status in openssh package in Debian:
New
Bug description:
[impact]
ssh can't call a binary from a snap, it will only work using the full path.
[test case]
Create a container. Install the go snap (and make sure golang-go is not
installed). Run "ssh <container-ip> go version" and check the binary is found.
[regression potential]
It's a pam change an they are always a bit scary but the code follows the
existing pattern for updating PATH in /etc/environment and has been tested in
groovy.
[original description]
Let's say I have the hello snap installed in 192.168.122.24. Then:
elopio@ubuntu-xenial:~/mosh$ ssh 192.168.122.24 hello
[email protected]'s password:
bash: hello: command not found
elopio@ubuntu-xenial:~/mosh$ ssh 192.168.122.24 /snap/bin/hello
[email protected]'s password:
Hello, world!
To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1659719/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : [email protected]
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
