On Thu, Jun 27, 2002 at 10:21:20AM -0400, Prentis Brooks wrote: > Ok, I was basing my response on the info I got from Charles, where he > pointed out that libwrap declares certain ints as extern, leaving tcpd > and ssh to define them. I am not familiar with DLL's so I am going > solely by what he says, which I expect is accurate considering the work > he has already done. According to his email, these externally defined > ints work fine when linked statically, but not in a DLL. He suggested > that I go through and change the libwrap library to define these > variable and export them to the applications. Once that is done, I have > to go through the applications and stop them from declaring these > variables themselves (this is the part where I do a lot of reading). > > Regarding changes to ssh, that is based on the assumption that ssh, like > tcpd, declares these ints itself and would need similiar edits to work > with the DLL. Regarding the inetd, I was actually talking about making > the edits to tcpd and using inetd to test the functionality, since that > is the only other place I have used tcpwrap other than in SSH. > > Does that clarify or have I muddied the water further?
It clarifies. I was just confused how inetd comes into play here. Just consider that if the usage of a tcp wrappers dll actually requires us to change sshd code, I'd better live with static linking. libwrap.a isn't that big. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:[EMAIL PROTECTED] Red Hat, Inc.
