frustating error compiling openssh3.7p1--> checking for libwrap... configu error: *** libwrap missing

frustating error compiling openssh3.7p1--> checking for libwrap... configu error: *** libwrap missing

Post by nicole_lea » Sat, 20 Sep 2003 03:03:06


Hi,

I am not sure whether I am missing something here thats simple But I
put an hour and half and couldnt get past this. I have already
compiled and installed openssl with zlib.

I am trying to compile openssh3.7p1 with tcp wrappers. I have compiled
tcpd from Casper Dik's code. I copied libwrap.a and tcpd.h into
/usr/lib and /usr/local/include respectively and tried to do the
configure with

./configure --prefix=/usr/local/openssh-3.7p1
--sysconfdir=/etc/openssh-3.7p1 --with-tcp-wrappers

type libwrap.a
libwrap.a is /usr/lib/libwrap.a

type libwrap
libwrap is /usr/lib/libwrap

(I copied libwrap.a to libwrap as the error says its looking for
libwrap and not libwrap.a)

I dont understand why it cant use any one from /usr/lib.

Again I tried passing on the whole path after making a copy of libwrap
into /usr/local/lib

./configure --prefix=/usr/local/openssh-3.7p1
--sysconfdir=/etc/openssh-3.7p1 --with-tcp-wrappers=/usr/local/lib

But that doesnt get me any where as well. I had all these directories
in my path. I even tried compiling it with having
/tmp/tcpd/tcp_wrappers_7.6-ipv6(directory where I had all my wrapper
stuff in) in my path.

One more Q--> Is any one starting SSHD out of inetd.conf? How does
that work for you? If that doesnt work well or has some other issues I
can forget about this error and compile with out tcp wrappers option.

Any pointers/suggestions are truely appreciated.

Thanks a lot!
 
 
 

frustating error compiling openssh3.7p1--> checking for libwrap... configu error: *** libwrap missing

Post by Darren Dun » Sat, 20 Sep 2003 06:05:57


Hmm. You are aware that compiling with tcp wrapper support doesn't
require you to run it out of inetd, right?

--
Darren Dunham XXXX@XXXXX.COM
Unix System Administrator Taos - The SysAdmin Company
Got some Dr Pepper? San Francisco, CA bay area
< This line left intentionally blank to confuse you. >

 
 
 

frustating error compiling openssh3.7p1--> checking for libwrap... configu error: *** libwrap missing

Post by nicole_lea » Sat, 20 Sep 2003 13:56:23


Darren,

Yeah I understand that I can compile it with tcpwrapper support and
doesnt need to start sshd out of inetd. But will we be using the
tcpwrapper support we built into it if we were to start it as a start
up service from /etc/rc or /etc/init.d? I am not sure about that. If
yes I will get that worked to build with tcp-wrapper-support. May be I
have to tweak the configure script some how for it to find libwrap.a
and tcpd.h But I will be glad if some one can point me to the solution
 
 
 

frustating error compiling openssh3.7p1--> checking for libwrap... configu error: *** libwrap missing

Post by Darren Dun » Sun, 21 Sep 2003 02:25:01


Yes!

When done you can have it startup as a normal daemon, but it will still
honor any entries in /etc/hosts.{allow,deny}.

There are some folks running sshd out of inetd for a particular reason
or two, but it's not something I'd do on a normal server. It just takes
too much time to start up.
--
Darren Dunham XXXX@XXXXX.COM
Unix System Administrator Taos - The SysAdmin Company
Got some Dr Pepper? San Francisco, CA bay area
< This line left intentionally blank to confuse you. >
 
 
 

frustating error compiling openssh3.7p1--> checking for libwrap... configu error: *** libwrap missing

Post by nicole_lea » Sun, 21 Sep 2003 05:29:51


I had tcpd.h in /usr/lib/include and libwrap in /usr/lib. It was
finding libwrap but it wasnt finding tcpd.h(though I gave
--with-tcp-wrappers=/usr/lib:/usr/lib/include). I copied tcpd.h into
/usr/lib and ran it and it worked fine. But still It should compain
about missing tcpd.h and not libwrap. Any way just wanted to post
back.
 
 
 

frustating error compiling openssh3.7p1--> checking for libwrap... configu error: *** libwrap missing

Post by Darren Dun » Sun, 21 Sep 2003 06:02:38


/usr/lib/include? Shouldn't that be /usr/include?

--
Darren Dunham XXXX@XXXXX.COM
Unix System Administrator Taos - The SysAdmin Company
Got some Dr Pepper? San Francisco, CA bay area
< This line left intentionally blank to confuse you. >
 
 
 

frustating error compiling openssh3.7p1--> checking for libwrap... configu error: *** libwrap missing

Post by Richard E. » Tue, 23 Sep 2003 12:44:55

>>>>> "DD" == Darren Dunham < XXXX@XXXXX.COM > writes:

DD> There are some folks running sshd out of inetd for a particular
DD> reason or two, but it's not something I'd do on a normal server.
DD> It just takes too much time to start up.

I think this is mostly an issue if you're supporting protocol 1, since
sshd has to generate the PFS ("server") key every time. I don't think
there's any big reason to prefer standalone operation if you're supporting
only protocol 2.

--
Richard Silverman
XXXX@XXXXX.COM