Hi George,
It might be some new code I added for Kerberos PAC analysis to extract
groups. What Kerberos version do you use ? Can you send me your config.log ?
Thank you
Markus
"George Billios" wrote in message
news:E1Wxb2r-0002U0-PB@xxxxxxxxxxxxxxxxxxxxx...
On Thu, 19 Jun 2014 23:21:45 +1200, Amos Jeffries <squid3@xxxxxxxxxxxxx>
wrote:
On 19/06/2014 6:40 p.m., George Billios wrote:
> Hi,
>
> I'm trying to upgrade from 3.3.8 to 3.4.5 (3.4.x in general), compile
> squid with the same options (that are still valid in 3.4.x) and use
> negotiate authentication, but every time negotiate_kerberos_auth crashes
> with the following:
>
>
> 2014/06/18 23:06:20| negotiate_wrapper: Error reading Kerberos helper
> response
> 2014/06/18 23:06:20 kid1| WARNING: negotiateauthenticator #Hlpr0 exited
> 2014/06/18 23:06:21| negotiate_kerberos_auth: ERROR:
> krb5_pac_get_buffer: Invalid argument
> *** glibc detected *** /usr/libexec/negotiate_kerberos_auth: double free
> or corruption (fasttop): 0x000000000159af00 ***
> ======= Backtrace: =========
> /lib/libc.so.6(+0x71e16)[0x7f6bf3b3ae16]
> /lib/libc.so.6(cfree+0x6c)[0x7f6bf3b3fb8c]
> /usr/lib/libkrb5.so.3(krb5_free_data+0x12)[0x7f6bf54a3472]
> /usr/libexec/negotiate_kerberos_auth[0x4044e9]
> /usr/libexec/negotiate_kerberos_auth[0x40319c]
> /lib/libc.so.6(__libc_start_main+0xfd)[0x7f6bf3ae7c8d]
> /usr/libexec/negotiate_kerberos_auth[0x4018b9]
Do you have a trace that shows what the helper was doing?
From that trace it looks like simply calling the main() function and
linking to the library crashed it. None of that is Squid code, all OS
code, so ... ?!
Amos
I don't have a trace but I can probably enable all the debug options and get
one.
Even if this an OS issue what can trigger it since the helper from 3.3.8
works but the one from 3.4.x doesn't with the same libraries, same compile
options etc ? That is why I'm asking if something fundamental changed -
which from a quick look at the helper code I can say something has but I
don't have the programming skills to understand what exactly and how it
could create this issue.
In any case I'll come back with more debug info.
