[3055] in Kerberos
Kerberos source code
daemon@ATHENA.MIT.EDU (georges rahbani)
Tue Mar 29 14:19:01 1994
Date: Tue, 29 Mar 1994 08:12:13 -0800
To: kerberos@MIT.EDU
From: georgesr@wrq.com (georges rahbani)
Cc: georgesr@elmer.wrq.com
Hi,
I have posted a message asking for help on how to get to the Kerberos
source code. I have received many helpful replies so I thought to post some
ways to get access to the code so that the new people (like myself) to
Kerberos may find this information helpful.
First, I would like to thank all of those who replied to my message.
Second, An easy way to get oriented to the world of Kerberos is to get a
copy of the FAQ (Frequetly Asked Questions) file. This is a text file that
resides on various archives on the net. In it you will find the location of
the compressed source code and how to access it.
Third, another way to gain more knowledge about Kerberos (ver V) is to read
the RFC1510. Again this is available on various archives on the net.
Fourth, ftp in BINARY mode the kerberos "*.tar.Z" files. The current beta 3
version is available from ATHENA-DIST.MIT.EDU in /pub/kerberos/dist/941701.
Fifth, uncompress and extract the files to their original form using
whatever tool you might be familiar with. Some of these are:
* "zcat file.tar.Z | tar xpvf -" This will uncompress the file ".Z"
before extracting the contents. You may have to experiment with the tar options.
* gtar with -z option. This should have the same effect as above.
* I have not tried the following method, but I included it here to be
complete on my description of the replies I got and as an appreciation
gesture to all who are willing to help.
>I, like you, am new to Kerberos, but I think I can help you with the
>source code. The files you downloaded should have been ksrc.01.shar -
>ksrc.35.shar. These are actually self extracting shell scripts. If
>you create a directory structure ( the make files expect /mit/kerberos/src
>but you can call it anything you want), and execute each of the files in
>turn, you should have the source code. But that's the easy part.
I hope you will find this information helpful. And if I unintentionally
provided any erroneous information please correct me on them with a message
to the group.
Georges Rahbani
Walker, Richer & Quinn, Inc.
georgesr@wrq.com
