| Soren Aalto on Mon, 2 Apr 2001 14:08:21 +0200 |
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
| squid2.2S4 and authentication... |
I have a copy of Squid2.2S4 here that is the proxy for our student labs. Suddenly it tells everybody that they aren't authenticated and all attempts to give a username/password fail. I was suspicious as I have a lot of wierd stuff woven into this -- the authenticator program is an SUIDed copy of ncsa_auth that autheticates against /etc/shadow (no lectures please), and then there is a fancy redirector that talks to other stuff I don't even want to go into... Whatever. However, when I turn on tracing of the password stuff, the username/password is getting handed to the authenticator OK & being checked properly. But then squid hands back a 407/Proxy auth req'd header like so: GET http://www.uct.ac.za/ HTTP/1.0 HTTP/1.0 407 Proxy Authentication Required Server: Squid/2.2.STABLE4 The thing that wierds me out -- it does this even though I have taken out the ACL that asks for authentication and have disabled all of the other stuff. I have no idea what is going on. I have another copy of 2.2S4 running for the staff LAN and there don't seem to be any problems there, although there isn't the same goofy redirector stuff going on and I am authenticating against a file that isn't /etc/shadow. I'm just hoping somebody has seen something like this before? -- Soren Aalto <soren@xxxxxxxxxxxxxxx> Internet guy, University of Zululand If Bill Gates had a nickel for every time Windows crashed...oh wait, he does.