| |
|
From bjaspan@MIT.EDU Tue Nov 26 16:55:03 1996
Received: from MIT.EDU (SOUTH-STATION-ANNEX.MIT.EDU [18.72.1.2]) by rt-11.MIT.EDU
(8.7.5/8.7.3) with SMTP id QAA18441 for <bugs@RT-11.MIT.EDU>; Tue, 26 Nov 1996
16:55:03 -0500
Received: from THE-TICK.MIT.EDU by MIT.EDU with SMTP
id AA25830; Tue, 26 Nov 96 16:55:01 EST
Received: by the-tick.MIT.EDU (940816.SGI.8.6.9/4.7) id VAA21440; Tue, 26 Nov 1996
21:55:00 GMT
Message-Id: <199611262155.VAA21440@the-tick.MIT.EDU>
Date: Tue, 26 Nov 1996 21:55:00 GMT
From: bjaspan@MIT.EDU
Reply-To: bjaspan@MIT.EDU
To: krb5-bugs@MIT.EDU, krbdev@MIT.EDU
Subject: binary distributions don't contain krb5.conf or kdc.conf
X-Send-Pr-Version: 3.99
>Number: 249
>Category: krb5-build
>Synopsis: binary distributions don't contain krb5.conf or kdc.conf
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: tlyu
>State: open
>Class: sw-bug
>Submitter-Id: unknown
>Arrival-Date: Tue Nov 26 16:56:01 EST 1996
>Last-Modified: Fri Nov 29 19:58:49 EST 1996
>Originator: Barry Jaspan
>Organization:
mit
>Release: 1.0-development
>Environment:
System: IRIX the-tick 5.3 02091401 IP22 mips
>Description:
A binary distribution created according to the build-instructions file
does not end up containing a sample krb5.conf and kdc.conf. Given
that the major purpose of the binary distributions is to make it very
easy to sample krb5, this is unfortunate.
The install rule in src/config-files, which already exists, could
easily install the sample files in, say, share/config-files.
Comments on priority?
>How-To-Repeat:
>Fix:
>Audit-Trail:
From: "Theodore Y. Ts'o" <tytso@MIT.EDU>
To: krb5-bugs@MIT.EDU, bjaspan@MIT.EDU
Cc: tlyu@MIT.EDU, gnats-admin@RT-11.MIT.EDU, krb5-prs@RT-11.MIT.EDU
Subject: Re: krb5-build/249: binary distributions don't contain krb5.conf or kdc.conf
Date: Tue, 26 Nov 1996 22:03:11 -0500
Actually, I'm beginning to think the right answer is for the sample
configuration files to go into the *documentation* tree.
My proposal is for the 1.0 release, to add a new directory,
doc/sample-config-files containing the sample configuration files into
the documentation tree, and then after the 1.0 release, we'll remove
krb5.conf, kdc.conf, and services.append from src/config-files.
Comments?
- Ted
From: "Barry Jaspan" <bjaspan@MIT.EDU>
To: tytso@MIT.EDU
Cc: krb5-bugs@MIT.EDU, tlyu@MIT.EDU, gnats-admin@rt-11.MIT.EDU,
krb5-prs@rt-11.MIT.EDU
Subject: Re: krb5-build/249: binary distributions don't contain krb5.conf or kdc.conf
Date: Wed, 27 Nov 1996 17:24:39 GMT
Actually, I'm beginning to think the right answer is for the sample
configuration files to go into the *documentation* tree.
That sound's sensible.
Barry
( Forwarded from [250] )
From: Ezra Peisach <epeisach@MIT.EDU>
Subject: Re: binary distributions don't contain krb5.conf or kdc.conf
To: bjaspan@MIT.EDU
Cc: krb5-bugs@MIT.EDU, krbdev@MIT.EDU
Date: Tue, 26 Nov 1996 17:01:32 EST
I really would prefer not having to change the tarball...
Question: Would the sample files be appropriate to install in share/config-files?
Would we be better off providing next to the binary distribution
a tarball containing these shared files? (And indicate that
users should get both - at least for this release).
Ezra
>Unformatted:
|
Download (untitled) 3.3k
|
