On Wed, 2012-06-27 at 12:04 +0300, Timo Sirainen wrote:
> On Tue, 2012-03-06 at 18:12 +, Sam Morris wrote:
> > On Mon, 2012-03-05 at 20:52 +0200, Timo Sirainen wrote:
> > > On 5.3.2012, at 20.45, Sam Morris wrote:
> > >
> > > > 3. The credentials lookup triggers an info log message saying
On Tue, 2012-03-06 at 18:12 +, Sam Morris wrote:
> On Mon, 2012-03-05 at 20:52 +0200, Timo Sirainen wrote:
> > On 5.3.2012, at 20.45, Sam Morris wrote:
> >
> > > 3. The credentials lookup triggers an info log message saying that
> > >credentials for GSSAPI were requested, "but we h
On Mon, 2012-03-05 at 20:52 +0200, Timo Sirainen wrote:
> On 5.3.2012, at 20.45, Sam Morris wrote:
>
> > 3. The credentials lookup triggers an info log message saying that
> >credentials for GSSAPI were requested, "but we have only (e.g.)
> >MD5-CRYPT". The authplugin doesn't a
On 5.3.2012, at 20.45, Sam Morris wrote:
> 3. The credentials lookup triggers an info log message saying that
>credentials for GSSAPI were requested, "but we have only (e.g.)
>MD5-CRYPT". The authplugin doesn't actually want the credential,
>but I think that the only wa
The attached patch makes it possible for Kerberos principals to be
associated with a password database entry by adding a new "k5principals"
passdb setting. A client that successfully authenticates using GSSAPI
will be able to log in as any user who has been associated with the
client's Kerberos pri
