From owner-freebsd-current Sat Feb 10 15:32:45 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA17997 for current-outgoing; Sat, 10 Feb 1996 15:32:45 -0800 (PST) Received: from wa3ymh.transsys.com (#6@wa3ymh.TransSys.COM [144.202.42.42]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id PAA17991 for ; Sat, 10 Feb 1996 15:32:35 -0800 (PST) Received: from wa3ymh.transsys.com (#6@localhost.TransSys.COM [127.0.0.1]) by wa3ymh.transsys.com (8.7.3/8.7.3) with ESMTP id SAA09404; Sat, 10 Feb 1996 18:32:16 -0500 (EST) Message-Id: <199602102332.SAA09404@wa3ymh.transsys.com> To: "Garrett A. Wollman" cc: Warner Losh , current@freebsd.org From: "Louis A. Mamakos" Subject: Re: Kerberos @ freebsd.org? In-reply-to: Your message of "Sat, 10 Feb 1996 16:56:41 EST." <9602102156.AA12462@halloran-eldar.lcs.mit.edu> Date: Sat, 10 Feb 1996 18:32:12 -0500 Sender: owner-current@freebsd.org Precedence: bulk > < said: > > > I'm not sure what the exact interoperability status is. To date I've > > just usered our version to access machines that are running our > > version. I've heard conflicting things about eBones vs KerberosIV. > > I have not had any interoperability difficulty between FreeBSD's > eBones and real, honest-to-God MIT Kerberos v4. Nor have I had any interoperability problems between FreeBSD's eBones (both 2.1R and now 2.2-960130-SNAP) and the Cynus "version" of Kerberos. Works great. louie