[23579] in Kerberos
A Kerberos authentication scheme.
daemon@ATHENA.MIT.EDU (Michael Norwick)
Wed Mar 23 04:06:19 2005
Message-ID: <4241316D.1080503@centurytel.net>
Date: Wed, 23 Mar 2005 03:05:49 -0600
From: Michael Norwick <ctx37888@centurytel.net>
MIME-Version: 1.0
To: Kerberos Mailing List <Kerberos@mit.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Errors-To: kerberos-bounces@mit.edu
I apologize if this is off topic. I have been subscribed to this list
for two years and have
archived most of the posts. I am inexperienced at implementing an
authentication
scheme beyond using PAM/OpenSSH/OpenSSL, and various flavors of file and
filesystem
encryption. I wish to move to a stronger security model that would
implement Kerberos
with one of the developing (authenticated?) filesystems eg. AFS, Coda,
NFSv4 on Linux
and OpenBSD with support for Windows clients. For the size of networks
I administer,
2-20 node lans in small business and education, protection with
environments such as
SELinux and LIDS have proved too visible to the users. I would like to
provide something
more transparent. I have a small 5 node test lan on which I have built
and installed Kerberos
with AFS, and am now preparing to test NFSv4. In reviewing the posts on
this mailing
list, it appears that a many of you work with LARGE networks with many
kdc's, realms and
educated users. My question is; Am I forsaking the KISS paradigm and
trying to dig a post
hole with a bulldozer or, does Kerberos/AFS/whatever, scale down well to
meet my current
needs? To be able to 'standardize' on an authentication method would
make my life a lot
easier. I guess I'm looking for krb/afs is to authentication as LAMP is
to web services?
Michael
________________________________________________
Kerberos mailing list Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos
