All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ondrej Valousek <webserv@s3group.cz>
Cc: autofs mailing list <autofs@linux.kernel.org>
Subject: Re: krb5 required when building with sasl support
Date: Fri, 06 Feb 2009 13:23:54 +0100	[thread overview]
Message-ID: <498C2BDA.6070101@s3group.cz> (raw)
In-Reply-To: <n7xr62bx0fg.fsf@sor.suse.de>

sasl could be (theoretically) built without GSSAPI support and in this
case it would not require Kerberos. But the facts are:
- sasl support in autofs can not be obviously compiled without gssapi
- in these days sasl is many times meant as synonym for sasl/gssapi so
it probably does not make any sense not to include gssapi once we
include sasl.

Ondrej

Matthias Koenig wrote:
> Guillaume Rousse <Guillaume.Rousse@inria.fr> writes:
>
>   
>> More seriously, I think the proper solution would rather be fixing 
>> underliking in SASL (http://wiki.mandriva.com/en/Underlinking).
>>     
>
> Hmm, are you really sure, that libsasl depends on kerberos symbols?
> In this case you would be right.
> I assumed that they're independent from each other and after
> a quick grep I couldn't find any krb5_* symbols in libsasl.
> At least the lookup_ldap.h header from autofs explicitly includes
> the krb5.h header.
>
> Matthias
>
> _______________________________________________
> autofs mailing list
> autofs@linux.kernel.org
> http://linux.kernel.org/mailman/listinfo/autofs
>   

  reply	other threads:[~2009-02-06 12:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-04 16:42 krb5 required when building with sasl support Matthias Koenig
2009-02-04 16:58 ` Ondrej Valousek
2009-02-05 18:27   ` Guillaume Rousse
2009-02-06 11:35     ` Matthias Koenig
2009-02-06 12:23       ` Ondrej Valousek [this message]
2009-02-06 13:09         ` Guillaume Rousse
2009-02-06 13:18       ` Guillaume Rousse

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=498C2BDA.6070101@s3group.cz \
    --to=webserv@s3group.cz \
    --cc=autofs@linux.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.