Commit graph

8 commits

Author SHA1 Message Date
jlam
83532f92f6 Support a new yes/no variable "KERBEROS_PREFIX_CMDS" that can be used by
Kerberos implementation packages to decide whether to prefix certain
commands with a "k" to differentiate it from system tools with similar
names.  KERBEROS_PREFIX_CMDS defaults to "no".
2004-01-15 12:48:00 +00:00
markd
f8c2eb7eb1 Fix build with gcc3. 2004-01-13 02:05:29 +00:00
jlam
18ec955c8a whitespace. 2004-01-13 00:00:32 +00:00
jlam
a41e499e44 Note CONFLICT with forthcoming mit-krb5 package. 2004-01-11 00:00:28 +00:00
jlam
99ac5d408b Add a rc.d script to start the kdc daemon on the Kerberos master server. 2004-01-10 21:59:29 +00:00
jlam
c0a16733a6 Back out previous. This doesn't work as expected and needs more thought. 2004-01-10 21:35:26 +00:00
jlam
ca86c17d51 The buildlink3 wrappers automatically remove -I/usr/include/* from the
command line options.  We need -I/usr/include/krb5 to build against
heimdal, so symlink the headers in /usr/include/krb5 into ${BUILDLINK_DIR}
so they can be found.
2004-01-10 19:44:16 +00:00
jlam
694ff19aff Initial import of heimdal-0.6 into security/heimdal.
Heimdal is a free implementation of Kerberos 5.

Kerberos is a system for authenticating users and services on a network.
It is built upon the assumption that the network is "unsafe".  Kerberos
is a trusted third-party service.  That means that there is a third
party (the Kerberos server) that is trusted by all the entities on the
network (users and services, usually called "principals").  All
principals share a secret password (or key) with the Kerberos server and
this enables principals to verify that the messages from the Kerberos
server are authentic.  Thus trusting the Kerberos server, users and
services can authenticate each other.
2004-01-10 14:56:44 +00:00