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
nisse@lysator.liu.se (Niels Möller) writes:
I was reminded that it would be good with a maintenance release of lsh. Things to do for an lsh-2.0.5:
I think it has to be lsh 2.1.
- Upgrade to recent autoconf and automake (to fix the distcheck security problem in Makefiles generated by earlier automake).
Done.
- Backport any portability fixes from the development branch, to make it compile and work on current systems.
Fixed some things: Replaced mini-inetd/tcpconnect with versions supporting IPv6, and an issue with ut_tv entry in struct utmp.
- Upgrade the license to GPLv3.
Not done, but should be fairly straightforward, replace "COPYING", replace "2" by "3" in (C) headers, update any mention of the license in documentation.
- Delete the bundled nettle library (to avoid shipping an ancient version of nettle), and do any fixes needed to work with recent nettle.
Done.
Anything else, e.g., any debian patches that should be integrated?
There are some debian patches which aren't yet applied, the largest one being support for a publickey blacklist. (See http://patch-tracker.debian.org/package/lsh-utils/2.0.4-dfsg-11).
Regards, /Niels