Hi, On Fri, 2012-06-29 at 15:19 0000, James Antill wrote: > On Fri, 2012-06-29 at 03:57 -0400, Zdenek Pavlas wrote: >> 2) no way to enable only one auth scheme and save the 1st request >> 3) can't disable BASIC (security) >> >> I'm okay with both solutions (proxy_auth env var, or disabling >> kerberos the hard way). 3rd option is adding an urlgrabber + yum >> option to yum.conf, but that feels an overkill to me. > > It feels like nobody would care if we just disable kerberos, and > probably 0.001% of users will use any configuration if you add it. So > I'd just go with the easiest thing and wait for someone to complain :)
Two and a half years later, here I am! Sorry, just had to. >> 1) no way to ever use kerberos > > Not sure I see the problem :). I mean we never have supported it, > right? I don't know about "supporting", but kerberos-authenticated proxy is working just fine if you just don't explicitely disable it. I wasn't able to find much discussion on the lists, but looking at the git repo this was "fixed" (check with pycurl version, commit 9b9a1db5 in urlgrabber repo, Jan 8 2013) then the commit was revert (32ec3e47, May 17 2013)... and I can't find any mail or information regarding why ? I'm sure you had a reason and I can reluctantly keep a local version of the python-urlgrabber rpm for these machines, but I'd very much like to understand why I have to do that :) And, eventually, beg to reconsider and/or make it an option if possible? (not sure what the list policy is about keeping senders in Cc, so subscribed to the list for now) Regards, -- Dominique Martinet _______________________________________________ Yum-devel mailing list Yum-devel@lists.baseurl.org http://lists.baseurl.org/mailman/listinfo/yum-devel
