I know that work was done to ensure /snap/bin was in the default path
for systemd itself and that this should be inherited now by all units.
'systemd-path | grep search-binaries:' shows that it's there on my focal
system. 'sudo ps axewwww | grep sshd' also shows that it's set in the
PATH environment of the sshd parent processes. So I'm not sure what is
still resetting the PATH for noninteractive ssh sessions.
** Also affects: pam (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, 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 Committed
Status in openssh package in Ubuntu:
Confirmed
Status in pam package in Ubuntu:
New
Status in snapd package in Ubuntu:
Confirmed
Bug description:
ssh can't call a binary from a snap, it will only work using the full
path.
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
elopio@192.168.122.24's password:
bash: hello: command not found
elopio@ubuntu-xenial:~/mosh$ ssh 192.168.122.24 /snap/bin/hello
elopio@192.168.122.24'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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
