[1989] in Kerberos_V5_Development
Re: alternatives for signing krb5 1.0
daemon@ATHENA.MIT.EDU (Barry Jaspan)
Wed Nov 20 18:45:12 1996
Date: Wed, 20 Nov 1996 23:44:58 GMT
From: "Barry Jaspan" <bjaspan@MIT.EDU>
To: tytso@MIT.EDU
Cc: hartmans@MIT.EDU, krbdev@MIT.EDU
In-Reply-To: <9611202227.AA21695@dcl.MIT.EDU> (tytso@MIT.EDU)
Ted's suggestion is pretty similar to the proposal I was writing up (I
was writing it because I had nothing else to do and figured Ted would
appreciate the head start). So, I've now enclosed it below. Please
note that this is only a first draft, etc. Anyone who would like to
take it over are welcome.
Barry
--- snip snip ---
----------------------------------------------------------------------
Instructions for creating a binary distribution of Kerberos 5 1.0
----------------------------------------------------------------------
o Begin with a clean copy of the MIT Kerberos 5 1.0 source
distribution. Do NOT use any existing CVS working directory, however
carefully patched.
o Read doc/krb5-install.info or doc/install-guide.ps for full details
on building krb5. When you get to running configure, use the options
configure --with-ccopts=-O --with-krb4 --enable-shared
If the platform does not support shared libraries, configure will
print an error message and exit; re-run it without --enable-shared.
Run make to build the distribution. If you receive any errors, notify
krbdev@mit.edu immediately.
o Run the automated tests:
% make -k check |& tee check.log
Scan through check.log. Tests that fail will be marked by a make
error (typically preceeded by "***"). Tests that are not run because
you do not have the right permissions or software installed will be
marked by "+++" (software) or "# of untested" (permissions). In each
case, the name of tests should be apparent from the error message or
from the directory name printed immediately before the test was, for
example "making check in tests/dejagnu". Make a list of the test
directories containing tests that either failed or did not run so you
can include them in the build information form (see below).
o If you'd like, test the software yourself. Follow the installation
manual to install a Master KDC, create a principal with kadmin, and
test kinit. Set up klogind, kshd, telnetd, or gssftpd on a machine
and attempt to use the services.
o Run make install into an empty directory. For example:
% mkdir /tmp/krb5-1.0
% make install DESTDIR=/tmp/krb5-1.0
o Fill out the build information template below and write the
completed result to the file README.buildinfo in the directory in
which you installed (e.g. /tmp/krb5-1.0/README.buildinfo).
o Create a gzip'ed tar file of the distribution:
% cd /tmp/krb5-dist
% tar cvf - . | gzip --best > /tmp/krb5-1.0-<platform>.tgz
Ted T'so (tytso@mit.edu) will assign the strings to use for <platform>.
o Create a detached PGP signature of the distribution file:
% pgp -sab /tmp/krb5-1.0-<platform>.tgz
o FTP the distribution image and PGP signature to
ftp://XXX/krb5-1.0-<platform>.tgz
ftp://XXX/krb5-1.0-<platform>.asc
o Send email to Ted T'so (tytso@mit.edu) informing him that you have
completed the build, and include another copy of the build information
template.
----------------------------------------------------------------------
Instructions for filling out Kerberos 5 1.0 build information form
----------------------------------------------------------------------
All fields of the build information template must be filled out for
your build to be used. Since you will be signing your build yourself,
you are responsible for the correctness of the information. The
template, which will be included as the README.buildinfo file in each
binary distribution, states that as the builder you assert only that
you compiled the source code as given to you by MIT and that you are
not responsible for any problems resulting from its use.
o Name of builder. Enter your name. This should contain your real
name and e-mail address. You might as well use the name on your PGP
key; for example "Barry Jaspan <bjaspan@mit.edu>".
o Date of build. The date of your build, in MM/DD/YY format.
o Platform. The following two lines identify the platform on which
you compiled the distribution. For Hardware, specify the manufacturer
and major model name of the computer (for example, Sun SPARC). For
OS and Version, specify the name and version of your operating system
(for example, Solaris 2.5).
o Compiler. Specify the compiler you used. If the compiler is a
standard part of the OS, just enter "vendor." If you used some other
compiler, specify the name and version (for example, gcc 2.7.1).
o Compiler options. Specify the compiler options you gave to
configure. This should be "-O", but if you used something else, list
it.
o Tests failed and Tests not run. If you did not run make check at
all, specify "all" for tests not run. Otherwise, list tests that
failed (printing "***") or were not run (printing "+++" or "# of
untested"). If you do not have dejagnu installed, the tests run not
section will include at least lib/rpc, lib/kadm5, kpasswd, and
tests/dejagnu.
o Notes. Any additional information you would like to provide. If
you used different compiler options or the like, explain why. You may
add as many Notes lines as necessary.
---------- cut here ----------
MIT Kerberos 5 1.0 Build Information
The following form describes this Kerberos 5 1.0 binary distribution.
The builder asserts that she or he followed MIT's instructions to
compile and test exactly the source code provided in MIT Kerberos 5
1.0 without modification. The builder makes no other promises about
the distribution; all disclaimers in the top-level README file apply.
Name of builder :
Date of build :
Platform:
Hardware :
OS and version:
Compiler :
Compiler options:
Tests failed :
Tests not run :
Notes :
---------- cut here ----------
