pkgsrc - [no description]

Age	Commit message (Collapse)	Author	Files	Lines
2004-03-28	Fix the Kerberized telnetd and rsh to use the Heimdal binaries for	jlam	1	-8/+26
	login and rsh so that the correct programs (and not the system ones) are executed. Bump the PKGREVISION to 3.
2004-03-26	Reverse the use of USE_DB185 in bdb.buildlink3.mk -- it defaults to	jlam	1	-2/+1
	"yes" and packages that can't use the DB-1.85 API should set it to "no". This makes the native DB the preferred DB if it exists.
2004-03-26	PKGREVISION bump after openssl-security-fix-update to 0.9.6m.	wiz	1	-2/+2
	Buildlink files: RECOMMENDED version changed to current version.
2004-03-10	Convert to use bdb.buildlink3.mk.	jlam	1	-2/+2

2004-02-23	Let the rc.d script start kdc detached, as is the default for	wiz	1	-1/+2
	the in-tree kdc. From Jukka Salmi in PR 24489, ok'd by lukem@. Bump PKGREVISION to 1.
2004-02-22	configure looks for and finds -ltermcap too late in the process for it to	markd	1	-1/+7
	be linked in when testing -lreadline usability so that test fails on Solaris - so pass that lib into configure at the start via the environment. Also allow optional use of db4 rather that db.
2004-02-14	LIBTOOL_OVERRIDE and SHLIBTOOL_OVERRIDE are now lists of shell globs	jlam	1	-2/+1
	relative to ${WRKSRC}. Remove redundant LIBTOOL_OVERRIDE settings that are automatically handled by the default setting in bsd.pkg.mk.
2004-01-15	Support a new yes/no variable "KERBEROS_PREFIX_CMDS" that can be used by	jlam	1	-6/+16
	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-11	Note CONFLICT with forthcoming mit-krb5 package.	jlam	1	-1/+3

2004-01-10	Add a rc.d script to start the kdc daemon on the Kerberos master server.	jlam	1	-1/+2

2004-01-10	Initial import of heimdal-0.6 into security/heimdal.	jlam	1	-0/+64
	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.