Balazs Scheidler <[EMAIL PROTECTED]> writes:
> I don't, but it could be either crypt or something like this. But I
> planned to put low-level pty allocation routines here. (and the poll
> emulation code is here anyway) so it can stay lib IMHO.
My intention with the separate lib and include directories is not to
have a place to hide particularly low-level or ugly code. Instead, the
idea is that these directories are independent from lsh, doing one
thing (symmetric crypto algorithms and hash functions), so that it can
be lifted out and used in other projects without doing a lot of
modifications and cleanup. Like I said before, I started bt copying
these diractories verbatim from the Pike distribution, and I'd like to
be able to copy them back at some later time.
I don't think low-level system dependent code belongs there. If things
like poll, pty, unix passwords, etc is separated from the main src
directory, they should live in one or more directories of their own.
sysdep/ or unix/ or something like that; not together with the
portable crypto code currently in lib.
> > Looks like it should do the job (although I think you are a little
> > hard to the letter 'O'). You could copy it to the configure.in as
>
> I don't think simple shell script is the language where you could mess too
> much with algorithm effectiveness. You glue some commands together, and
> use the results.
Ooops. I wasn't referring to efficiency, but simply to the missing O
in the word "SECND" ;-)
/Niels
