Problem with web uploads in new dansguardian 2.12.0.3

[rjcrowder]

Agreed…. it does not work with -1 in the group options... I also tried setting it to a value... doesn't work.

@asterix:

@marcelloc:

It's not working even if you set it to -1 on group options?

Tried that already. Does not work.

[marcelloc]

I've fixed the code.  ;D

The patch 11 was malformed and broke up web upload check.

I did not pushed it to dansguardian devel or freebsd patch yet.

Test my dansguardian package and see if it works

I've also included the code to limit upload size(was not working on 2.12.0.2 AFAIK)

amd64
http://e-sac.siteseguro.ws/packages/amd64/8/All/dansguardian-2.12.0.3_1.tbz

i386
http://e-sac.siteseguro.ws/packages/8/All/dansguardian-2.12.0.3_1.tbz

Do not forget to kill dansguardian process before trying new packge binaries.

[rjcrowder]

Thanks Marcello… that's awesome!  I'm currently traveling - so I won't be able to check it till Friday. Will let you know as soon as I do though...

@marcelloc:

I've fixed the code.  ;D

The patch 11 was malformed and broke up web upload check.

I did not pushed it to dansguardian devel or freebsd patch yet.

Test my dansguardian package and see if it works

I've also included the code to limit upload size(was not working on 2.12.0.2 AFAIK)

amd64
http://e-sac.siteseguro.ws/packages/amd64/8/All/dansguardian-2.12.0.3_1.tbz

i386
http://e-sac.siteseguro.ws/packages/8/All/dansguardian-2.12.0.3_1.tbz

Do not forget to kill dansguardian process before trying new packge binaries.

[samham]

Marcello when will you push the patch?

[marcelloc]

@samham:

Marcello when will you push the patch?

I've pushed it to dansguardian sourceforge project.

But not for freebsd ports.

I'm waiting feedbacks to see if there are other bugs that I can help to fix.

[rjcrowder]

Seems to work. Thanks!

[cirkit]

I am a noob to freebsd but faced the same problem above, I downlaoded the new package (modified) extracted dansguardian from sbin and pasted it in sbin of my pfsense box and it worked
Is it necessary to replace the other files?

[marcelloc]

no, just dansguardian bin.

I've uploaded dansguardian bin to my personal repo :)

i386
killall dansguardian
cd /usr/local/sbin
fetch http://e-sac.siteseguro.ws/pfsense/8/dansguardian

amd64
killall dansguardian
cd /usr/local/sbin
fetch http://e-sac.siteseguro.ws/pfsense/8/amd64/dansguardian

[dig1234]

patched binary worked for me, Thanks!

[awsiemieniec]

ditto on the fix, thanks!  ;D

[neil]

I have just set up Dansguardian for a large site and have experienced the same "web upload is banned" as reported in this thread.

Package Manager shows 2.12.0.3pkg v.0.1.7_3.

I've tried downloading the patched binary from http://e-sac.sitesguro.ws/pfsense/8/amd64/dansguardian
after killing dansguardian.
When I try to start the new binary I get the message:

/usr/local/sbin/dansguardian: 1: Syntax error: ")" unexpected
./dansguardian.sh WARNING: failed to start dansguardian

Are you able to help me here, and in particular what steps do I need to follow to resolve the "web upload is banned" problem - thanks

PS.  to be able to save this post, I had to put an exception for forum.pfsense.org into the sites exception list, to avoid having this post blocked by the same error for which I am seeking help!

[marcelloc]

@neil:

I've tried downloading the patched binary from http://e-sac.sitesguro.ws/pfsense/8/amd64/dansguardian
after killing dansguardian.
When I try to start the new binary I get the message:

/usr/local/sbin/dansguardian: 1: Syntax error: ")" unexpected
./dansguardian.sh WARNING: failed to start dansguardian

If you copied only dansguardian binary, it should start as it does not touch dansguardian.sh file.

try to save dansguardian config again to recreate startup script.

[neil]

Thanks for the quick reply - I did as you suggested, made a change in DG/PFsense, and saved the change - presumably this recreates the dansguardian.sh script - unfortunately no change.

Just to recap all I did was:

1. killall dansguardian
2. cd /usr/local/sbin
3. mv dansguardian dansguardian.orig (ie backed up the old version)
4. fetch https://e-sac….....etc
This retrieved a file of size 994216 dated feb 8.
The permissions on this file did not match those on the old version and in particular were not executable.
So I typed chmod 555 dansguardian and the permissions then matched (ie -r-xr-xr-x)
5. cd /usr/local/etc/rc.d
6. ./dansguardian.sh start

This resulted in the error I reported.

When I copy the original dansguardian binary back again, the startup script runs without any error.

Any further thoughts?

[marcelloc]

@neil:

Any further thoughts?

No. :( Except for the mv dansguardian dansguardian.orig I've did it again here and it started up fine.

[neil]

Hmmmm - I'm not getting anywhere here.
If I copy the dansguardian.orig back to dansguardian and run ./dansguardian.sh start , DG starts without error.
The "syntax error: " etc seems to be coming from the binary not from the script.

I've tried downloading the binary again, and there is no improvement.

Could you send the binary to me at neil@darfield.school.nz?

Thanks

[neil]

DOH this was my problem - my production servers are all x64 while my development server is x86.
I was trying to apply the x64 version of DG to an x86 PFsense install.
I've downloaded the x86 version and this starts correctly.
Thanks for your replies

[Legion]

Also had problems uploading, also downloaded your patch, also worked. Thanks marcelloc.

[eldersouza]

@marcelloc:

@samham:

Marcello when will you push the patch?

I've pushed it to dansguardian sourceforge project.

But not for freebsd ports.

I'm waiting feedbacks to see if there are other bugs that I can help to fix.

Estava com esse problema aqui no dansguardian, só fiz substituir o arquivo que você disponibilizou e pronto!! Problema resolvido !!

Valeuz Marcello

[Hugovsky]

Me too! Thanks marcelloc.  8)

[engellion]

I have the same problem, but I can not download the patch. When I try ato fetch, I get a: fetch http://e-sac.sitesguro.ws/pfsense/8/dansguardian: Operation timed out

I tried a traceroute on http://e-sac.sitesguro.ws and got the following:

traceroute e-sac.stesguro.ws
traceroute to e-sac.stesguro.ws (64.70.19.198), 64 hops max, 52 byte packets
1  10.1.1.1 (10.1.1.1)  0.463 ms  0.335 ms  0.281 ms
2  nexthop.qld.iinet.net.au (203.215.9.250)  14.452 ms  14.227 ms  16.294 ms
3  150.101.33.158 (150.101.33.158)  31.716 ms  13.708 ms  16.490 ms
4  ae1.br1.syd4.on.ii.net (150.101.33.18)  29.600 ms  28.967 ms  31.846 ms
5  te0-0-0-1.br1.lax1.on.ii.net (203.16.213.69)  178.061 ms
    te0-1-1-2.bd1.lax1.on.ii.net (203.16.213.65)  206.041 ms
    te0-0-0-1.br1.lax1.on.ii.net (203.16.213.69)  177.792 ms
6  144.223.30.1 (144.223.30.1)  218.953 ms  207.542 ms  203.939 ms
7  sl-crs2-ana-0-15-0-0.sprintlink.net (144.232.19.226)  175.235 ms
    144.232.1.177 (144.232.1.177)  176.961 ms  179.663 ms
8  sl-st21-la-13-0-0.sprintlink.net (144.232.20.69)  208.509 ms
    sl-st21-la-0-0-0.sprintlink.net (144.232.20.206)  210.669 ms  210.212 ms
9  208.174.196.113 (208.174.196.113)  211.137 ms  208.013 ms  208.514 ms
10  pr2-so-6-1-0.losangelesequinix.savvis.net (204.70.200.97)  191.378 ms
    pr2-so-6-0-0.losangelesequinix.savvis.net (204.70.200.93)  195.916 ms
    pr2-so-6-2-0.losangelesequinix.savvis.net (204.70.200.101)  195.221 ms
11  hr1-te-1-0-0.irvine2oc2.savvis.net (204.70.204.189)  190.690 ms  191.125 ms  190.078 ms
12  hr2-te-1-0-1.irvine2oc2.savvis.net (204.70.204.166)  218.562 ms  220.108 ms  221.215 ms
13  hr1-te-1-0-0.elsegundola1.savvis.net (204.70.204.194)  188.445 ms  189.647 ms  188.262 ms
14  das1-v3006.la1.savvis.net (64.70.11.54)  187.990 ms  190.962 ms  191.201 ms
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
(this went up to 44 * * * before a did a ctrl-C)

Is this patch accessible from Australia?

Thanks.
Paul.