Re: [policyd-users] chroot breaking name lookups

2007-07-25 Thread Antonio Querubin
On Wed, 25 Jul 2007, Benny Pedersen wrote: > On Wed, July 25, 2007 20:05, Antonio Querubin wrote: >>> Sure, if I could find out how to make it resolve this within the chroot.. >>> Any ideas ? >> Specify the address instead of the hostname for now? > > blacklist_dnsname and whitelist_dnsname does n

Re: [policyd-users] chroot breaking name lookups

2007-07-25 Thread Benny Pedersen
On Wed, July 25, 2007 20:05, Antonio Querubin wrote: >> Sure, if I could find out how to make it resolve this within the chroot.. >> Any ideas ? > Specify the address instead of the hostname for now? blacklist_dnsname and whitelist_dnsname does not work without working dns -- This message was

Re: [policyd-users] chroot breaking name lookups

2007-07-25 Thread Antonio Querubin
On Wed, 25 Jul 2007, Jan-Frode Myklebust wrote: > On 2007-07-24, Antonio Querubin <[EMAIL PROTECTED]> wrote: >> >> The above would add an IPv4 dependency back into the code because of >> gethostbyname(), inet_ntoa(), and struct in_addr. At some point in the >> future your MySQL server may have an

Re: [policyd-users] chroot breaking name lookups

2007-07-25 Thread Jan-Frode Myklebust
On 2007-07-24, Antonio Querubin <[EMAIL PROTECTED]> wrote: > > The above would add an IPv4 dependency back into the code because of > gethostbyname(), inet_ntoa(), and struct in_addr. At some point in the > future your MySQL server may have an IPv6 address. Sorry, didn't realize that. Would a g

Re: [policyd-users] chroot breaking name lookups

2007-07-24 Thread Antonio Querubin
On Tue, 24 Jul 2007, Jan-Frode Myklebust wrote: > I changed it to resolve the name once it reads it from the config file. > Now my completely empty CHROOT=/var/empty/policyd works fine. > > -- > --- generic.c.original 2007-07

Re: [policyd-users] chroot breaking name lookups

2007-07-24 Thread Jan-Frode Myklebust
On 2007-07-24, Cami Sardinha <[EMAIL PROTECTED]> wrote: > > The resolution could take place before the chroot() occurs. I changed it to resolve the name once it reads it from the config file. Now my completely empty CHROOT=/var/empty/policyd works fine. ---

Re: [policyd-users] chroot breaking name lookups

2007-07-24 Thread Cami Sardinha
Jan-Frode Myklebust wrote: > We run policyd v1.81 as user/group policyd, chroot to an empty > directory /var/empty/policyd/. But then policyd isn't able to > resolve my MYSQLHOST hostname. If I use ip-address it works fine. > > It complains: > > policyd: connecting to mysql database: >

[policyd-users] chroot breaking name lookups

2007-07-24 Thread Jan-Frode Myklebust
We run policyd v1.81 as user/group policyd, chroot to an empty directory /var/empty/policyd/. But then policyd isn't able to resolve my MYSQLHOST hostname. If I use ip-address it works fine. It complains: policyd: connecting to mysql database: policyd: mysql_real_connect(): Unkno