Subject | RE: [firebird-support] Tcp-wrapper support |
---|---|
Author | Helen Borrie |
Post date | 2007-02-21T22:47:33Z |
At 09:15 AM 22/02/2007, you wrote:
Reading about tcp wrapper (assuming that's what Rick means by
"tcp-wrapper"), it seems to do pretty much a combination of what you
can configure the Firebird server to do for itself and what you can
configure the tcp service to allow or deny.
It was a rather vague question: what do you want Firebird to do that
it's not doing already? Log requests? Control all accesses to the
server and auxiliary ports? Override keepalive? Something else?
./heLen
>Rick,Even Superserver, which manages its own attachment requests?
>
> > > Is Firebird compiled with tcp-wrapper support? If not, are there
> > plans
> > > for it to be?
>
>My reading on TCP Wrappers suggests that Firebird can already support
>TCP Wrappers since this functionality can be added via configuration
>changes to the inetd and xinetd services.
>
>The configuration changes ensure that TCP Wrappers are applied to all
>server services, including Firebird.
Reading about tcp wrapper (assuming that's what Rick means by
"tcp-wrapper"), it seems to do pretty much a combination of what you
can configure the Firebird server to do for itself and what you can
configure the tcp service to allow or deny.
It was a rather vague question: what do you want Firebird to do that
it's not doing already? Log requests? Control all accesses to the
server and auxiliary ports? Override keepalive? Something else?
./heLen