[6366] in Kerberos
NetBSD liason
daemon@ATHENA.MIT.EDU (Gord Matzigkeit)
Fri Dec 15 13:19:36 1995
To: kerberos@MIT.EDU
Date: 12 Dec 1995 16:34:31 -0700
From: gord@enci.ucalgary.ca (Gord Matzigkeit)
Reply-To: Gord Matzigkeit <gord@enci.ucalgary.ca>
-----BEGIN PGP SIGNED MESSAGE-----
Hi!
I just finished posting to the NetBSD tech-userlevel list to ask if
there is somebody integrating Kerberos v5 with NetBSD.
If there is already somebody with that job, I'll talk to them. If
not, I would be happy to tackle it, since my employer is interested in
having a fully-Kerberized NetBSD/pmax environment, and I've already
started work on the NetBSD login program and friends.
I'd like to know where the Kerberos developers stand on this issue. I
think NetBSD is aiming for builtin Kerberos support (in all the
appropriate clients and servers), and I was wondering what the best
development procedure would be.
There is considerable overlap in terms of the code distributed with
Kerberos (I'm thinking of the Unix client/server code), and the code
that is already in NetBSD.
To me, it makes sense that the typical NetBSD user would simply
download the latest Kerberos library code, set
KERBEROS5 = yes
in /usr/share/mk/bsd.own.mk, then recompile the appropriate NetBSD
sources.
So, how can we avoid overlap and start sharing UNIX client/server
code? Would it make sense to have a separate krb5.clients package,
for those OSes that don't support Kerberos, and just have the
libraries and admin stuff in a krb5.lib distribution?
Thanks in advance for your replies,
- --Gord
- --
Gord Matzigkeit | Jaques Cousteau loved programming in assembler.
gord@enci.ucalgary.ca | PGP mail preferred... finger me for my key.
Keyprint: D5 66 08 E0 4D F4 D7 7B 8A C8 8A 9C 7F 39 25 A7 - ID 339ABEB9
-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface
iQCVAwUBMM4RWyFsfCEzmr65AQFj6gP9EtXkVeJ0YmR2ti7sLucjlXe6z0CYKw17
MYgN3wylAYMIuRRGHDL9iOq596Njgi3yE6RruJU7Bz8Z1m53rjRCiJVg2V/zmMQu
C+ImBPeOxGRL8alYgfJY3O0gGyvKSEFZaadWsSrefkqr3q+WwHJTuN3OhDG2mk/n
JvKychx5Kro=
=66vw
-----END PGP SIGNATURE-----
