Received: from PACIFIC-CARRIER-ANNEX.MIT.EDU by po7.MIT.EDU (5.61/4.7) id AA01745; Wed, 20 Dec 95 15:10:07 EST
Received: from relay.hp.com by MIT.EDU with SMTP
	id AA20744; Wed, 20 Dec 95 13:42:30 EST
Date: Wed, 20 Dec 95 13:42:30 EST
From: MAILER-DAEMON@MIT.EDU (Mail Delivery Subsystem)
Subject: Returned mail: Deferred: Bad file number
Message-Id: <9512201842.AA20744@MIT.EDU>
To: owner-kerberos@MIT.EDU

   ----- Transcript of session follows -----
451 pfenning@techfak.uni-bielefeld.de... reply: read error
451 pfenning@techfak.uni-bielefeld.de... reply: read error
421 brownvm.brown.edu.tcp... Deferred: Connection refused by BROWNVM.BROWN.EDU
451 exuksm@exu.ericsson.se... reply: read error
451 exuksm@exu.ericsson.se... reply: read error
421 gardenia.saclay.cea.fr.tcp... Deferred: Connection timed out during user open with oeillet.saclay.cea.fr
>>> RCPT To:<DJMSYS@ritvax.isc.rit.edu>
<<< 553 unknown or illegal user: DJMSYS@ritvax.isc.rit.edu
550 DJMSYS@ritvax.isc.rit.edu... User unknown
451 ncho@gmu.edu... reply: read error
451 ncho@gmu.edu... reply: read error
421 falcon.mbsa.com.tcp... Deferred: Connection timed out during user open with zeos.NetAns.com
451 kerb@athena.tay.dec.com... reply: read error
451 kerb@athena.tay.dec.com... reply: read error
421 amoco.com.tcp... Deferred: Connection timed out during user open with interlock.amoco.com
421 ccm.sns.com.sg.tcp... Deferred: Connection refused by ccm.sns.com.sg
451 watchman@molhub.mol.net.my... reply: read error
451 watchman@molhub.mol.net.my... reply: read error

   ----- Unsent message follows -----
Received: from relay.hp.com by MIT.EDU with SMTP
	id AA20481; Wed, 20 Dec 95 13:42:30 EST
Received: from it_750.ch.apollo.hp.com by relay.hp.com with ESMTP
	(1.37.109.16/15.5+ECS 3.3) id AA082784954; Wed, 20 Dec 1995 10:42:35 -0800
Message-Id: <199512201842.AA082784954@relay.hp.com>
Received: from nyc.ch.apollo.hp.com by it_750.ch.apollo.hp.com 
	id AA268645119; Wed, 20 Dec 1995 13:45:19 -0500    
To: Gord Matzigkeit <gord@enci.ucalgary.ca>
Cc: kerberos@MIT.EDU, mullan_s@apollo.hp.com (Sean Mullan)
Subject: Re: NetBSD liason 
In-Reply-To: <npybsh7t6g.fsf@enci.ucalgary.ca> 
Date: Wed, 20 Dec 1995 13:42:49 -0500
From: Sean Mullan <mullan_s@apollo.hp.com>

On 12 Dec 1995 16:34:31 -0700  Gord Matzigkeit wrote:

>-----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

Hi Gord,

We are currently interested in krb5 versions of the BSD 4.4 remote
utilities (rlogin, rlogind, rsh, rshd). Have you done any work in
this area for NetBSD?

Thanks,
Sean 

************************************************************
Sean Mullan                    Phone: (508) 436-4129
Hewlett-Packard Co.         Internet: mullan_s@apollo.hp.com
300 Apollo Drive                 Fax: (508) 436-5140
Chelmsford, MA 01824
************************************************************

