News for the 1.1.3 release:
Support for encrypted private keys (not tested).
The lshg gateway client works.
To use encrypted private keys, use the -c 3des option to lsh-writekey.
The lsh client should ask you for your passphrase when needed.
Decryption of host keys is not currently supported (and I don't think
that is terribly useful).
The lshg client supports most features of the ordinary lsh client,
except for remote forwarding with -R. To use lshg, first start an lsh
client with
lsh -G remote
or
lsh -G -N remote
That will create a unix domain socket in a directory in /tmp.
You can start new sessions and local (-L) forwardings by connecting
with lshg instead of lsh:
lshg remote
lshg will reuse the existing connection, so there's no need for key
exchange or user authentication. I expect lshg to be useful in many
(but not all) circumstances when you would otherwise have used
ssh-agent or fsh. For instance for remote CVS access.
This release is fairly untested. I think it has enough new features
over lsh-1.0.x that I think it's soon time for a feature freeze. So
please test it report the bugs you find.
There are two known problems:
* Data is sometimes lost when using lsh with cvs diff.
* Building in a separate directory doesn't quite work.
http://www.lysator.liu.se/~nisse/archive/lsh-1.1.3.tar.gz
ftp://ftp.lysator.liu.se/pub/security/lsh/lsh/1.1.3.tar.gz
Best regards,
/Niels
