"J.H.M. Dassen (Ray)" <[EMAIL PROTECTED]> writes:
> Do you have any concrete suggestions for how to organise things? I'm
> currently doing some minor things (attempt to incorporate GPG's Blowfish
> code; cleaning up against more warnings (constness, signedness); listing
> some TODO stuff I notice) etc.
As far as general suggestions go: Please tell me early what you want
to work on. I also think it's a good idea to send me patches quite
early, so that we don't get too much out of sync.
One sub-project is to create a non-gpg-specific low-level crypto
library from the GPG code (and, if anything there is useful, the lib/
subdirectory of lsh). GPG and lsh needs different interfaces to these
functions, but they should be able to use the same implementations.
Other mostly orthogonal sub-projects are: Configuration (including
reading appropriate config files and better command line options),
better user authentication methods than passwords, key generation and
general key management, a decent source of random bits (using
/dev/random if available, with a reasonably good fallback), ...
Currently I'm working on the gc and object-system. Unfortunately, this
means some changes to many parts of lsh. But it has to be done, and
the sooner the better.
> Perhaps you can set up a CVS server for lsh?
There are a few options here:
� I could easily provide a read-only http-interface to my cvs
repository (I have done this for other projects, for instance <URL:
http://www.lysator.liu.se/~nisse/scheme/.>).
� It may be possible to create guest accounts at lysator, on an
individual basis. That would give convenient read-only or read-write
access.
� I could create a daily mirror on Idonex's anonymous cvs server
(accessible with CVS_RSH=ssh cvs -d [EMAIL PROTECTED]:/cvs,
password "anonymous").
I'm not very familiar with the pserver-feature of cvs, but my
impression is that it is not very secure.
Do have any suggestions here?
/Niels
