summaryrefslogtreecommitdiff
path: root/security/heimdal
AgeCommit message (Collapse)AuthorFilesLines
2004-04-23mk/bsd.pkg.install.mk now automatically registersreed1-2/+1
the RCD_SCRIPTS rc.d script(s) to the PLIST. This GENERATE_PLIST idea is part of Greg A. Woods' PR #22954. This helps when the RC_SCRIPTS are installed to a different ${RCD_SCRIPTS_EXAMPLEDIR}. (Later, the default RCD_SCRIPTS_EXAMPLEDIR will be changed to be more clear that they are the examples.) These patches also remove the etc/rc.d/ scripts from PLISTs (of packages that use RCD_SCRIPTS). (This also removes now unused references from openssh* makefiles. Note that qmail package has not been changed yet.) I have been doing automatic PLIST registration for RC_SCRIPTS for over a year. Not all of these packages have been tested, but many have been tested and used. Somethings maybe to do: - a few packages still manually install the rc.d scripts to hard-coded etc/rc.d. These need to be fixed. - maybe remove from mk/${OPSYS}.pkg.dist mtree specifications too.
2004-04-01There is no PKGREVISION less than 1. Just remove it in this case.jlam1-2/+1
2004-04-01Update to 0.6.1:joda8-109/+17
* Fixed cross realm vulnerability * Fixed ARCFOUR suppport * kdc: fix denial of service attack * kdc: stop clients from renewing tickets into the future * bug fixes
2004-03-29Note the info file for the new info file handling framework.jlam1-1/+2
2004-03-29Match the template builtin.mk file in bsd.builtin.mk, and make the twojlam1-7/+7
packages that use builtin.mk files (graphics/xpm and pkgtools/x11-links) use the new format correctly.
2004-03-28Fix the Kerberized telnetd and rsh to use the Heimdal binaries forjlam1-8/+26
login and rsh so that the correct programs (and not the system ones) are executed. Bump the PKGREVISION to 3.
2004-03-26Reverse the use of USE_DB185 in bdb.buildlink3.mk -- it defaults tojlam1-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-26PKGREVISION bump after openssl-security-fix-update to 0.9.6m.wiz2-3/+4
Buildlink files: RECOMMENDED version changed to current version.
2004-03-10Convert to use bdb.buildlink3.mk.jlam1-2/+2
2004-03-10Split out the code that deals with checking whether the software isjlam2-111/+87
built-in or not into a separate builtin.mk file. The code to deal checking for built-in software is much simpler to deal with in pkgsrc. The buildlink3.mk file for a package will be of the usual format regardless of the package, which makes it simpler for packagers to update a package. The builtin.mk file for a package must define a single yes/no variable USE_BUILTIN.<pkg> that is used by bsd.buildlink3.mk to decide whether to use the built-in software or to use the pkgsrc software.
2004-02-23Let the rc.d script start kdc detached, as is the default forwiz2-2/+4
the in-tree kdc. From Jukka Salmi in PR 24489, ok'd by lukem@. Bump PKGREVISION to 1.
2004-02-22configure looks for and finds -ltermcap too late in the process for it tomarkd4-2/+63
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-18Reorder some lines so that BUILDLINK_USE_BUILTIN.<pkg> set in thejlam1-16/+18
environment overrides all other settings.
2004-02-14LIBTOOL_OVERRIDE and SHLIBTOOL_OVERRIDE are now lists of shell globsjlam1-2/+1
relative to ${WRKSRC}. Remove redundant LIBTOOL_OVERRIDE settings that are automatically handled by the default setting in bsd.pkg.mk.
2004-02-12Create a new variable PREFER_NATIVE that has the opposite semanticsjlam1-3/+13
as PREFER_PKGSRC. Preferences are determined by the most specific instance of the package in either PREFER_PKGSRC or PREFER_NATIVE. If a package is specified in neither or in both variables, then PREFER_PKGSRC has precedence over PREFER_NATIVE.
2004-02-12Reorganize code so that any dependencies are checked as part of decidingjlam1-36/+35
whether the software is built-in or not. This facilitates implementing the forthcoming PKGSRC_NATIVE variable.
2004-02-06If we're passing through MAKEFLAGS variables whose values may containjlam1-4/+4
spaces, use the :Q modifier instead of double-quoting the value. This avoids breakage when executing the just-in-time su targets.
2004-02-05Make PREFER_PKGSRC just yes/no or a list of packages. This makes itjlam1-5/+3
simpler to understand.
2004-02-05Rename BUILDLINK_PREFER_PKGSRC to PREFER_PKGSRC so that we can use itsjlam1-5/+4
value outside of buildlink-related files.
2004-02-05Support a new global variable:jlam1-1/+9
BUILDLINK_PREFER_PKGSRC This variable determines whether or not to prefer the pkgsrc versions of software that is also present in the base system. This variable is multi-state: defined, or "yes" always prefer the pkgsrc versions not defined, or "no" only use the pkgsrc versions if needed by dependency requirements This can also take a list of packages for which to prefer the pkgsrc-installed software. The package names may be found by consulting the value added to BUILDLINK_PACKAGES in the buildlink[23].mk files for that package.
2004-02-02Pretend that all versions of NetBSD newer than 1.6U have Heimdal-0.6.jlam1-2/+2
2004-01-24Support BUILDLINK_DEPENDS.<pkg> being a list of values.jlam1-5/+9
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.