lsh-bugs May 2007

lsh-bugs@lists.lysator.liu.se

3 participants
4 discussions

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 02 May '07

02 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

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 May 2007