[838] in Kerberos_V5_Development
Re: Planned changes for multiple encryption support....
daemon@ATHENA.MIT.EDU (Theodore Ts'o)
Thu Jan 26 12:03:45 1995
Date: Thu, 26 Jan 1995 12:02:54 +0500
From: Theodore Ts'o <tytso@MIT.EDU>
To: John Kohl <jtk@atria.com>
Cc: krbdev@MIT.EDU
In-Reply-To: John Kohl's message of Thu, 26 Jan 1995 09:45:48 -0500,
<9501261445.AA04463@banana>
Date: Thu, 26 Jan 1995 09:45:48 -0500
From: John Kohl <jtk@atria.com>
Is "krb5_context" an aggregate type or something else? If it's an
aggregate, you don't want to pass it directly (pass a pointer) as you
show in the mail from earlier this week.
krb5_context is a pointer type.
I spoke some more with Chris P.; he thinks you may have more than one
include file to install into the system include file area (he thought it
would be 3). If you have more than one, I strongly suggest you put them
all in a subdirectory and call their names <krb5/file1.h>,
<krb5/file2.h>, etc.
Having slashes in the include file names presents problems for the
Macintosh port. Our requirements for the port include a single source
tree, and minimal amounts of fussing about with the tree in order to get
it to work.
We're currently looking at only one (krb5.h), and *perhaps* another one
(k5-sys.h) that would only be used for user-level daemons (rlogind,
telnetd, etc). The stuff in k5-sys.h could be folded into krb5.h, or
perhaps k5-sys.h might not be installed at all.
I still disgree with you that disaster would strike the earth if we
still more than one include file in the top-level include directory.
- Ted
