On Thu, Apr 12, 2012 at 12:36:21AM +1000, Trent W. Buck wrote: > Alessandro Ghedini wrote: > > On Tue, Apr 10, 2012 at 11:14:25AM +0200, Hannes von Haugwitz wrote: > > > Hello, > > > > > > On Sat, Feb 18, 2012 at 05:01:14PM +0100, Alessandro Ghedini wrote: > > > > An alternative solution would be to build curl with Heimdal (AFAICT > > > > they do > > > > provide the static library) instead of the MIT kerberos implementation. > > > > > > > > I'm not sure on the consequences of such change though, and I will need > > > > to > > > > do some testing first. > > > > > > Is there any progress with this issue? > > > > Not much. I'm still quite uncomfortable on replacing MIT kerberos, the > > reference > > implementation of Kerberos and the default one on Debian, with another, less > > used and tested, alternative. > > Would it be possible to use MIT krb for the dynamic libcurl, and *no* > krb for the static libcurl? The krb part is, after all, only used for > SPNEGO, and the set intersection of "people who want static libcurl" > and "people who need krb" is probably pretty small.
Shipping a not compatible static library would be even worse. Not to mention the
fact that every libcurl flavour would need to be re-built multiple times only
for removing a dependency on the static library.
Anyway, as a first step I can upload a curl package that lists heimdal as an
alterative build dependency. krb5 would remain the default choice for now, but
at least it would make re-building curl with heimdal much easier (just like
openssh does). If nothing bad happens I can re-consider switching to heimdal by
default.
Cheers
--
perl -E'$_=q;$/= @{[@_]};and s;\S+;<inidehG ordnasselA>;eg;say~~reverse'
signature.asc
Description: Digital signature
