On Fri, 7 Nov 2003, Craig Ringer wrote:
> > GSSAPI/KERBEROS_V4 rely on the Kerberos Domain Controllers (KDC).
>
> Yeah. I left that off because it seemed pretty obvious, but p'haps it's
> best included.
It struck me as the same as a "Windows NT" authentication source.
> I personally like using P
>> This is much better. I'd probably put the mechanisms outside of the
>> libsasl box, since they are (almost always) loaded dynamicly.
>
> OK.
>
>> NTLM can use either Windows NT networking or the auxprop plugins.
>
> I don't quite get you there. I'll have a deeper look into the NTLM
> support an
Craig Ringer wrote:
This is much better. I'd probably put the mechanisms outside of the
libsasl box, since they are (almost always) loaded dynamicly.
OK.
NTLM can use either Windows NT networking or the auxprop plugins.
I don't quite get you there. I'll have a deeper look into the NTLM
supp
This is much better. I'd probably put the mechanisms outside of the
libsasl box, since they are (almost always) loaded dynamicly.
OK.
NTLM can use either Windows NT networking or the auxprop plugins.
I don't quite get you there. I'll have a deeper look into the NTLM
support and see if I get a be
On Thu, 6 Nov 2003, Craig Ringer wrote:
> I'm about as far from an expert on Cyrus as there is, so apologies if
> I'm dead wrong about something. I do think that a document like this
> will be useful in showing people how things fit together, and the
> various different "paths" through which Cyrus
Hi Craig,
I just wanted to say that such a 'big picture' is VERY useful. One picture
says more than thousand words.
Thanks,
Simon
> I posted a little while ago with a graphical map of the Cyrus
> authentication methods - missing the Mechanism layer completely.
> I think I have a better understan
I posted a little while ago with a graphical map of the Cyrus
authentication methods - missing the Mechanism layer completely.
I think I have a better understanding of that now, and have
updated the document appropriately. Comments would be appreciated.
I'm about as far from an expert on Cyrus as t
Ken Murchison wrote:
Craig, this is a good start, but as Rob said, you've left out the
mechanism layer.
Hmm... thanks. It appears that there's something lacking in my
understanding of the authentication scheme, but the posts on this thread
have given me some idea where to look and learn. I'll inc
On Fri, 31 Oct 2003, Craig Ringer wrote:
> Rob Siemborski wrote:
> > I'd also be much more inclined to accept this into the distribution if it
> > was in an easily modifiable format (at this point, I suspect that means
> > xfig, but if you have another suggestion I'm willing to listen).
>
> The cu
On Thu, 30 Oct 2003, Ken Murchison wrote:
> Craig Ringer wrote:
>
> > I'd really appreciate feedback on this - what have I missed, do I have
> > anything just plain wrong, etc. I've left out some things - like the
> > 'shadow' mechanism of saslauthd - that seem best solved using other
> > methods
Craig Ringer wrote:
I'd really appreciate feedback on this - what have I missed, do I have
anything just plain wrong, etc. I've left out some things - like the
'shadow' mechanism of saslauthd - that seem best solved using other
methods (getpwent in that case). Also left out are the specific-ven
On Thu, 30 Oct 2003, Craig Ringer wrote:
> I'd really appreciate feedback on this - what have I missed, do I have
> anything just plain wrong, etc. I've left out some things - like the
> 'shadow' mechanism of saslauthd - that seem best solved using other
> methods (getpwent in that case). Also lef
12 matches
Mail list logo
