summaryrefslogtreecommitdiff
path: root/security/openssh+gssapi
AgeCommit message (Collapse)AuthorFilesLines
2005-12-29Remove USE_PKGINSTALL from pkgsrc now that mk/install/pkginstall.mkjlam1-2/+1
automatically detects whether we want the pkginstall machinery to be used by the package Makefile.
2005-12-05Ran "pkglint --autofix", which corrected some of the quoting issues inrillig1-6/+6
CONFIGURE_ARGS.
2005-12-05Fixed pkglint warnings. The warnings are mostly quoting issues, forrillig1-4/+4
example MAKE_ENV+=FOO=${BAR} is changed to MAKE_ENV+=FOO=${BAR:Q}. Some other changes are outlined in http://mail-index.netbsd.org/tech-pkg/2005/12/02/0034.html
2005-10-07Remove MANDIR usage in PLIST (like I did for openssh packagereed2-19/+15
in July). And remove CONFIGURE_ARGS for --mandir as this is now done for GNU_CONFIGURE.
2005-08-23The real user name in PKG_USERS does not need to be escaped with doublerillig1-2/+2
backslashes anymore. A single backslash is enough. Changed the definition in all affected packages. For those that are not caught, an additional check is placed into bsd.pkginstall.mk.
2005-08-19Merge CONF_FILES/SUPPORT_FILES and CONF_FILES_PERMS/SUPPORT_FILES_PERMSjlam1-8/+3
as the INSTALL and DEINSTALL scripts no longer distinguish between the two types of files. Drop SUPPORT_FILES{,_PERMS} and modify the packages in pkgsrc accordingly.
2005-07-16Get rid of USE_PERL5. The new way to express needing the Perl executablejlam1-4/+2
around at either build-time or at run-time is: USE_TOOLS+= perl # build-time USE_TOOLS+= perl:run # run-time Also remove some places where perl5/buildlink3.mk was being included by a package Makefile, but all that the package wanted was the Perl executable.
2005-06-01Remove mk/autoconf.mk and mk/automake.mk and replace their usage withjlam1-3/+3
USE_TOOLS and any of "autoconf", "autoconf213", "automake" or "automake14". Also, we don't need to call the auto* tools via ${ACLOCAL}, ${AUTOCONF}, etc., since the tools framework takes care to symlink the correct tool to the correct name, so we can just use aclocal, autoconf, etc.
2005-05-31Rename option PAM to pam (so all options are lower case). Backwardsdillo1-4/+4
compatibility provided via PKG_OPTIONS_LEGACY_OPTS.
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-28Add CONFLICTS with lsh (common man page).wiz1-1/+2
2005-04-11Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used.tv1-2/+1
2005-02-24Add RMD160 digests.agc1-1/+3
2005-02-07Instantly deprecate USE_PAM from pkgsrc as its value is being set fromjlam1-3/+7
within NetBSD-current's bsd.own.mk, which conflicts with its usage in pkgsrc. The package that use USE_PAM have been converted to use the bsd.options.mk framework. This should fix PR pkg/29257.
2005-01-14Create a pam.buildlink3.mk file that is used by PAM-using packages.jlam1-2/+2
It includes the correct buildlink3.mk file from either Linux-PAM (security/PAM) or OpenPAM (security/openpam) and eventually will support solaris-pam. pam.buildlink3.mk will: * set PAMBASE to the base directory of the PAM files; * set PAM_TYPE to the PAM implementation used. There are two variables that can be used to tweak the selection of the PAM implementation: PAM_DEFAULT is a user-settable variable whose value is the default PAM implementation to use. PAM_ACCEPTED is a package-settable list of PAM implementations that may be used by the package. Modify most packages that include PAM/buildlink3.mk to include pam.buildlink3.mk instead.
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-10-03Libtool fix for PR pkg/26633, and other issues. Update libtool to 1.5.10tv1-2/+2
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-06-15Resurrect openssh+gssapi per request of jwise@.kristerw16-0/+568
2004-06-01Remove obsolete packages, per discussion on tech-pkg.kristerw16-568/+0
2004-05-11Convert to buildlink3.snj1-7/+7
2004-04-27Don't support the updating the in-tree openssh via pkgsrc. pkgsrc reallyjlam2-60/+1
has no business trying to update parts of the base system.
2004-04-23mk/bsd.pkg.install.mk now automatically registersreed2-5/+2
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-03-26PKGREVISION bump after openssl-security-fix-update to 0.9.6m.wiz1-2/+2
Buildlink files: RECOMMENDED version changed to current version.
2004-02-07Don't set LD=${CC} globally, but only pass it to CONFIGURE_ENV, which isjlam1-2/+2
the only relevant place that wants it.
2003-09-17Update for _new_ new OpenSSH patch, bump pkgrevision.jwise4-10/+71
``Oops, they did it again.''
2003-09-16Apply security patch for OpenSSH-3.6.1p2 recently released by openssh team.jwise3-5/+33
PKGREVISION bump, and BROKEN= removed. While there, fix Solaris short pkg name.
2003-09-16Mark this package as broken until an updated version of the openssh+gssapijwise1-1/+3
patch is available, as OpenSSH-3.6.1p2 contains another buffer overflow.
2003-09-11Garbage-collect USE_OPENSSL_VERSION now that openssl/buildlink2.mk supportsjlam1-4/+1
just setting BUILDLINK_DEPENDS.openssl. USE_OPENSSL_VERSION wasn't actually needed here anyway since the minimum version allowed by openssl/buildlink2.mk exceeded the version requested here.
2003-08-30Add definitions for DEINSTALL_EXTRA_TMPL and INSTALL_EXTRA_TMPL ifjlam1-1/+3
USE_PKGINSTALL is "YES". bsd.pkg.install.mk will no longer automatically pick up a INSTALL/DEINSTALL script in the package directory and assume that you want it for the corresponding *_EXTRA_TMPL variable.
2003-08-30Prepare for pkgviews by making sure that passing VIEW-INSTALL orjlam1-16/+16
VIEW-DEINSTALL to the INSTALL/DEINSTALL scripts don't cause errors.
2003-08-05We need explicit -lcrypto on -current (at least with gcc3), and it does nojwise1-2/+2
harm on older versions, so bring it in explicitly.
2003-08-01This needs to define KERBEROS or the section which adds the right librariesjmc1-1/+2
never gets included and nothing links.
2003-07-24Make difference between this package and ../openssh clearer in DESCR andjwise2-9/+7
COMMENT, and add comment to Makefile explaining why we copy, rather than source, files from ../openssh.
2003-07-24Import package for openssh+gssapi, which is openssh-3.6.1p2 with versionjwise15-0/+541
20030430 of the GSSAPI patches from http://www.sxw.org.uk/computing/patches/openssh.html . From the site: The patches on this page are concerned with adding support for authenticating users via their Kerberos credentials, and allowing authenticated users to forward their credentials to a remote machine over ssh. These patches are against various versions of the OpenSSH portable code. SSH has both a legacy protocol version 1, and a newer, protocol version 2 (which is being standardised in the IETF). Techniques exist for performing Kerberos authentication over both protocols, and GSSAPI authentication over protocol version 2. In this package standard ssh support for kerberos versions 4 and 5 is kept for version 1 of the ssh protocol (openssh does not support kerberos 4 in ssh protocol version 2). These patches, which provide a much more thorough implementation of kerberos 5 support than that shipped with openssh, are pkg'ed here with an eye toward evaluation of their usefullness for inclusion in the base os.
generated by cgit v1.2.3 (git 2.39.1) at 2025-01-05 12:12:03 +0000