Mark Eichin <[EMAIL PROTECTED]> wrote:
>
> As long as you plan to include the kerberos mechanisms: go for
> it! you've gotten further than I have had time for - I'm happy
> to just use them (but can advise on the kerberos bits if they
> give you difficulty.)
Yep, I'll enable all the appropriate
As long as you plan to include the kerberos mechanisms: go for it!
you've gotten further than I have had time for - I'm happy to just use
them (but can advise on the kerberos bits if they give you difficulty.)
> and alwaystrue (useful for testing).
Heh, like the never-released GSSAPI "assert" me
Hi,
We have been working with Pubcookie here at Progeny for the past
month or so... We've begun on significant improvements, and
already have Debian packages we are using for our internal
infrastructure. Considering our active interest in the use and
development of Pubcookie I hope that you will
> You might want to take a look at what umn.edu does with their x.500
If there were any x.500 validation servers available in debian, that
would be interesting -- however, as far as I can tell, there aren't.
The whole reason pubcookie is interesting is that it can work with
kerberos, and thus on
Mark W. Eichin wrote:
failed access) and give a kerberos login, and get back a cookie; the
cookie can then be used for access to other pages. (Yes, this
You might want to take a look at what umn.edu does with their x.500
login system. THere is at least a description at
http://www.umn.edu/c
Package: wnpp
Severity: wishlist
* Package name: libapache-mod-pubcookie
Version :
Upstream Author : washington.edu Pubcookie Team
* URL : http://www.washington.edu/computing/pubcookie/
* License : MIT/X-style
Description : kerberos auth for web pages
Yo
6 matches
Mail list logo
