Your message dated Mon, 27 Aug 2007 14:50:39 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#425577: Bug confirmation. Possible target for a future
stable update ?
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: squid
Severity: important
Tags: patch
Hi!
I have seen this on a stable (etch) system while trying to check the users
against a windows domain, the config used to work on sarge, but was broken
after upgrading to etch.
What I have on my squid config among other stuff is:
external_acl_type domain_groups concurrency=5 %LOGIN
/usr/lib/squid/wbinfo_group.pl
However after adding a -d that wbinfo_group.pl line I got this info on my
logs:
Got 0 USERNAME GROUP from squid
Could not convert sid S-1-whatever-sid to gid
User: -0-
Group: -USERNAME-
SID: -S-1-whatever-sid-
GID: --
Could not get groups for user 0
Sending OK to squid
What I could see here is that squid was sending a "0" before sending the
username, I don't know if this is supposed to be like that and we should fix
wbinfo_group.pl or squid is broken and it is sending something it shouldn't,
in any case, for a quick fix I patched wbinfo_group.pl like this:
--- wbinfo_group.pl 2006-05-22 22:42:06.000000000 +0200
+++ wbinfo_group_patched.pl 2007-05-21 15:06:14.000000000 +0200
@@ -85,7 +85,7 @@
while (<STDIN>) {
chop;
&debug ("Got $_ from squid");
- ($user, @groups) = split(/\s+/);
+ ($ans, $user, @groups) = split(/\s+/);
$user =~ s/%([0-9a-fA-F][0-9a-fA-F])/pack("c",hex($1))/eg;
# test for each group squid send in it's request
foreach $group (@groups) {
so that the "0" was skipped and that the user groups get where they were
supposed to, and right now it is working ok.
I don't know if this problem can affect other helpers or not, if you need
any other info on the problem just let me know.
Regards!
--- End Message ---
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
[ Following up to debian-release so this bug is no considered ]
Hi André, Santiago,
in Squid 2.6 changes where made to the external_acl configuration
directive and meaning of concurrency has changed. To achieve old
behaviour please use 'children=' instead of 'concurrency='.
This change is documented in the RELEASENOTES, even if not so
explicitly.
See http://www.squid-cache.org/bugs/show_bug.cgi?id=2063 for upstream
description of configuration error.
Regards,
L
- --
Luigi Gangitano -- <[EMAIL PROTECTED]> -- <[EMAIL PROTECTED]>
GPG: 1024D/924C0C26: 12F8 9C03 89D3 DB4A 9972 C24A F19B A618 924C 0C26
- --
Luigi Gangitano -- <[EMAIL PROTECTED]> -- <[EMAIL PROTECTED]>
GPG: 1024D/924C0C26: 12F8 9C03 89D3 DB4A 9972 C24A F19B A618 924C 0C26
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
iD8DBQFG0sih8ZumGJJMDCYRAiaKAJ9vOUPosEd9rKCzBT++n8rcmGOdbQCdGMMu
lh2HtT1hdZSWVBSbN3NYtgE=
=BDci
-----END PGP SIGNATURE-----
--- End Message ---
