SYSTEM WARNING: 'date_default_timezone_get(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone.' in '/usr/share/mantis/www/core.php' line 264

0000156: Havp Whitelist are not applied to havp conf - MantisBT
MantisBT - Endian Firewall
View Issue Details
0000156Endian FirewallApplication Level Proxiespublic2007-04-05 09:322009-10-27 12:01
buzzzo 
simon-endian 
normalminoralways
closedfixed 
2.1 
2.3 
0000156: Havp Whitelist are not applied to havp conf
When i save an havp whitelist tru web gui it will be saved on /var/efw/havp/whitelist , but it seems that the python script doesn't write
the whitelist on /etc/havp .

So the result is that havp doesn't use the whitelist provided from the web gui .

Is it a bug ?

Thx
needsfix
Issue History
2007-04-05 09:32buzzzoNew Issue
2007-04-12 17:54peter-endianNote Added: 0000279
2007-04-12 17:54peter-endianStatusnew => feedback
2007-04-16 08:38buzzzoNote Added: 0000287
2007-04-24 21:30detlefNote Added: 0000293
2007-05-08 16:38buzzzoNote Added: 0000315
2007-05-10 15:32peter-endianStatusfeedback => resolved
2007-05-10 15:32peter-endianResolutionopen => fixed
2007-05-10 15:32peter-endianAssigned To => peter-endian
2007-05-10 15:32peter-endianNote Added: 0000317
2007-07-11 09:01peter-endianStatusresolved => closed
2008-11-04 13:01luca-endianNote Added: 0001767
2008-11-04 13:01luca-endianStatusclosed => feedback
2008-11-04 13:01luca-endianResolutionfixed => reopened
2008-11-04 13:02luca-endianStatusfeedback => confirmed
2008-11-04 16:42peter-endianTag Attached: needsfix
2008-11-04 16:42peter-endianStatusconfirmed => new
2008-11-04 16:42peter-endianAssigned Topeter-endian => simon-endian
2008-11-04 16:42peter-endianStatusnew => confirmed
2008-11-21 16:58simon-endianNote Added: 0001822
2008-11-21 16:58simon-endianStatusconfirmed => resolved
2008-11-21 16:58simon-endianFixed in Version => 2.3
2008-11-21 16:58simon-endianResolutionreopened => fixed
2009-10-27 12:01peter-endianStatusresolved => closed

Notes
(0000279)
peter-endian   
2007-04-12 17:54   
in havp.conf the place for the whitelist is set to /etc/havp/whitelist, which is a symbolic link to /var/efw/havp/whitelist, so this should not be a problem.
try to open /etc/havp/whitelist with an editor, you should see the same content as in /var/efw/havp/whitelist
(0000287)
buzzzo   
2007-04-16 08:38   
As far as I remember the file was not a simlink , but was a empty file .

I've resolved the problem modifying the restarthavp.py and adding a simple
check of the whitelist file and copy it on the right place (/etc/whitelist).

I suggest adding code on the script to check if the link exists and if not, creating it .

Thx
(0000293)
detlef   
2007-04-24 21:30   
Hi,

whitelist dosnĀ“t work for me. Have installed efw-2.1 on four boxes and
it never works.
In the whitlist are two entries:

www.testvirus.de/*
www.eicar.org/*

every time i download a testvirus, havp is blocking this.
on my boxes the symlink and /etc/havp/whitelist does exist.

Detlef
(0000315)
buzzzo   
2007-05-08 16:38   
So ... how about this bug ?

I think it should be closed ... the problem is acknowleged and the solution
is simply to create the simlink .
(0000317)
peter-endian   
2007-05-10 15:32   
thank you very much for pointing out to close the issue.
this is what we need to keep the tracker clean.
(0001767)
luca-endian   
2008-11-04 13:01   
Same problem of original issue.
That appends on efw enterprise 2.2 and also development version.
(0001822)
simon-endian   
2008-11-21 16:58   
- if /etc/havp/whitelist is not a symlink but a file the file is moved to /var/efw/havp/whitelist, owner is set to nobody:nobody and a symlink is created (0000156)
- if /etc/havp/whitelist is not a symlink and does not exist a symlink is created (0000156)
- if /var/efw/havp/whitelist does not exist it is touched and owner is set to nobody:nobody (0000156)