[Bug 1659719] Re: ssh can't call a binary from a snap without the full path
Brian Murray
1659719 at bugs.launchpad.net
Tue Jul 28 17:45:44 UTC 2020
Hello Leo, or anyone else affected,
Accepted pam into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/pam/1.1.8-3.6ubuntu2.18.04.2 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
bionic to verification-done-bionic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-bionic. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: pam (Ubuntu Bionic)
Status: New => Fix Committed
** Tags added: verification-needed-bionic
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to openssh in Ubuntu.
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:
New
Status in pam source package in Xenial:
New
Status in livecd-rootfs source package in Bionic:
New
Status in openssh source package in Bionic:
New
Status in pam source package in Bionic:
Fix Committed
Status in livecd-rootfs source package in Focal:
New
Status in openssh source package in Focal:
New
Status in pam source package in Focal:
Fix Committed
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 at ubuntu-xenial:~/mosh$ ssh 192.168.122.24 hello
elopio at 192.168.122.24's password:
bash: hello: command not found
elopio at ubuntu-xenial:~/mosh$ ssh 192.168.122.24 /snap/bin/hello
elopio at 192.168.122.24's password:
Hello, world!
To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1659719/+subscriptions
More information about the foundations-bugs
mailing list