Dansguardian package for 2.0
-
I just figured out what was different on that one account. Apparently the script can't handle () characters in the distinguished name. After renaming without the () characters, it is working. Ideally all characters that AD supports should be handled but that could be MS diverging from LDAP standards too… so depending on if it is in the LDAP standards it may or may not make sense to fix that (of if you just want to avoid possible AD issues).
The other issue of not updating after the AD group is empty still happens though. Easy enough to work around (delete it from pfsense) but something to put on the list to fix.
-
I just figured out what was different on that one account. Apparently the script can't handle () characters in the distinguished name. After renaming without the () characters, it is working. Ideally all characters that AD supports should be handled but that could be MS diverging from LDAP standards too… so depending on if it is in the LDAP standards it may or may not make sense to fix that (of if you just want to avoid possible AD issues).
This script running for squidguard breaks xml with special characters. On dansguardian, the config filed for users are base64 encoded, so you can fetch it but will not apply correctly. My suggestion is to work around this limitation by do no use characters other then [a-z,A-Z,0-9].
The other issue of not updating after the AD group is empty still happens though. Easy enough to work around (delete it from pfsense) but something to put on the list to fix.
It makes sense. if there is no users on groups, then there is no loop to do. :P
-
It makes sense. if there is no users on groups, then there is no loop to do. Tongue
I don't think you got what I meant. So I add a user to the AD group; it adds a user in pfsense/dansguardian. I then remove that user from the AD group; it does nothing so the user still exists in pfsense/dansguardian. If I add 10 users, it adds 10. If I then remove all 10 users at once, all 10 users remain in pfsense/dansguardian. So you can never remove access for all users via an AD group. At best you can remove 9 first, but then you will always have that 1 left that won't get removed (unless you do it in the pfsense gui).
Like I said, easy work around but still a bug. ;)
-
I understood you, I was just explaining why there was no update on empty groups :)
-
So I was able to get the newer version of squid by loading the squid-reverse package after dansguardian however there are issues with this. For some reason squid then can't start on its own after boot up. I have to run /usr/local/etc/rc.d/squid.sh start and then it will start (doesn't work from the GUI). Also sarg can't find the dansguardian log (could before). Since there are issues with this way, it sounds like I'll have to wait until that is updated before I use this setup.
Also how is the dansguardian patch coming? That is the other thing I think I need to wait on as I will have both ntlm and IP authenticated users and can't use both authplugins at the moment. What are you running into with the patch? Perhaps I could help figure something out?
Thanks marcelloc for all the great work you are doing!
-
So I was able to get the newer version of squid by loading the squid-reverse package after dansguardian however there are issues with this. For some reason squid then can't start on its own after boot up. I have to run /usr/local/etc/rc.d/squid.sh start and then it will start (doesn't work from the GUI). Also sarg can't find the dansguardian log (could before). Since there are issues with this way, it sounds like I'll have to wait until that is updated before I use this setup.
It's working for me.
I did dansguardian install and then squid-reverse install.
something I've added was a cron job to check squid status. when offline, script runs /usr/local/sbin/squidAlso how is the dansguardian patch coming? That is the other thing I think I need to wait on as I will have both ntlm and IP authenticated users and can't use both authplugins at the moment. What are you running into with the patch? Perhaps I could help figure something out?
I'm still getting alloc erros on dansguardian while trying to compile it with squid3 and multi plugin patch.
-
SSL filtering working now?
-
-
SSL filtering working now?
I am able to get past the Invalid Server Certificate error message by dropping all the recognized public CA certs in the /etc/ssl folder (along with the appropriate symlinks named with the hash value of each cert) but I'm stuck on a missing cgi script called mitm.cgi.
Daniel Barron over on the dansguardian-dev list informed me that this script has not been open sourced by smoothwall and that we would have to reverse engineer/rewrite it based on the dansguardian mitm source code.If you want more details on how to install those certs let me know.
-
If you want more details on how to install those certs let me know.
dig1234,
I've already included the ca-root package as well links to ca folder, can you test on a virtual machine if this patch results on the same point you got?
-
dig1234,
I've already included the ca-root package as well links to ca folder, can you test on a virtual machine if this patch results on the same point you got?
Hi I tried this, fresh pfsense install on vmware, installed dans and squid, turned on cert check & mitm. Now I just get connection refused when trying https sites. Also in the logs I see dansguardian[17654]: error opening new certificate. So, no I am not at the same place.
One thing I noticed is that you have added the 150 public certs to /etc/ssl but they are all in one file called cert.pem. Dans wants each one to be in a separate. Also they need to be named with the hash value of the cert (or symlinks by that name). They should look something like this:
ef2f636c.0
f060240e.0
f081611a.0
f15719eb.0
f3377b1b.0UPDATE:
I turned off mitm and left cert checking turned on and didn't get any errors so maybe it is finding the certs. The problem now is with creation of the 'forged' certs.. Is there a way to get more verbose logging from dansguardian? -
I had issues and uninstalled DG, Squid, HAVP, reinstalled Dansguardian –--> HAVP ----> WWW, so no more squid.
I now get in the system logs: Dans Guardian [xxxx} "Error connecting via IPC socket to log: No such file or directory"
After a reboot Dansguardian doesnt start, it starts from web configurator fine, workd fine, just using ram I think and get this in the log quite frequently. Any one seen this?
-
After a reboot Dansguardian doesnt start, it starts from web configurator fine, workd fine, just using ram I think and get this in the log quite frequently. Any one seen this?
I experienced the same, dans not starting on reboot but starts fine from webgui later. I attributed it to squid taking a longer time to start, but I could be wrong…
-
I experienced the same, dans not starting on reboot but starts fine from webgui later. I attributed it to squid taking a longer time to start, but I could be wrong…
I've just installed a clean 2.0.1 install with dansguardian and squid3 package and I still had no luck on reproducing this issue.
Can you check what happens during your boot process?
-
After a reboot Dansguardian doesnt start, it starts from web configurator fine, workd fine, just using ram I think and get this in the log quite frequently. Any one seen this?
I experienced the same, dans not starting on reboot but starts fine from webgui later. I attributed it to squid taking a longer time to start, but I could be wrong…
Same issue here and I tend to thing dig1234 is correct… has to be a timing issue - which would be different depending on the machine. That said, doesn't it make sense that DG should start after Squid anyway? DG is dependent on Squid to proxy...
Also, haven't been able to find anywhere that DG gives an error message as to why it won't start. Let me know if you have any idea where I should look.
-
Also, haven't been able to find anywhere that DG gives an error message as to why it won't start. Let me know if you have any idea where I should look.
Can you check boot process just like I've posted?
-
Also, haven't been able to find anywhere that DG gives an error message as to why it won't start. Let me know if you have any idea where I should look.
Can you check boot process just like I've posted?
I couldn't figure out how you got VirtualBox bigger - so I couldn't take a screenshot showing everything… However, the boot looks the exact same as the one you posted with the exception of dansguardian not running... in other words, the ps grepping for dans does not show anything.
BTW. I noted that if you install the old version of squid, it starts before dans.
-
I couldn't figure out how you got VirtualBox bigger
printscreens and paint/gimp ;)
In other words, the ps grepping for dans does not show anything.
BTW. I noted that if you install the old version of squid, it starts before dans.
I'm checking dansguardian boot process. I've fixed clamav startup error when enabled on dansguardian but I'll do more tests before publishing and I still have no idea why some systems are getting issues on boot and other don't.
-
I couldn't figure out how you got VirtualBox bigger
printscreens and paint/gimp ;)
In other words, the ps grepping for dans does not show anything.
BTW. I noted that if you install the old version of squid, it starts before dans.
I'm checking dansguardian boot process. I've fixed clamav startup error when enabled on dansguardian but I'll do more tests before publishing and I still have no idea why some systems are getting issues on boot and other don't.
So… can't explain it, but DG seems to be starting up fine in the new virtual that I built. This is the first time I've seen it startup without needing to be restarted post-boot. All of that said, I do think that DG should start after squid and suspect that doing so would solve problems that people are having.
I was also wondering if you have given any thought to changing how the GUI handles the "denied" page? The thing that is stopping me from fully switching to PFsense is the fact that the GUI doesn't properly support using an access denied URL and both the GUI and the bootup process insist on overwriting my manual DG bypass changes (see this threadhttp://forum.pfsense.org/index.php/topic,47856.30.html. Obviously I can create a script to restore my changes, but that's a pretty inconvenient hack…
Just wondering... thanks!
-
So I did a little more playing around so that I could be specific about what is necessary to make the bypass feature work correctly (without any overwrite issues)…
1. In the "Report and Log" page...
- Add the ability to specify the "accessdeniedaddress" value instead of just the HTML form content2. In the "Groups" page...
- Add the ability to specify the "accessdeniedaddress"
- Add the ability to specify the "bypasskey"That would basically do it...
