lsh-bugs December 2015

lsh-bugs@lists.lysator.liu.se

3 participants
5 discussions

/etc/environment not honored by lshd
by ludo＠gnu.org 15 Dec '15

15 Dec '15

Hello! Somehow /etc/environment isn’t honored when logging in via SSH to an lshd server running on GuixSD, despite the fact that /etc/pam.d/lshd has this: --8<---------------cut here---------------start------------->8--- account required pam_unix.so auth required pam_unix.so password required pam_unix.so sha512 shadow session required pam_env.so session required pam_unix.so --8<---------------cut here---------------end--------------->8--- Ludo’.

2 2

Re: Time for an lsh release
by nisse＠lysator.liu.se 11 Dec '15

11 Dec '15

ludo(a)gnu.org (Ludovic Courtès) writes: > (This is due to the Guix setup where by default nothing would be found > in $PATH; patch attached. That's a pretty non-standard environment... Processes spawned for a user by lshd get a pretty trimmed down initial environment, with PATH set to /bin:/usr/bin or something close. If standard unix tools aren't found there, then I think you'd need to either * have the shell startup files setup a working path (ssh "shell" is implemented by spawning a login shell, and "exec" by starting a shell with -c command-line-string). * Or some option to lshd to let child processes inherit PATH or set it to a specific value. Not sure if it's appropriate to use that when running the tests, though. There's a related hack to inherit HOME in some circumstances. Regards, /Niels -- Niels Möller. PGP-encrypted email is preferred. Keyid C0B98E26. Internet email is subject to wholesale government surveillance.

2 4

lsh cannot forward UNIX domain sockets
by Thompson, David 10 Dec '15

10 Dec '15

Hello! I'm new to lsh. Lshd is the default SSH server on GuixSD, and so I found myself using it over OpenSSH. However, I found that I cannot use the port forwarding features with UNIX domain sockets. I'm used to being able to do this as the OpenSSH server supports it. It would be really great to add this feature. Any estimate on how much work it would involve or other thoughts? Thanks! - Dave

2 1

Re: Time for an lsh release
by nisse＠lysator.liu.se 03 Dec '15

03 Dec '15

ludo(a)gnu.org (Ludovic Courtès) writes: > … I’m getting test failures: > lsh, test 1 > Closed spurious fd 10 > Closed spurious fd 5 > FAIL: lsh-1 It seems all tests actually trying to make a connection fails. To find out how it fails, you can try adding a set -x in the lsh-1-test script, and/or add -v or even --debug to LSH_FLAGS when running the tests. Or try running the newly built lsh client manually, to see if it's a client or server problem. Regards, /Niels -- Niels Möller. PGP-encrypted email is preferred. Keyid C0B98E26. Internet email is subject to wholesale government surveillance.

1 0

Time for an lsh release
by ludo＠gnu.org 01 Dec '15

01 Dec '15

Hi! I realize my previous message¹ went unanswered: OpenSSH 6.7 removed all CBC, among others, from its default cipher suites (see <http://www.openssh.com/txt/release-6.7>.) As a consequence, the SSH client from lsh 2.1 cannot connect to a recent OpenSSH server by default. Instead, one needs to pass ‘-c aes256-ctr’, which is one of the few ciphers in common. I think it would make sense to make a new lsh release that would at least change the default set of cipher suites to follow what OpenSSH did. WDYT? I think this is one of the things urgently needed if we want to allow people to keep using lsh/lshd, along with applying the Nettle 3 upgrade patch². Thanks, Ludo’. ¹ http://lists.lysator.liu.se/pipermail/lsh-bugs/2015q3/000664.html ² http://lists.lysator.liu.se/pipermail/lsh-bugs/2015q3/000662.html

2 4

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

lsh-bugs December 2015