login code in a separate library?

[Andre Lucas]

Following on from an earlier discussion about login recording, I was
toying with the idea of breaking out the login code into a separate
library (in a subdirectory of the OpenSSH source tree) with its own
configure script.

I think this would serve three purposes: First, it would in the long run
remove a lot of things from OpenSSH's configure script that, save for
the login code, needn't be there; second, it would more readily allow
parallel development so that people don't try OpenSSH-1.3pre1 (or
2.0pre1, or whatever) and suddenly lose all their utmp etc.

Third, it ties in with what Damien was saying before about this being a
way for approaching this problem in other projects. I think it may make
some people happy to have an autoconf/automake login library ready to
plug in.

I'm able to test on only four platforms, but the idea - David Rankin was
right to make this point - is to have enough generality to detect new
platforms on its own. I think that the best way to get this right is to
separate the admin function of recording a login from SSH's security
functionality.

I'm hoping to get this ready for inclusion in the next round of test
releases (i.e. after 1.2.1).

Ta,
-Andre

-- 
Andre Lucas <andre.lucas at dial.pipex.com>
http://dspace.dial.pipex.com/andre.lucas/