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
[Resend, first attempt wasn't sent to the list]
ludo@gnu.org (Ludovic Courtès) writes:
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².
I agree an lsh-2.2 update is needed. There are also compilation problems with the argp subdir and gcc-5, due to the changed inline semantics.
For nettle-3 and lsh-2.x, I'm considering doing the nettle3 update using dsa-compat.h instead, like in https://sources.debian.net/src/lsh-utils/2.1-7/debian/patches/nettle3.patch/
Unfortunately, I don't have too much hacking time, and I also have a Nettle release due soon. Co-maintainers welcome.
I have filed the paperwork needed to get my employer (since a few weeks back I'm at google, Stockholm) to disclaim copyright interest in lsh development I do. I already have a similar clearance for Nettle.
Regards, /Niels
Hi Niels!
nisse@lysator.liu.se (Niels Möller) skribis:
ludo@gnu.org (Ludovic Courtès) writes:
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².
I agree an lsh-2.2 update is needed. There are also compilation problems with the argp subdir and gcc-5, due to the changed inline semantics.
For nettle-3 and lsh-2.x, I'm considering doing the nettle3 update using dsa-compat.h instead, like in https://sources.debian.net/src/lsh-utils/2.1-7/debian/patches/nettle3.patch/
Either way is fine IMO.
Unfortunately, I don't have too much hacking time, and I also have a Nettle release due soon. Co-maintainers welcome.
I’m not volunteering ;-), but I guess that a minimal maintenance release fixing the build issues and upgrading the cipher suites would be enough. (I understand that it’s still quite a bit of work, but hopefully not as much as adding new features.)
Cheers, Ludo’.
ludo@gnu.org (Ludovic Courtès) writes:
but I guess that a minimal maintenance release fixing the build issues and upgrading the cipher suites would be enough.
Right, probably only a few days hacking, plus a bit of release administrivia.
Regards, /Niels
ludo@gnu.org (Ludovic Courtès) writes:
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².
I've spent the evening fixing the most important issues: nettle-3 (using Magnus' patch), gcc-5, and updated default ciphers. The new default cipher-list is trimmed down to aes256-ctr, aes128-ctr, 3des-cbc.
Testing highly appreciated. To try it out, use something like
git clone https://git.lysator.liu.se/lsh/lsh.git cd lsh git checkout lsh-2.0.4 # This is the stable branch ./.bootstrap ./configure make bootstrap make make check
Regards, /Niels