summaryrefslogtreecommitdiff
path: root/security/heimdal
AgeCommit message (Collapse)AuthorFilesLines
2005-05-31Packages have no business modifying PKG_DEFAULT_OPTIONS -- it's adillo1-5/+3
user settable variable. Set PKG_SUGGESTED_OPTIONS instead. Also, make use of PKG_OPTIONS_LEGACY_VARS. Reviewed by wiz.
2005-05-22Remove USE_GNU_TOOLS and replace with the correct USE_TOOLS definitions:jlam1-2/+2
USE_GNU_TOOLS -> USE_TOOLS awk -> gawk m4 -> gm4 make -> gmake sed -> gsed yacc -> bison
2005-05-11Rename MAKE_VARS to MAKEVARS so that it more closely resemblesjlam1-2/+2
"MAKEFLAGS". Both "MAKEVARS" and "MAKEFLAGS" affect the package-level make process, not the software's own make process.
2005-05-11I mixed up MAKE_FLAGS with MAKEFLAGS. The latter is what we actually usejlam1-3/+3
to pass make flags to bmake.
2005-05-09Don't assign to PKG_OPTIONS.<pkg> which has special meaning to thejlam1-6/+6
options framework. Rename PKG_OPTIONS.* to PKG_BUILD_OPTIONS.*.
2005-05-09Teach bsd.pkg.mk to create a phase-specific "makevars.mk" file thatjlam1-3/+3
caches variable definitions that were computed by make. These variables are specified by listing them in MAKE_VARS, e.g., .if !defined(FOO) FOO!= very_time_consuming_command .endif MAKE_VARS+= FOO bsd.pkg.mk will include only the one generated during the most recent phase. A particular phase's makevars.mk file consists of variable definitions that are a superset of all of the ones produced in previous phases of the build. The caching is useful because bsd.pkg.mk invokes make recursively, which in the example above has the potential to run the very time-consuming command each time unless we cause FOO to be defined for the sub-make processes. We don't cache via MAKE_FLAGS because MAKE_FLAGS isn't consistently applied to every invocation of make, and also because MAKE_FLAGS can overflow the maximum length of a make variable very quickly if we add many values to it. One important and desirable property of variables cached via MAKE_VARS is that they only apply to the current package, and not to any dependencies whose builds may have been triggered by the current package. The makevars.mk files are generated by new targets fetch-vars, extract-vars, patch-vars, etc., and these targets are built during the corresponding real-* target to ensure that they are being invoked with PKG_PHASE set to the proper value. Also, remove the variables cache file that bsd.wrapper.mk was generating since the new makevars.mk files provide the same functionality at a higher level. Change all WRAPPER_VARS definitions that were used by the old wrapper-phase cache file into MAKE_VARS definitions.
2005-05-08PKG_OPTIONS.<pkg> isn't a good approximation to PKG_OPTIONS for thejlam1-2/+8
package because PKG_OPTION.<pkg> could contain negative options, which are never part of PKG_OPTIONS. Instead, use the show-var target to display the value. We cache it in WRAPPER_VARS and in MAKE_FLAGS to prevent reinvoking the show-var target recursively.
2005-05-02RCD_SCRIPTS_EXAMPLEDIR is no longer customizable.reed1-1/+2
And always is defined as share/examples/rc.d which was the default before. This rc.d scripts are not automatically added to PLISTs now also. So add to each corresponding PLIST as required. This was discussed on tech-pkg in late January and late April. Todo: remove the RCD_SCRIPTS_EXAMPLEDIR uses in MESSAGES and elsewhere and remove the RCD_SCRIPTS_EXAMPLEDIR itself.
2005-04-21Update to Heimdal 0.6.4. While I'm here, claim maintainership of thislha4-36/+22
package. Also please pkglint. Changes in heimdal 0.6.4 include: * fix vulnerabilities in telnet * rshd: encryption without a separate error socket should now work * telnet now uses appdefaults for the encrypt and forward/forwardable settings * bug fixes
2005-04-21lha agreed to maintain this package.wiz1-2/+2
2005-04-11Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used.tv1-2/+1
2005-02-24Add RMD160 digests.agc1-1/+2
2004-12-28The default location of the pkgsrc-installed rc.d scripts is nowreed1-2/+2
under share/examples/rc.d. The variable name already was named RCD_SCRIPTS_EXAMPLEDIR. This is from ideas from Greg Woods and others. Also bumped PKGREVISION for all packages using RCD_SCRIPTS mechanism (as requested by wiz).
2004-12-23Enable building heimdal with the "ldap" option to allow using an LDAPjlam1-7/+6
server as a datastore for the KDC.
2004-12-14Change the way that openssl/builtin.mk handles the USE_OLD_DES_API flag.jlam3-53/+3
The idea is to prevent needing to patch source files for packages that use OpenSSL for DES support by ensuring that including <openssl/des.h> will always present the old DES API. (1) If des_old.h exists, then we're using OpenSSL>=0.9.7, and <openssl/des.h> already does the right thing. (2) If des_old.h doesn't exist, then one of two things is happening: (a) If <openssl/des.h> is old and (only) supports the old DES API, then <openssl/des.h> does the right thing. (b) If it's NetBSD's Special(TM) one that stripped out the old DES support into a separate library and header (-ldes, <des.h>), then we create a new header <openssl/des.h> that includes the system one and <des.h>. Also modify existing packages that set USE_OLD_DES_API to simply include <openssl/des.h> instead of either <des.h> or <openssl/des_old.h> (This step is mostly just removing unnecessary patches). This should fix building packages that use OpenSSL's old DES API support on non-NetBSD systems where the built-in OpenSSL is at least 0.9.7.
2004-12-04Set USE_OLD_DES_API and replace custom changes to work with NetBSD-2.0'sjlam4-148/+55
OpenSSL, with patches to use <openssl/des_old.h>.
2004-11-28Remove pre-buildlink and post-buildlink as part of getting pkgsrc readyjlam1-2/+2
for pkgsrc-2004Q4. The "buildlink" phase was removed for the last branch, and this is the final cleanup. "post-buildlink" is now "post-wrapper".
2004-11-19Correctly detect the old DES API in the OpenSSL in NetBSD's basejlam4-8/+152
install. This prevents Heimdal from building and installing its own DES library and headers. Bump the PKGREVISION.
2004-11-15Add a new variable BROKEN_READLINE_DETECTION which should be set tojlam1-10/+4
yes/no by a package Makefile, depending on whether the configure process properly detects the additional libraries needed to link against -lreadline (typically, you need either "-lreadline -ltermcap", or "-lreadline -lcurses" to properly link against -lreadline). If this variable is set to "yes", then we automatically expand "-lreadline" into "-lreadline -l<termcap functions library>". BROKEN_READLINE_DETECTION defaults to "no". Set BROKEN_READLINE_DETECTION to "yes" in security/heimdal and remove the custom logic that did the same work.
2004-11-09Fix location of heimdal mirror at ftp.sunet.se.jlam1-2/+2
2004-10-19Don't list the info/ files. This uses INFO_FILES so theyreed1-4/+1
are automatically registered.
2004-10-19This needs a yacc.reed1-1/+2
So used: USE_GNU_TOOLS+= yacc (But it didn't necessarily need a GNU version.)
2004-10-06Undefine open in ndbm_wrap.c. This fixes a build problem on Solaris.gavan2-1/+14
2004-10-03Libtool fix for PR pkg/26633, and other issues. Update libtool to 1.5.10tv2-3/+4
in the process. (More information on tech-pkg.) Bump PKGREVISION and BUILDLINK_DEPENDS of all packages using libtool and installing .la files. Bump PKGREVISION (only) of all packages depending directly on the above via a buildlink3 include.
2004-09-22Mechanical changes to package PLISTs to make use of LIBTOOLIZE_PLIST.jlam1-2/+1
All library names listed by *.la files no longer need to be listed in the PLIST, e.g., instead of: lib/libfoo.a lib/libfoo.la lib/libfoo.so lib/libfoo.so.0 lib/libfoo.so.0.1 one simply needs: lib/libfoo.la and bsd.pkg.mk will automatically ensure that the additional library names are listed in the installed package +CONTENTS file. Also make LIBTOOLIZE_PLIST default to "yes".
2004-09-15The configure script checks for some libraries the wrong order, sincejlam1-3/+11
-lreadline also needs either -ltermcap, -lcurses, -lncurses in the link command to resolve all symbols used in the readline library. Cause one of these libraries to automatically be added whenever "-lreadline" appears on the command line. This is a generalization of the change in revision 1.6 to work on more operating systems.
2004-09-15Include buildlink3.mk files for packages needed to satisfy libraryjlam1-1/+12
dependencies. This fixes link failures when the Heimdal dependency is satisfied by the package rather than the builtin Heimdal. Pointed out by Mark Davies in private email. I've intentionally left out including readline/buildlink3.mk. Although it is used by libsl.* and libss.*, those libraries are not actually critical or used by other packages that depend on Heimdal for Kerberos functionality.
2004-09-14Teach builtin.mk about the latest releases of Heimdal and match them upjlam1-1/+4
with NetBSD versions.
2004-09-14Update security/heimdal to 0.6.3. Changes from version 0.6.1 include:jlam5-63/+17
* fix vulnerabilities in ftpd * support for linux AFS /proc "syscalls" * support for RFC3244 (Windows 2000 Kerberos Change/Set Password) in kpasswdd * fix possible KDC denial of service * Fix possible buffer overrun in v4 kadmin (which now defaults to off)
2004-08-22Change the way that legacy USE_* and FOO_USE_* options are convertedjlam1-11/+3
into the bsd.options.mk framework. Instead of appending to ${PKG_OPTIONS_VAR}, it appends to PKG_DEFAULT_OPTIONS. This causes the default options to be the union of PKG_DEFAULT_OPTIONS and any old USE_* and FOO_USE_* settings. This fixes PR pkg/26590.
2004-08-05It's PKG_OPTIONS.heimdal, not PKG_OPTIONS.mit-krb5.jlam1-4/+4
2004-07-30Convert to use bsd.options.mk. The relevant options variable to setjlam1-10/+23
for each package can be determined by invoking: make show-var VARNAME=PKG_OPTIONS_VAR The old options are still supported unless the variable named in PKG_OPTIONS_VAR is set within make(1) (usually via /etc/mk.conf).
2004-07-24Honor VARBASE; bump PKGREVISION.jlam1-2/+3
2004-06-25Cede maintainership to the hard-working people on tech-pkg@NetBSD.org.jlam1-2/+2
2004-06-25Whitespace nits.jlam1-11/+11
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.
generated by cgit v1.2.3 (git 2.39.1) at 2024-06-30 12:49:53 +0000