summaryrefslogtreecommitdiff
path: root/security/openssl
AgeCommit message (Collapse)AuthorFilesLines
2007-08-04Add a target configuration for Tru64 with gcc.tnn5-22/+64
2007-07-18Compile OpenSSL with supports for threads. This allows an applicationtron1-3/+3
to register callbacks which implement locking primitive to make OpenSSL thread-safe. Bump package revision because of this change.
2007-05-30Removed some code duplication from the buildlink3 files by using the newrillig1-8/+3
pkg-build-options.mk procedure.
2007-05-03Fix typo in "SUBST_MESSAGE.dl".tron1-2/+2
2007-04-26Also link with the "dl" library when creating the shared libraries.tron3-15/+24
Another attempt to fix PR pkg/36086.
2007-04-24Use all necessary means to convince OpenSSL's "special" build systemtron1-4/+10
to link with the "dl" library under Mac OS X if necessary. This should finally fix PR pkg/36086.
2007-04-18Make sure that the "dlcompat" related options are actually added totron1-1/+3
"LDFLAGS". This is another attempt to fix PR pkg/36086.
2007-04-17Because OpenSSL uses dlfcn(3) only internally and Mac OS X supports sharedtron1-3/+1
library dependences we don't need to include "dlopen.buildlink3.mk" here.
2007-04-17Use "pkgsrc/mk/dlopen.buildlink3.mk" instead of manually includingtron2-9/+6
"pkgsrc/devel/dlcompat/buildlink3.mk" under Darwin. This might finally fix PR pkg/36086.
2007-04-01Add ${BUILDLINK_LDFLAGS.dlcompat} (defined as "-ldl") to "LDFLAGS" undertron1-1/+3
Mac OS X. This is harmless under recent versions of Mac OS X where "libdl.dylib" is symbolic link to "libSystem.dylib". And it is necessary under old versions of Mac OS X (Jaguar and older) where we need the "libdl.dylib" from the "dlcompat" package. This should finally fix PR pkg/36086 by John D. Baker.
2007-03-26Include "pkgsrc/devel/dlcompat/buildlink3.mk" when building this packagetron1-1/+5
under Mac OS X. This should fix PR pkg/36086.
2007-02-22Whitespace cleanup, courtesy of pkglint.wiz1-8/+8
Patch provided by Sergey Svishchev in private mail.
2006-12-12Replace mk/bsd.prefs.mk includes with bsd.fast.prefs.mk includes.joerg1-2/+2
The redundant parsing of bsd.prefs.mk is mostly avoided now and parse time e.g. for x11/kdebase3 gets reduced by up to 10%.
2006-12-03Check for GCC on IRIX instead of assuming the native compiler is used.cbiere1-1/+5
2006-09-30Apply patches which fixes recent security problem of OpenSSL.taca14-3/+337
http://secunia.com/advisories/22130/ Bump PKGREVISION.
2006-09-07Add a patch to address CVE-2006-4339adrianp3-3/+32
2006-08-09some apps (dovecot) need the SSLDIR rather than SSLCERTS & SSLKEYSabs1-10/+10
2006-07-08Change the format of BUILDLINK_ORDER to contain depth information as well,jlam1-2/+2
and add a new helper target and script, "show-buildlink3", that outputs a listing of the buildlink3.mk files included as well as the depth at which they are included. For example, "make show-buildlink3" in fonts/Xft2 displays: zlib fontconfig iconv zlib freetype2 expat freetype2 Xrender renderproto
2006-07-08Track information in a new variable BUILDLINK_ORDER that informs usjlam1-1/+2
of the order in which buildlink3.mk files are (recursively) included by a package Makefile.
2006-06-13Forgotten patchsum update.joerg1-2/+2
2006-06-12Add DragonFly support.joerg4-12/+45
2006-04-06Over 1200 files touched but no revisions bumped :)reed2-5/+5
RECOMMENDED is removed. It becomes ABI_DEPENDS. BUILDLINK_RECOMMENDED.foo becomes BUILDLINK_ABI_DEPENDS.foo. BUILDLINK_DEPENDS.foo becomes BUILDLINK_API_DEPENDS.foo. BUILDLINK_DEPENDS does not change. IGNORE_RECOMMENDED (which defaulted to "no") becomes USE_ABI_DEPENDS which defaults to "yes". Added to obsolete.mk checking for IGNORE_RECOMMENDED. I did not manually go through and fix any aesthetic tab/spacing issues. I have tested the above patch on DragonFly building and packaging subversion and pkglint and their many dependencies. I have also tested USE_ABI_DEPENDS=no on my NetBSD workstation (where I have used IGNORE_RECOMMENDED for a long time). I have been an active user of IGNORE_RECOMMENDED since it was available. As suggested, I removed the documentation sentences suggesting bumping for "security" issues. As discussed on tech-pkg. I will commit to revbump, pkglint, pkg_install, createbuildlink separately. Note that if you use wip, it will fail! I will commit to pkgsrc-wip later (within day).
2006-03-30Avoid extra stat() calls by not repeatedly checking whether a filejlam1-5/+7
exists on the disk -- we can just check whether a variable defined by find-files.mk is "__nonexistent__" or not.
2006-03-14Drop maintainership for packages that I no longer have time to maintain.jlam1-2/+2
2006-03-02add support for Solaris/i386 and x86_64, and fallback to the configuregrant1-6/+17
script's auto detection for other archs.
2006-02-05Recursive revision bump / recommended bump for gettext ABI change.joerg2-3/+4
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-27Update patch to also use PKGMANDIR instead of "man" for thereed2-4/+4
MANDIR in the makefile.
2005-12-17Change my MAINTAINER email address to the one I've been using forjlam1-2/+2
pkgsrc work.
2005-12-05Ran "pkglint --autofix", which corrected some of the quoting issues inrillig1-3/+3
CONFIGURE_ARGS.
2005-12-05Fixed pkglint warnings. The warnings are mostly quoting issues, forrillig1-2/+2
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-31Fix build on Interix; it seems % has special meaning in Configure now.tv2-4/+4
2005-10-15Update security/openssl from 0.9.7h to 0.9.7i. Changes from versionjlam2-6/+6
0.9.7h include fixing a shared library upgrade problem where openssl-0.9.7h had a different ABI than previous 0.9.7 sub-revisions due to a changed constant.
2005-10-12If the native openssl-0.9.7d contains the security fixes pulled up tojlam1-3/+16
the netbsd-2-0, netbsd-2, and netbsd-3-0 branches on 2005-10-11, then for the purposes of satisfying dependencies, pretend it's openssl-0.9.7h.
2005-10-12Remove leading "-" from version number when matching the openssl-0.9.6gjlam1-2/+2
from the netbsd-1-6 branch with the 20040401 fix.
2005-10-11Update security/openssl to version 0.9.7h. This is a securityjlam7-53/+54
vulnerability triggered update due to CAN-2005-2969. Changes from version 0.9.7f include: o Fix SSL 2.0 Rollback, CAN-2005-2969 o Allow use of fixed-length exponent on DSA signing o Default fixed-window RSA, DSA, DH private-key operations o More compilation issues fixed. o Adaptation to more modern Kerberos API. o Enhanced or corrected configuration for Solaris64, Mingw and Cygwin. o Enhanced x86_64 assembler BIGNUM module. o More constification. o Added processing of proxy certificates (RFC 3820).
2005-08-16For NetBSD's crippled OpenSSL distribution, create an <openssl/des_old.h>jlam1-2/+10
header in the buildlink directory that just pulls in /usr/include/des.h. This should allow packages that purposely include <openssl/des_old.h> on post-0.9.7 versions of OpenSSL to find it on NetBSD.
2005-07-19the option for fee-based-commercial-use is fee-based-commercial-use,grant1-7/+7
not fee-based-commercial.
2005-07-16Get rid of USE_PERL5. The new way to express needing the Perl executablejlam1-3/+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-11Some shells don't accept empty word lists in for loops. For thosejlam1-1/+16
Makefiles where this occurs, edit the file so that we avoid running the loop. This should fix PR pkg/28809.
2005-06-09Fix copy-and-paste error -- in the case where we prefer the pkgsrcjlam1-2/+2
version of the software, USE_BUILTIN.<pkg> should be set to "no", not to ${IS_BUILTIN.<pkg>}.
2005-06-01Massive cleanup of buildlink3.mk and builtin.mk files in pkgsrc.jlam1-119/+92
Several changes are involved since they are all interrelated. These changes affect about 1000 files. The first major change is rewriting bsd.builtin.mk as well as all of the builtin.mk files to follow the new example in bsd.builtin.mk. The loop to include all of the builtin.mk files needed by the package is moved from bsd.builtin.mk and into bsd.buildlink3.mk. bsd.builtin.mk is now included by each of the individual builtin.mk files and provides some common logic for all of the builtin.mk files. Currently, this includes the computation for whether the native or pkgsrc version of the package is preferred. This causes USE_BUILTIN.* to be correctly set when one builtin.mk file includes another. The second major change is teach the builtin.mk files to consider files under ${LOCALBASE} to be from pkgsrc-controlled packages. Most of the builtin.mk files test for the presence of built-in software by checking for the existence of certain files, e.g. <pthread.h>, and we now assume that if that file is under ${LOCALBASE}, then it must be from pkgsrc. This modification is a nod toward LOCALBASE=/usr. The exceptions to this new check are the X11 distribution packages, which are handled specially as noted below. The third major change is providing builtin.mk and version.mk files for each of the X11 distribution packages in pkgsrc. The builtin.mk file can detect whether the native X11 distribution is the same as the one provided by pkgsrc, and the version.mk file computes the version of the X11 distribution package, whether it's built-in or not. The fourth major change is that the buildlink3.mk files for X11 packages that install parts which are part of X11 distribution packages, e.g. Xpm, Xcursor, etc., now use imake to query the X11 distribution for whether the software is already provided by the X11 distribution. This is more accurate than grepping for a symbol name in the imake config files. Using imake required sprinkling various builtin-imake.mk helper files into pkgsrc directories. These files are used as input to imake since imake can't use stdin for that purpose. The fifth major change is in how packages note that they use X11. Instead of setting USE_X11, package Makefiles should now include x11.buildlink3.mk instead. This causes the X11 package buildlink3 and builtin logic to be executed at the correct place for buildlink3.mk and builtin.mk files that previously set USE_X11, and fixes packages that relied on buildlink3.mk files to implicitly note that X11 is needed. Package buildlink3.mk should also include x11.buildlink3.mk when linking against the package libraries requires also linking against the X11 libraries. Where it was obvious, redundant inclusions of x11.buildlink3.mk have been removed.
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-04-11Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used.tv1-2/+1
2005-03-23Update security/openssl to openssl-0.9.7f.jlam8-117/+214
Pkgsrc changes from version 0.9.7e include: *) Install the man pages with names that are less likely to collide with other packages' man pages. *) Support PKG_OPTIONS of "idea", "mdc2" and "rc5" to allow building with patented algorithms. By default, this package still builds without patented algorithms. Major changes from version 0.9.7e include: *) Prompt for pass phrases when appropriate for PKCS12 input format. *) Back-port of selected performance improvements from development branch, as well as improved support for PowerPC platforms. *) Add lots of checks for memory allocation failure, error codes to indicate failure and freeing up memory if a failure occurs. *) Add new -passin argument to dgst. *) Make an explicit check during certificate validation to see that the CA setting in each certificate on the chain is correct.
generated by cgit v1.2.3 (git 2.39.1) at 2024-06-27 14:29:04 +0000