lsh-bugs

lsh-bugs@lists.lysator.liu.se

491 discussions

IPv6 link local
by Sylvain BERTRAND 19 Dec '14

19 Dec '14

Hi, me again. Is there a way to tell lsh about the interface to use when using a link local IPv6 address? For instance an --interface option or IPV6%iface syntax. best regards, -- Sylvain

2 4

git server changes
by nisse＠lysator.liu.se 08 Jun '14

08 Jun '14

Lysator's git server, git.lysator.liu.se, is about to be replaced. New server will run gitlab software instead of the current gitorious. Nettle and LSH repos (as well as other repos I have there) will move, but they may be temporarily unavailable in the weekend or next week. Don't panic. I'll send another mail once everything is ready at the new server. Intention is that git urls will be unchanged. Regards, /Niels -- Niels Möller. PGP-encrypted email is preferred. Keyid C0B98E26. Internet email is subject to wholesale government surveillance.

1 2

lshg fails when passed data on stdin
by ludo＠gnu.org 06 Mar '14

06 Mar '14

Hi, lshg/lsh (as of lsh 2.1 on GNU/Linux, x86_64) systematically fails for me when passed large data streams on stdin: --8<---------------cut here---------------start------------->8--- $ lsh -G -B fencepost.gnu.org Passphrase for key `xxx@yyy': $ lshg fencepost.gnu.org uname -o GNU/Linux $ cat /dev/zero | lshg fencepost.gnu.org md5sum lsh: Protocol error: Write buffer full, peer not responding. lsh: write_buffer: Attempt to write data to closed buffer. lsh: Protocol error: Write buffer full, peer not responding. lsh: write_buffer: Attempt to write data to closed buffer. [...] lsh: Protocol error: Write buffer full, peer not responding. lshg: write_buffer: Attempt to write data to closed buffer. $ killall lsh lsh: no process found --8<---------------cut here---------------end--------------->8--- Conversely, this works well: --8<---------------cut here---------------start------------->8--- $ cat /dev/zero | lsh fencepost.gnu.org md5sum --8<---------------cut here---------------end--------------->8--- Any idea what’s wrong or how to debug it? Thanks, Ludo’.

2 4

‘lshg -G’ aborts
by ludo＠gnu.org 23 Jan '14

23 Jan '14

Hi again, As of lsh 2.1, I get this: --8<---------------cut here---------------start------------->8--- $ lshg -G fencepost.gnu.org Passphrase for key `xxx@yyy': Aborted --8<---------------cut here---------------end--------------->8--- A look at the strace output suggests an assertion failure in one of the child processes: --8<---------------cut here---------------start------------->8--- write(2, "lshg: sys.c:109: sys_on_fd: Assertion `((void *)0) == sys->files[fd][ev].f && \"multiple handlers registered for a file event\"' failed.\n", 135) = 135 --8<---------------cut here---------------end--------------->8--- Any ideas? Thanks, Ludo’.

2 7

ANNOUNCE: lsh-2.1
by nisse＠lysator.liu.se 26 Jun '13

26 Jun '13

I'm happy to announce a new release of GNU lsh, an implementation of the secure shell protocols. This is a maintenance release, with no new features. News for the 2.1 release No longer includes the Nettle library; GNU Nettle has to be installed separately. At least version 2.2 is needed. Available at ftp.gnu.org. Includes several improvements from debian maintainer Magnus Holmgren: * Make lsh exit properly on connection failure. * Improved lsh error message when seed file doesn't exist. * Make lshd set the IPV6_V6ONLY option when binding IPv6 sockets. Uses a more recent version of automake, avoiding a vulnerability in the automake-generated distcheck target. Use service name "lshd" in lsh-pam-checkpw (patch from Ludovic Courtès). Fixed an utmp-related build problem on GNU/Linux x86_64. Testsuite includes new versions of tcpconnect and mini-inetd, which work better with IPv6. Available at ftp://ftp.gnu.org/gnu/lsh/lsh-2.1.tar.gz. Development of LSH have seen slow progress in recent years, for various reasons. I'm working towards lsh-3.0, and users and developers are encouraged to check out the development version. The client side of the development version is pretty solid, I'm using it daily since a long time. The server side has seen less testing. An (old) summary of differences between 2.x and the development version can be found at http://lists.lysator.liu.se/pipermail/lsh-bugs/2007q2/000598.html, and a list of important things that remain to do is maintained at http://www.lysator.liu.se/~nisse/lsh/plan.html. I'd be happy to see a new co-maintainer or maintainer for LSH, to help move the project forward. Please mail me if you are interested. Non-maintainer contributions are of course also welcome. The LSH homepage, http://www.lysator.liu.se/~nisse/lsh/, includes information about the psst mailinglist, the public git repoitory, as well as the online manual. Happy hacking, /Niels Möller -- Niels Möller. PGP-encrypted email is preferred. Keyid C0B98E26. Internet email is subject to wholesale government surveillance.

1 0

[PATCH] bootstrap: Remove bundled nettle references
by David Michael 04 Jun '13

04 Jun '13

--- Hi, I have built lsh from git to use the system's nettle, but the bootstrap script fails since the bundled nettle was removed. Can something like this be applied? Thanks. David .bootstrap | 23 ++++++----------------- 1 file changed, 6 insertions(+), 17 deletions(-) diff --git a/.bootstrap b/.bootstrap index 24ca101..fd57f56 100755 --- a/.bootstrap +++ b/.bootstrap @@ -28,7 +28,6 @@ relative_symlink() { relative_symlink misc/run-tests \ src/testsuite src/argp/testsuite \ - src/nettle/testsuite src/nettle/examples \ src/sftp/testsuite src/spki/testsuite relative_symlink acinclude.m4 \ @@ -37,29 +36,19 @@ relative_symlink acinclude.m4 \ relative_symlink misc/vsnprintf.c \ src/argp src/sftp -relative_symlink misc/getopt.c \ - src/nettle/examples src/nettle/tools src/spki/tools -relative_symlink misc/getopt1.c \ - src/nettle/examples src/nettle/tools src/spki/tools -relative_symlink misc/getopt.h \ - src/nettle/examples src/nettle/tools src/spki/tools - -(cd src/nettle && ln -s ../../acinclude.m4 aclocal.m4 || true) - -relative_symlink config.guess src/nettle src/spki -relative_symlink config.sub src/nettle src/spki +relative_symlink misc/getopt.c src/spki/tools +relative_symlink misc/getopt1.c src/spki/tools +relative_symlink misc/getopt.h src/spki/tools -relative_symlink install-sh src/nettle -relative_symlink texinfo.tex src/nettle -relative_symlink INSTALL src/nettle -relative_symlink COPYING src/nettle +relative_symlink config.guess src/spki +relative_symlink config.sub src/spki if [ "$1" = "links" ] ; then # Skip the time consuming autoconf and automake stuff exit 0; fi -for subdir in src/argp src/nettle src/sftp src/spki ; do +for subdir in src/argp src/sftp src/spki ; do (cd $subdir && ./.bootstrap) done -- 1.8.1.4

2 1

git.lysator.liu.se temporarily down
by nisse＠lysator.liu.se 30 May '13

30 May '13

The machine git.lysator.liu.se is being upgraded to a more recent debian version. Not sure when it will be operational again (it's maintained on a volunteer basis), but hopefully within a day or two. Possibly the gitorious web interface will be replaced by something different (gitolite, gitlab, ...), since gitorious seems to require quite a bit of work to install. Sorry for the inconvenience. Regards, /Niels -- Niels Möller. PGP-encrypted email is preferred. Keyid C0B98E26. Internet email is subject to wholesale government surveillance.

1 0

Coming maintenance release?
by nisse＠lysator.liu.se 03 Apr '13

03 Apr '13

I was reminded that it would be good with a maintenance release of lsh. Things to do for an lsh-2.0.5: 1. Upgrade to recent autoconf and automake (to fix the distcheck security problem in Makefiles generated by earlier automake). 2. Backport any portability fixes from the development branch, to make it compile and work on current systems. I'm also considering 3. Upgrade the license to GPLv3. 4. Delete the bundled nettle library (to avoid shipping an ancient version of nettle), and do any fixes needed to work with recent nettle. Anything else, e.g., any debian patches that should be integrated? Regards, /Niels -- Niels Möller. PGP-encrypted email is preferred. Keyid C0B98E26. Internet email is subject to wholesale government surveillance.

1 1

Re: Coming maintenance release?
by nisse＠lysator.liu.se 29 Mar '13

29 Mar '13

ludo(a)gnu.org (Ludovic Courtès) writes: > nisse(a)lysator.liu.se (Niels Möller) skribis: > >> I had fixed the guile support already, but I'll add the other two. >> Thanks! > > Great. Checked in now (on the lsh-2.0.4 branch). Regards, /Niels -- Niels Möller. PGP-encrypted email is preferred. Keyid C0B98E26. Internet email is subject to wholesale government surveillance.

1 0

Re: Coming maintenance release?
by nisse＠lysator.liu.se 14 Mar '13

14 Mar '13

ludo(a)gnu.org (Ludovic Courtès) writes: > In Guix we have 3 tiny patches; see lsh-*.patch at > <http://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/patches/>. I had fixed the guile support already, but I'll add the other two. Thanks! Should I credit the fixes to you, or did you get them from someone else? Regards, /Niels -- Niels Möller. PGP-encrypted email is preferred. Keyid C0B98E26. Internet email is subject to wholesale government surveillance.

1 0

Jump to page:

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