From: Nam Nguyen <namn@berkeley.edu>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: 32855@debbugs.gnu.org
Subject: bug#32855: sshuttle /usr/bin/env
Date: Sat, 29 Sep 2018 15:40:01 -0700 [thread overview]
Message-ID: <20180929224001.GA10179@antelope> (raw)
In-Reply-To: <87o9ciha1x.fsf@tobias.gr>
Hi Tobias,
After testing, I think the /bin/sh substitution introduced a regression.
Lines in question:
(substitute* "sshuttle/ssh.py"
;; Perhaps this is unreachable, but don't let's take risks.
(("/bin/sh") (which "sh")))
$ sshuttle -r user <at> server.com 0/0 -x server.com
ksh: /gnu/store/rb...-bash-minimal-4.4.19/bin/sh: not found
client: fatal: server died with error code 127
The server I am sshing to is not running GuixSD. It is trying to find
/gnu/store/.../bin/sh but it doesn't exst. My local client is running
GuixSD. The only requirements on the server side should be Python. Should
those lines should be removed? I tested without, and it seems to work okay,
at least for my particular setup: GuixSD client --> non-GuixSD server.
I suppose we have to state the assumptions of whether the client and
server are running Guix or not, and arrive at good defaults.
next prev parent reply other threads:[~2018-09-29 22:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-27 18:23 bug#32855: sshuttle /usr/bin/env Nam Nguyen
2018-09-27 19:11 ` Tobias Geerinckx-Rice
2018-09-27 19:22 ` Nam Nguyen
2018-09-27 22:04 ` Tobias Geerinckx-Rice
2018-09-29 22:40 ` Nam Nguyen [this message]
2018-09-30 11:52 ` Tobias Geerinckx-Rice
2018-09-30 14:45 ` Nam Nguyen
2018-10-06 14:19 ` Marius Bakke
2018-10-06 14:49 ` Tobias Geerinckx-Rice
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180929224001.GA10179@antelope \
--to=namn@berkeley.edu \
--cc=32855@debbugs.gnu.org \
--cc=me@tobias.gr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).