ClearFoundation Tracker - ClearOS
View Issue Details
0006531ClearOSapp-web-proxy - Web Proxypublic2015-12-01 19:432019-05-20 04:26
bchambers 
 
normalmajoralways
closedfixed 
7.1.0 
 
0006531: Adding Web Proxy Bypasss (IP) Rule fails to restart FW
Loosen up the interface name validation with ClearOS 7. The new naming scheme is a tad weird and unpredictable, so allow all sorts of stuff in validator.
No tags attached.
Issue History
2015-12-01 08:13user2New Issue
2015-12-01 08:21user2Statusnew => resolved
2015-12-01 08:21user2Fixed in Version => 7.1.0 Updates
2015-12-01 08:21user2Resolutionopen => fixed
2015-12-01 08:21user2Assigned To => user2
2015-12-01 19:43bchambersNew Issue
2015-12-01 19:44bchambersNote Added: 0002301
2015-12-02 19:33bchambersNote Added: 0002331
2016-02-25 09:00user2Statusnew => acknowledged
2019-05-20 04:26NickHStatusacknowledged => closed
2019-05-20 04:26NickHResolutionopen => fixed

Notes
(0002301)
bchambers   
2015-12-01 19:44   
Test was with Proxy in Non-Transparent Mode requiring authentication.

Proxy service was started. Content filter was disabled.
(0002331)
bchambers   
2015-12-02 19:33   
Upgrade to app-firewall 2.1.28 does trigger the fw restart, however, there's another problem...something to do with clearsync UID:

Dec 2 21:30:59 chambers sudo: pam_unix(sudo:auth): conversation failed
Dec 2 21:30:59 chambers sudo: pam_unix(sudo:auth): auth could not identify password for [clearsync]
Dec 2 21:30:59 chambers sudo: pam_succeed_if(sudo:auth): requirement "uid >= 1000" not met by user "clearsync"
Dec 2 21:30:59 chambers sudo: clearsync : command not allowed ; TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/systemctl restart firewall6
Dec 2 21:31:27 chambers sudo: clearsync : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/sbin/trigger network_proxy

Result is the same...firewall does not restart when adding IP exception to proxy.