group.of.nepali.translators team mailing list archive

Thread
Date

[Bug 1659719] Re: ssh can't call a binary from a snap without the full path

To: group.of.nepali.translators@xxxxxxxxxxxxxxxxxxx
From: Brian Murray <1659719@xxxxxxxxxxxxxxxxxx>
Date: Wed, 28 Jul 2021 22:57:36 -0000
Reply-to: Bug 1659719 <1659719@xxxxxxxxxxxxxxxxxx>
Sender: noreply@xxxxxxxxxxxxx

** Changed in: openssh (Ubuntu)
       Status: Confirmed => Invalid

** Changed in: openssh (Ubuntu Groovy)
       Status: Confirmed => Won't Fix

-- 
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:
  Invalid
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:
  Won't Fix
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
  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