Who is the maintaner of the SquidGuard-Devel?



  • Hi!

    I need some information.

    The last update changed the redirection on blacklist blocking, inputing some args on the URL, I can't use the usual arguments that SquidGuard uses.

    So… anyone knows who is the maintaner?


  • Banned

    There is no maintainer anywhere. Dunno which latest update you mean really. This package requires Squid 2.7 which is dead as a coffin nail. Stop using both. Unmaintained, buggy like hell.



  • @doktornotor:

    There is no maintainer anywhere. Dunno which latest update you mean really. This package requires Squid 2.7 which is dead as a coffin nail. Stop using both. Unmaintained, buggy like hell.

    There's two versions of SquidGuard in the repo…

    SquidGuard-Devel is currently being updated, there is someone working on it.

    -- EDIT ---
    Well well... looking at the Changelog: https://github.com/pfsense/pfsense-packages/commits/master/config/squidGuard-devel

    You seem to be working on it.

    I need to locate the function that generates the URL for the redirection. Normally SquidGuard would only include parameters if you use the marks lie %t, %u, etc.

    Now it is generating an URL followed bu the IP address, Group and Username. My sgerror.php was edited to a more "user friendly" appearence, so I need those parameters working.


  • Banned

    I'm not working on any package that requires Squid 2.7, really. Any commits there are coincidential with mass changes to mass-broken stuff (such as crontab handling).



  • @doktornotor:

    I'm not working on any package that requires Squid 2.7, really. Any commits there are coincidential with mass changes to mass-broken stuff (such as crontab handling).

    Good Lord…

    You don't even know the package it seems.

    SquidGuard-Devel is not SquidGuard... the "Devel" version doesn't require Squid 2.7. If memory serves, when this package first showed up, Marcelloc did some work on it. It actually was design towards Squid3.

    I just don't know who is working on it now, a new version was deployed like two weeks ago.


  • Banned

    Well, your memory serves you completely wrong. The non-devel package works with both Squid versions. The -devel one does NOT work with Squid3. Noone ever touched that package after being initially commited (as a pretty much verbatim copy of the non-devel version). Zero works has been done on it ever since. The original intentions are completely irrelevant ATM. Never been done and the package is badly broken.

    P.S. Proof is in the pudding…

    <build_options>squidGuard-devel_UNSET_FORCE=SQUID32 SQUID33;squidGuard-devel_SET_FORCE=LDAP STRIPNT SQUID27;squid_UNSET_FORCE=DNS_HELPER IPFILTER PINGER STACKTRACES STRICT_HTTP_DESC USERAGENT_LOG WCCPV2;squid_SET_FORCE=PF LDAP_AUTH NIS_AUTH SASL_AUTH ARP_ACL AUFS CACHE_DIGESTS CARP COSS DELAY_POOLS FOLLOW_XFF HTCP IDENT KERB_AUTH KQUEUE LARGEFILE REFERER_LOG SNMP SSL VIA_DB WCCP;SQUID_UID=proxy;SQUID_GID=proxy</build_options>



  • @doktornotor:

    Well, your memory serves you completely wrong. The non-devel package works with both Squid versions. The -devel one does NOT work with Squid3. Noone ever touched that package after being initially commited (as a pretty much verbatim copy of the non-devel version). Zero works has been done on it ever since. The original intentions are completely irrelevant ATM. Never been done and the package is badly broken.

    P.S. Proof is in the pudding…

    <build_options>squidGuard-devel_UNSET_FORCE=SQUID32 SQUID33;squidGuard-devel_SET_FORCE=LDAP STRIPNT SQUID27;squid_UNSET_FORCE=DNS_HELPER IPFILTER PINGER STACKTRACES STRICT_HTTP_DESC USERAGENT_LOG WCCPV2;squid_SET_FORCE=PF LDAP_AUTH NIS_AUTH SASL_AUTH ARP_ACL AUFS CACHE_DIGESTS CARP COSS DELAY_POOLS FOLLOW_XFF HTCP IDENT KERB_AUTH KQUEUE LARGEFILE REFERER_LOG SNMP SSL VIA_DB WCCP;SQUID_UID=proxy;SQUID_GID=proxy</build_options>

    Yes it works with Squid3, I have 7 servers running it now. We are not talking about the same package then.

    Look at the pic attached, the Production server was setup 2 months ago, with Squid3 running together with SquidGuard-Devel, I took this screenshot today, just bellow there's a screenshot from a test VM I setup yesterday.

    Someone updated the package and now the Redirect Helper is inserting unwanted parameter on the URL upon Blocked access based on ACLs. I would gladly correct it, If knew where the function is and who changed the package.

    I do agree the package description is misleading.



  • Banned

    Sigh. There's nothing misleading about the package description. Look at how's it compiled above.

    Also, I'm telling you that noone touched any of that since the package was commited. None of the crontab/package privs side commits are relevant in any way. Stop using this -devel package. It ain't intended for Squid3 at all.



  • For what it's worth, I am also running squid3 0.2.8 alongside squidguard-devel 1.5_1beta pkg v.1.5.6.  They work well together.



  • @doktornotor:

    Sigh. There's nothing misleading about the package description. Look at how's it compiled above.

    Also, I'm telling you that noone touched any of that since the package was commited. None of the crontab/package privs side commits are relevant in any way. Stop using this -devel package. It ain't intended for Squid3 at all.

    I AM TELLING YOU it works with Squid3… on pfSense 2.2.4 64 Bits, I have 7 servers working with it.

    It's clear on the Screenshot I posted on attachment that was an update on the package published on the official repo. There's no denying on that.

    BTW this is irrelevant, I want to know who did it, in order to solve one issue, if you can't help with that, please don't fill this thread with off-topic information and I might say, disinformation.


  • Banned

    This is apparently hopeless debate. I don't care what you are telling me, as you can clearly see than damned thing is compiled against Squid 2.7, has never been intended for use with Squid 3.x, plus has had ZERO relevant changes regarding your claimed issues as you can check here: https://github.com/pfsense/pfsense-packages/tree/master/config/squidGuard-devel

    This is what changed between 1.5.7 and 1.5.8. Now, if you could enlighten us where are the logging changes, Mr. Genius.

    If you know better, then go help yourself and yeah, please don't fill this thread with misinformation. Ktnxbye.

    ::) ::) ::)



  • @doktornotor:

    This is apparently hopeless debate. I don't care what you are telling me, as you can clearly see than damned thing is compiled against Squid 2.7, has never been intended for use with Squid 3.x, plus has had ZERO relevant changes regarding your claimed issues as you can check here: https://github.com/pfsense/pfsense-packages/tree/master/config/squidGuard-devel

    This is what changed between 1.5.7 and 1.5.8. Now, if you could enlighten us where are the logging changes, Mr. Genius.

    If you know better, then go help yourself and yeah, please don't fill this thread with misinformation. Ktnxbye.

    ::) ::) ::)

    How nice of you, next time you want to be so arrogant, please, keep it to yourself. I asked who did the change in the package, instead you chose to argue over if the package works with Squid3 or not. It works, as another said above, in fact works better than SquidGuard(the standard package). Why even argue over that? You should had answered with the changes you made to the code and done.

    Also, it is irrelevant if it is compiled to work over Squid 2.7, it's working with Squid3, me and a lot of others did testing and Luiz Gustavo also recommended to use it, since it have better support for LDAP features when using NTLM with Squid3.

    IT IS FACT that after the last change, now when a site is blocked and it redirects the user, the url will have unwanted parameters there.

    The original URL it was supposed to redirect to was like: http://172.16.0.50/proxy/blocked.php

    SquidGuard throws this URL to the user: http://172.16.0.50/proxy/blocked.php?172.16.0.51/- testuser GET

    Those parameters don't follow the standard SquidGuard uses, like:
    %a=client_address
    %n=client_name
    %i=client_user
    %s=client_group
    %t=target_group
    %u=client_url"

    So, I can't setup a custom error page, neither use the internal one "sgerror.php".


  • Banned

    I'm still waiting for you to point me to the change that broke your logging. Ah, right. you don't have any, because no such change happened anywhere in the package.

    Good luck with using package intended for Squid 2.7 with Squid 3.4. Soon, the install will be blocked, there's already a pull request for this. That will hopefully prevent similar idiotic threads.



  • @doktornotor:

    I'm still waiting for you to point me to the change that broke your logging. Ah, right. you don't have any, because no such change happened anywhere in the package.

    My gosh, why are you so arrogant?

    Did I say it was your fault? No. I said there is a problem after the update. Again, if you don't want to help, there's no need to call anyone idiot.

    @doktornotor:

    Good luck with using package intended for Squid 2.7 with Squid 3.4. Soon, the install will be blocked, there's already a pull request for this. That will hopefully prevent similar idiotic threads.

    In your POV this package is garbage, okay I get that. If that's your opinion doesn't mean everyone should agree with you. I said many times in this thread when and why this package has being used by a lot of people.

    Idiotic behavior is to derail threads imposing personal opinions and ignoring information provided.


  • Banned

    My gosh, why are you so stupid? Haven't seen such level of idiocy for quite some time.

    • The package is marked as "Requires Squid 2.x" (you even posted a screenshot here).
    • The package is compiled against Squid 2.7 (already posted a link here, everyone can see it).
    • You come here, and start moaning about how it "works fine", but the "latest changes" (that exist only in your head) have broken it (again, no such changes exist, again links posted here, once again everyone can see it.)

    So yeah – as for "information provided", that's what you have been ignoring from the very start of this thread. As noted above, hopefully the package manager will prevent installing this and other packages incompatible with Squid 3.x soon.



  • @doktornotor:

    My gosh, why are you so stupid? Haven't seen such level of idiocy for quite some time.

    Neither I had seen such level of arrogance. I think you either didn't read anything I wrote or just want to troll.

    @doktornotor:

    • The package is marked as "Requires Squid 2.x" (you even posted a screenshot here).

    I know that, you know that, but IT WORKS REALLY DENDY WELL with Squid3. Period.

    @doktornotor:

    • The package is compiled against Squid 2.7 (already posted a link here, everyone can see it).

    Yep, same point as above. It doesn't matter what's written there, in real -life it's working, for a long time I have to say.

    @doktornotor:

    • You come here, and start moaning about how it "works fine", but the "latest changes" (that exist only in your head) have broken it (again, no such changes exist, again links posted here, once again everyone can see it.)

    You started the moaning. I just asked who was supporting the package now, what the rest have to do with anything. You are acting like a little B, trying to impose your opinion as to why I shouldn't be using this package.

    @doktornotor:

    So yeah – as for "information provided", that's what you have been ignoring from the very start of this thread. As noted above, hopefully the package manager will prevent installing this and other packages incompatible with Squid 3.x soon.

    I and a lot of others will argue very much that this package is in fact compatible with Squid3.

    – For a nail in the coffin, see the attachment bellow, of all the packages setup and running on my test server.

    I just can't believe a user with this amount of posts can behave like this, this conversation is over.



Log in to reply