lsh-list@brennmeister.com writes:
Ok, I wasn't sure about what the tcpwrappers support exactly means. I thought it would be similar to compiling in an inetd compatibility mode, but thats obviously wrong.
Yes, it just brings in code to use tcpwrappers (which is basically the same thing as tcpserver, in library form (well, it comes as a separate program for usage with inetd too, see tcpd).
The primary reason for using tcpserver instead of tcpwrappers would be to have access control lists one place less.
Setting LDFLAGS="-lnsl" before configuring lsh with tcpwrappers support works. So thats a problem with the configure script? Shouldn't it work out all the libraries needed?
Yeah, it should (and AFAIK, it does so on all the boxes I have access to). In fact, it should have complained about it at the ./configure stage (sending me your config.log might help).
/Pontus