lsh-bugs

lsh-bugs@lists.lysator.liu.se

494 discussions

can't connect to lshd using midpssh
by Christiaan Welvaart 26 Jun '07

26 Jun '07

hi, When I try to initiate a session using MidpSSH [1] I get: Protocol error: No common hostkey algorithm.^M What could be causing this, or how can I debug the problem? >From the source code and the RFC I see that the hostkey algorithm is pretty much always ssh-dss, so maybe the real problem is somehwere else. I'm using lshd 2.0.3 . Christiaan [1] http://www.xk72.com/midpssh/ - version 1.6.0

2 1

Can't get X forwading working
by Kaloian Doganov 05 Jun '07

05 Jun '07

(I'm not sure whether this mailing list the apropriate place to report bugs or problems with GNU lsh. If it is not, please point me to the right place.) Using GNU lsh 2.9-exp to login on a remote host ("mafra", running OpenSSH server with X11 forwarding enabled, of course), I end up with no DISPLAY environment variable on the remote host: --------------------8<-------------------- $ /usr/local/bin/lsh --x11-forward --verbose mafra.doganov.org lsh: Enabling default escape character `~' lsh: Could not open gateway: (errno = 2): No such file or directory lsh: Starting /usr/local/bin/lsh-transport. Passphrase for key `kaloian@millenium-falcon': lsh-transport: Connecting to mafra.doganov.org:22.... lsh-transport: ... connected. lsh-transport: Server version string: SSH-2.0-OpenSSH_4.3p2 Debian-9 lsh-transport: Received KEXINIT message. Key exchange initated. lsh-transport: Selected keyexchange algorithm: diffie-hellman-group14-sha1 with hostkey algorithm: ssh-rsa lsh-transport: Selected bulk algorithms: (client to server, server to client) Encryption: (aes256-cbc, aes256-cbc) Message authentication: (hmac-sha1, hmac-sha1) Compression: (none, none) lsh-transport: SPKI host authorization successful! lsh-transport: Requesting authentication using the `publickey' method. lsh-transport: Received USERAUTH_SUCCESS. lsh: Allocated local channel number 0 lsh: pty request succeeded Linux mafra 2.6.18-4-686 #1 SMP Wed May 9 23:03:12 UTC 2007 i686 The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. Last login: Sun Jun 3 22:52:11 2007 from 141.201.pppoe.intech.bg kaloian@mafra:~$ echo $DISPLAY kaloian@mafra:~$ --------------------8<-------------------- The same example case goes a little further when I try to execute it with GNU lsh 2.0.3: --------------------8<-------------------- $ /usr/local/bin/lsh --x11-forward --verbose mafra.doganov.org lsh: Enabling default escape character `~' lsh: Using local X11 transport `/tmp/.X11-unix/X0' Passphrase for key `kaloian@millenium-falcon': lsh: garbage collecting... lsh: Objects alive: 88, garbage collected: 24 lsh: Client version: SSH-2.0-lsh-2.0.3 lsh - a GNU ssh Server version: SSH-2.0-OpenSSH_4.3p2 Debian-9 lsh: Received KEXINIT message. Key exchange initated. lsh: Selected keyexchange algorithm: diffie-hellman-group14-sha1 with hostkey algorithm: ssh-rsa lsh: Selected bulk algorithms: (client to server, server to client) Encryption: (aes256-cbc, aes256-cbc) Message authentication: (hmac-sha1, hmac-sha1) Compression: (none, none) lsh: SPKI host authorization successful! lsh: Received NEWKEYS. Key exchange finished. lsh: Setting session key lifetime to 2400 seconds lsh: Requesting authentication using the `none' method. lsh: Requesting authentication using the `publickey' method. lsh: Requesting authentication using the `publickey' method. lsh: SSH_MSG_USERAUTH_PK_OK received lsh: Sending `publickey' signature. lsh: User authentication successful. lsh: Allocated local channel number 0 lsh: Registering local channel 0. lsh: Taking channel 0 in use, (local 0). lsh: Requesting a remote pty. lsh: Requesting X11 forwarding. lsh: pty request succeeded lsh: X11 request succeeded Linux mafra 2.6.18-4-686 #1 SMP Wed May 9 23:03:12 UTC 2007 i686 The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. Last login: Sun Jun 3 22:52:22 2007 from 141.201.pppoe.intech.bg kaloian@mafra:~$ echo $DISPLAY localhost:10.0 kaloian@mafra:~$ xclock lsh: Allocated local channel number 1 lsh: x11 connection attempt, originator: 127.0.0.1:50836 lsh: Registering local channel 1. lsh: Taking channel 3 in use, (local 1). --------------------8<-------------------- xclock hangs forever at this point and xclock's window is not displayed on the X server. The same test with openssh -X leads to xclock's window actually displayed on the X server. -- Protect your digital freedom and privacy, eliminate DRM, learn more at http://www.defectivebydesign.org/what_is_drm

2 2

Re: Converting private key from OpenSSH to lsh (or the other way around)
by nisse＠lysator.liu.se 04 Jun '07

04 Jun '07

Simon Josefsson <simon(a)josefsson.org> writes: > If it would help someone, there is code in libssh2 that I wrote which > decodes unencrypted OpenSSL private keys (which apparently is what > OpenSSH is using) and imports them into a libgcrypt sexp. Does openssl and openssh use the PKCS#1 format for private keys, as the DER encoding of ASN.1 objects? (Maybe that spec is for RSA keys only, but if so there ought to be some related spec for DSA). I would have expected openssh to use something closer to the ssh wireformat, i.e., the wireformat ssh-rsa/ssh-dsa with some additional felds for the secret information, like I think the old proprietary ssh program did. For PKCS#1 format, the program pkcs1-conv (from nettle-1.14 and later) can also convert RSA keys in pkcs#1 formats to sexp format. Regards, /Niels

3 5

Converting private key from OpenSSH to lsh (or the other way around)
by Kaloian Doganov 31 May '07

31 May '07

Hello, GNU lsh hackers! I would like to try out lsh, but I'm currently stuck with a problem: in the real world I authenticate to most of my remote hosts via a public key. Is there any chance to convert my current OpenSSH key to a format, usable by lsh? I know there is no an authomatic tool for doing that, but I would do it manually if there is a known method of doing it. If not, is there a way to convert a key pair in the opposite direction -- from lsh to OpenSSH format? If there is, I can simply generate a new key pair with lsh and use it both with lsh and OpenSSH. -- Protect your digital freedom and privacy, eliminate DRM, learn more at http://www.defectivebydesign.org/what_is_drm

2 1

Re: File names with white spaces and `lcp'
by nisse＠lysator.liu.se 03 May '07

03 May '07

ludo(a)chbouib.org (Ludovic Courtès) writes: > Besides, it'd be nice to have a `-r' option, but that would require > sophisticated shellology... ;-) I don't think it would have to be so complicated. One could use something along the lines lsh host tar cf - $dir | tar xf - I do that manually from time to time. But one should probably create the archive with filenames that are relative to $dir. > PS: Is there any reason why http://www.gnu.org/software/lsh/ doesn't > exist? No good reason, I think. I'm just not familiar at all with the GNU web infrastructure. http://www.gnu.org/software/gmp gives a redirect to the gmp homepage. Something similar would make sense for software/lsh. Regards, /Niels

1 0

Re: File names with white spaces and `lcp'
by nisse＠lysator.liu.se 02 May '07

02 May '07

ludo(a)chbouib.org (Ludovic Courtès) writes: > The trivial patch below allows `lcp' to cope with file names containing > white spaces. > -file=`basename $src_file` > +file="`basename "$src_file"`" Thanks. Checked in now. I'm afraid lcp still doesn't do the right thing with file names containing quotes (the quote function, used when constructing the remote command line, doesn't handle all cases). Regards, /Niels

1 0

ANNOUNCE: lsh-2.9-exp
by nisse＠lysator.liu.se 05 Apr '07

05 Apr '07

Long time, no release... I've been using the client part of the new experimental branch for a couple of weeks now, so I think it's time. News for the 2.9-exp release This is not a regular release, it's the current state of the development version. "exp" for "experimental". New things: * Server split into three main programs; lshd, lshd-userauth and lshd-connection, to reduce the amount of code that is running with root privileges. * The server programs use configuration files, in addition to the command line options. * Client split into two programs, lsh and lsh-transport. By default, lsh tries to use a gateway, and lshg is just a shell script that invokes lsh with options to make it unconditionally use a gateway, or fail if none is present. Missing features and known problems: * The server in the current version will not listen on anything but localhost. I don't recommend using the server in this version for anything but testing. * Server supports publickey authentication only. * Internal flow-control is not fully implemented. Programs may exit (in a controlled fashion) if some channel or socket is overwhelmed with data. * Client does not support any escape key. * PTY support, using the lshd-pty-helper program, has some portability problems. * The manual is not up-to-date. Interfaces, including the syntax of the configuration files and the protocols used for communication betwen the various processes, may change in the next version of lsh. Available at http://www.lysator.liu.se/~nisse/archive/lsh-2.9-exp.tar.gz ftp://ftp.lysator.liu.se/pub/security/lsh/lsh-2.9-exp.tar.gz Happy hacking, /Niels

1 0

ANNOUNCE: lsh-2.0.3
by nisse＠lysator.liu.se 09 May '06

09 May '06

Another bugfix release, this time properly signed. News for the 2.0.3 release At startup, lshd now tries to close any spurious open file descriptors. New test case for lshd fd leakage. lshd --daemonic --no-syslog now sets up a proper daemonic environment, except that log messages are still sent to stderr. Improved testing of this feature. Available at http://www.lysator.liu.se/~nisse/archive/lsh-2.0.3.tar.gz ftp://ftp.lysator.liu.se/pub/security/lsh/lsh-2.0.3.tar.gz Regards, /Niels

1 0

(no subject)
by 胡涛 22 Feb '06

22 Feb '06

贵公司您好: 你好！现我公司可提供代开以下发票服务，点数优惠，所开发票贵公司可在税务局或网上验证后付款。欢迎来电咨询，谢谢！ <广州市南华贸易有限公司 > 1、商品销售发票 2、广告发票 3、运输发票 4、工业发票 5、建筑安装发票联系人：胡涛联系电话：13826450808 020-33622266 电子信箱：abnewkoko(a)avl.com.cn

2 1

increase in sexual desire
by Ella Lindsey 21 Feb '06

21 Feb '06

Carefully chosen herbal ingredients are the key to peniis enlargement success. Not only the precise blend of ingredients but also many other factors have effect on the overall potency and strength of peniis enlargement formula. Some of these factors include growing conditions, geographical location where herbs are grown, harvest time, the way herbs are stored before processing, the way herbs are processed. http://ackmbhif.greenmatis.info/?degjlfxwqowyackmzppbhi 0o

1 0

← Newer
1
2
3
4
5
6
7
...
50
Older →

Jump to page:

2026

2025

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