summaryrefslogtreecommitdiff
path: root/security/heimdal
AgeCommit message (Collapse)AuthorFilesLines
2004-01-15Support a new yes/no variable "KERBEROS_PREFIX_CMDS" that can be used byjlam2-19/+30
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-13Fix build with gcc3.markd2-1/+17
2004-01-13whitespace.jlam1-9/+9
2004-01-11Note CONFLICT with forthcoming mit-krb5 package.jlam1-1/+3
2004-01-10Add a rc.d script to start the kdc daemon on the Kerberos master server.jlam2-1/+26
2004-01-10Back out previous. This doesn't work as expected and needs more thought.jlam1-4/+2
2004-01-10The buildlink3 wrappers automatically remove -I/usr/include/* from thejlam1-2/+4
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-10Initial import of heimdal-0.6 into security/heimdal.jlam9-0/+718
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.