Tech Insider					     Technology and Trends


		      Kerberos Mailing List Archives

daemon@TELECOM.MIT.EDU (steiner@ATHENA.MIT.EDU)
Thu May 19 13:00:22 1988

From: steiner@ATHENA.MIT.EDU
To: kerberos@ATHENA.MIT.EDU


Below is a list of people who will be participating
in the Kerberos beta test, along with brief descriptions
of their test environments.

Jennifer

--------

Steve Bellovin <smb@research.att.com> of AT&T Bell Labs.

  We have ~30 Suns running SunOS 3.4, plus several VAXen and a CCI 6/32
  running 4.3bsd.  Our machines are linked via assorted gateways to a
  moderate number of other TCP/IP networks (using assorted technologies).
  We'd really like to run Kerberos on our local nets plus those of one
  affiliated department, since we provide computing services for them
  (though they have their own workstations as well).  Our applications
  include the obvious standards ones (rsh, rlogin, and NFS (our VAXen
  are starting to run Mt. Xinu NFS)), possibly others.

--------
  
Dave Curry <davy@intrepid.ecn.purdue.edu> of Purdue University.

  26 timesharing machines (Vaxes and Goulds), 147 Sun workstations with
  about 100-150 more on order to show up this summer.  We have 7
  different Schools of Engineering in our network; we might make each
  one a different Kerberos realm (or not, depends on some of the
  capabilities of Kerberos).  We have about 12,000 users.  We are
  also connected to the Computer Center and the Computer Science
  department here.

--------

Craig Finset <fin@uf.msc.umn.edu> of the Minnesota Supercomputer Center.

  Our environment includes:
  
  	5 Sun 3/180 and 3/280 computers
  	10 Sun 3/50 and 3/60 diskless workstations
  	2 CRAY-2 supercomputers
  	They are connected via Ethernet and Hyperchannel.
  
  We will initially bring it up on our development computer and some of
  the workstations.  As we gain experience and confidence in it, we will
  expand it to our staff machine, then (ultimately) to our routers.
  Finally, we hope to port it to the Crays (and, after you have released
  the official version, to offer it to our customers).
  
  Initial applications will be to authenticate NFS mounts, to eliminate
  the /bin/su program, and to eliminate .rhosts files.  Later
  applications will be to convert from offering telnet-accessed local
  accounts to direct network access to services.

--------

Jordan Hayes <jordan@ucbarpa.Berkeley.EDU> of Advanced Decision Systems.

  Environment:

  Vaxes, Suns, Pyramids, Intel HyperCube, BBN Butterfly, etc.

  We are a government contractor centering on artificial
  intelligence applications.  We're interested in security,
  on the network and in UNIX in particular.

--------

Greg Kenley <harvard!palladium!gkenley> of Epoch Systems.

  Epoch Systems currently consists of a heterogeneous mix of
  Vaxen, Suns, Macs and PCs and our own DataStation(tm).  The
  DataStation is an ultra high capacity NFS compatable file server
  designed to support the current and next generation of technical 
  workstations.  The common thread amongst all our systems is that 
  they connect via NFS, the Darpa protocols and Ethernet.

--------

Norm Kincl <norm%atom@hplabs.HP.COM> of HP labs.

  We plan to bring Kerberos up on our HP-UX workstations and begin
  experimenting with authentication in various services.

--------

Pierre-Louis Neumann <neumann%inria.inria.fr@uunet.uu.net> of Inria.

  Inria is a governmental research institute in computer
  science.  We use 150 machines connected on an Ethernet:

    100 Sun3 diskless workstations (with 20 Sun servers)
    4 Vax 785 4.3BSD
    2 NP1 Gould
    1 Pyramid
    10 Apollo on their Domain ring network
    the others are French BULL SPS7 (System V.2 + sockets + NFS)

--------

Gary Rosenblum <rosenblg@acf3.nyu.edu> of New York University.

  Our initial test environment will consist of two Vaxen
  running Mt. Xinu's release of 4.3BSD, a Sun 3/180-S server,
  my Sun 3/50 workstation (both running Sun OS 3.4), and a
  Microvax running either 4.3BSD or Xinu's 4.3.  Then we will
  extend to more Vaxen and Sun workstations.
  
  In the summer, a new dorm will open with space for 80 workstations.  We
  plan to stock it with IBM PCs, Mac IIs, and Sun workstations.  Our plan
  is to use Kerberos for authentication of the workstations.  Eventually,
  we hope to include the (approximately) 100 Sun workstations and servers
  on other subnets, on our extended LAN.

--------

Robert Viduya <robert@pyr.gatech.edu> of the Georgia Institute
  of Technology.

  Our environment currently consists of a Pyramid 90x running an
  essentially 4.2BSD kernel, a MicroVAX II running 4.3BSD acting as our
  main network nameserver and two MicroVAX II's running Ultrix 2.2
  acting as fileservers for a cluster of 24 VAXStation 2000's running
  Ultrix 2.2.  In addition, we have two AT&T 3B20's running SysV R2.1.1
  with Wollongong TCP/IP and a few 3B2's running SysV R3.0, also with
  the Wollongong TCP/IP package.  We also have 60 Macintosh II's
  with A/UX (to be installed), and 24 Macintosh II's running MacOS.

--------

Mike Zeleznik <zeleznik@cs.utah.edu> of the University of Utah.

  Two groups within the University of Utah Computer Science Department
  will be working with Kerberos.
  
  1) Utah Retrieval System Architecture (URSA) group:
  
    We are interested in integrating Kerberos with the URSA information
  retrieval system. The URSA system is designed for very large (e.g. 50+
  Gbyte) non-formated databases, supported by custom pattern search
  hardware.  The architecture is message-based, distributed, and
  reconfigurable on the fly (the datacomm package relocates modules and
  reestablishes connections),  with a sophisticated window-based user
  interface.  It has run distributed across Apollo, Sun, and VAX systems,
  on both BSD4.X and native Apollo Aegis (it was designed also for
  portability).  Currently, we are working very closely with Apollo.
  
    We are also involved with the startup of the Univ. of Utah campus
  computing network, currently underway, which could also offer some
  interesting testing possibilities for Kerberos (e.g., multiple
  administrative domains).
  
  2) Computer Science Department systems programming group:

  We have ported 4.3 with NFS to the HP 9000/300 series machines
  (Bobcats), and are investigating using MIT's RVD protocol to provide
  diskless support for these HP workstations.  The current version of RVD
  uses Kerberos.
  
    In addition, in the CS dept's environment of well over 100 Unix hosts,
  we want to investigate Kerberos as a replacement for our current
  Berkeley .rhosts method of authentication, with its well known
  weaknesses.

--------

In addition (people for whom I don't yet have an environment
description) are:

--------

Scott Bradner <sob@harvard.harvard.edu> of Harvard.

--------

Steve Miller of DEC <miller%erlang.DEC@decwrl.dec.com>, one
of the original creators of Kerberos.

--------

Steven M. Miller <smiller@umn-cs.cs.umn.edu> of the
Secure Computing Technology Center of Honeywell.

--------

			        About USENET

USENET (Users’ Network) was a bulletin board shared among many computer
systems around the world. USENET was a logical network, sitting on top
of several physical networks, among them UUCP, BLICN, BERKNET, X.25, and
the ARPANET. Sites on USENET included many universities, private companies
and research organizations. See USENET Archives.

		       SCO Files Lawsuit Against IBM

March 7, 2003 - The SCO Group filed legal action against IBM in the State 
Court of Utah for trade secrets misappropriation, tortious interference, 
unfair competition and breach of contract. The complaint alleges that IBM 
made concentrated efforts to improperly destroy the economic value of 
UNIX, particularly UNIX on Intel, to benefit IBM's Linux services 
business. See SCO vs IBM.

The materials and information included in this website may only be used
for purposes such as criticism, review, private study, scholarship, or
research.

Electronic mail:			       WorldWideWeb:
   tech-insider@outlook.com			  http://tech-insider.org/