IP Whitelist

me too. We monitor the DA port via nagios and don't want to give false errors from that IP.
 
Last edited:
Bug Report

There's a bug.

My IP is added to ip_blacklist.
but if the file ip_whitelist exists, even its empty, I could enter DA without any problem. If I delete ip_whitelist, I couldnt enter DA then.
 
Hello,

I'm not able to duplicate that condition.. if the ip_blacklist has my ip, and the ip_whitelist is empty, I'm blocked. If the ip_whitelist is gone, also blocked.

Anoyone else getting the error? I'm not seeing it on my end.

John
 
I am seeing the same thing. If ip_whitelist exists it is like the blacklist function is totally non existant. I am using freebsd 6.1.

It will totally ignore ip_blacklist if all you do is:

touch /usr/local/directadmin/data/admin/ip_whitelist
 
see programmer's expression manual for basic AND/OR/TRUE/FALSE evaluation with defined and undefined variables.
Could help a lot...
 
Hello,

Thanks for the info guy, except xemaps, no soup for you ;)

I found the problem, the logic in the code is fine, it's just a permission error. There is a "check if path exists", then read in the files, but after the file (if exist) are read in, the read-in permission is set to "nobody". The initial "give me root" was then gone if the whitelist is checked, so "nobody" reading the blacklist can't see it, thus the list was essentially not there (which is valid.. a non-existant file is allowed).

The reason my intial test didn't find it is because the permissions on my admin folder are world readable. I tested on our freebsd 6.0 system which has tigher permissions, so I was able to see it ;)

I'll make another release with the fix.

John
 
well if no permission, this is the logic...
This post is right.
no soup for yourself cheers John ;)
 
um.... do we have to set permissions ourselves on the ip_whitelist file?

I had to create the file after the new update - never looked to see if it was there previously.

cheers
Nath.
 
You must log in or register to reply here.
Back
Top