| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Bump PKGREVISION.
|
|
detection doesn't work properly.
|
|
|
|
We are pleased to announce the availability of GnuPG 1.9.17 - the
branch of GnuPG featuring the S/MIME protocol. You should consider
using GnuPG 1.9 if you want to use the GPG-AGENT or GPGSM. The
GPG-AGENT is also helpful when using the stable GPG version 1.4 or if
you want to check out its ssh-agent replacement feature.
GnuPG 1.9 is the current development version of GnuPG. Despite of
that, most parts (in particular GPG-AGENT and GPGSM) are considered
ready for production use. Please keep on using GnuPG 1.4.x for
OpenPGP; 1.9 and 1.4 may - and actually should - be installed
simultaneously.
This release features a partly rewrite of the smartcard access code as
well as several bug fixes and enhancements. Noteworthy things are:
* gpg-connect-agent has now features to handle Assuan INQUIRE
commands.
* Internal changes for OpenPGP cards. New Assuan command WRITEKEY.
* GNU Pth is now a hard requirement.
* [scdaemon] Support for OpenSC has been removed. Instead a new and
straightforward pkcs#15 modules has been written. As of now it
does allows only signing using TCOS cards but we are going to
enhance it to match all the old capabilities.
* [gpg-agent] New option --write-env-file and Assuan command
UPDATESTARTUPTTY.
* [gpg-agent] New option --default-cache-ttl-ssh to set the TTL for
SSH passphrase caching independent from the other passphrases.
You will also need to get a new libassuan (our IPC library).
|
|
adds UPDATESTARTUPTTY to the Assuan protocol.
|
|
|
|
1.6.8p7 include:
562) Fixed noexec functionality on Linux.
564) Fixed a bug that prevented Heimdal authentication from working.
566) A sudoers entry with sudo ALL no longer overwrites the value of
safe_cmnd. This fixes the privilege escalation vulnerability
noted in http://www.courtesan.com/sudo/alerts/path_race.html
|
|
"nessus-plugins". The package can now be installed again after the
recent change to the "nessus-plugins" package.
|
|
Changes in release 0.6.5
* fix vulnerabilities in telnetd
* unbreak Kerberos 4 and kaserver
|
|
version number to 1.37.
|
|
Bump PKGREVISION.
|
|
Bump PKGREVISION.
|
|
- Bump to nb1
- ok'ed wiz@
|
|
Bump PKGREVISION.
|
|
${PREFIX}.
|
|
|
|
|
|
|
|
Approved by hubertf.
|
|
noted by adrianp
|
|
Makefiles where this occurs, edit the file so that we avoid running
the loop. This should fix PR pkg/28809.
|
|
Reviewed by wiz.
|
|
Noted by reed@
Replace ".Xx Ns 's" by ".Xx Ap s" while here.
|
|
version of the software, USE_BUILTIN.<pkg> should be set to "no", not
to ${IS_BUILTIN.<pkg>}.
|
|
|
|
but changed the name of the copyright holder.
I provided the original man page in PR #21865.
|
|
its compatiblity. Bump version to 1.35
Done during the freeze to have the support on the branch.
Okayed by wiz.
|
|
- Problem spotted by wiz@
|
|
Bump PKGREVISION.
|
|
supposed to.
|
|
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.
|
|
XXX: should there be one, replacing USE_INET6?
|
|
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.
|
|
|
|
|
|
|
|
* Version 1.2.4 (2005-05-28)
- Corrected some bugs that could affect 64 bit systems.
- Some corrections in the header files to include the prototype
of memmem properly (affected 64 bit systems). Report and patch
by Yoann Vandoorselaere <yoann@prelude-ids.org>.
- Introduced the --fix-key option to certtool, which can be used to
regenerate the (optional) parameters in a private key. It should
be used together with --key-info.
- Corrected a bug in certificate chain verification that could lead
to marking a trusted chain as non trusted, if the last certificate in
the chain was a self signed one.
- Gnulib portability files were updated.
- License were updated to reflect new FSF address.
|
|
compatibility provided via PKG_OPTIONS_LEGACY_OPTS.
|
|
compatibility provided via PKG_OPTIONS_LEGACY_OPTS.
|
|
user settable variable. Set PKG_SUGGESTED_OPTIONS instead. Also,
make use of PKG_OPTIONS_LEGACY_VARS.
Reviewed by wiz.
|
|
This still works on NetBSD (1.6.2 tested) but also fixes the include error
on Linux (Debian 3 tested) and Solaris (9 tested).
Although DragonFlyBSD, FreeBSD and OpenBSD should work as before I have
not tried to build the package there.
Feedback whether it builds/works on Darwin/MacOS is also welcome.
|
|
|
|
Changes from previous pkgsrc version 2.1.0 include:
apg-2.2.3
Fixed version info (-v).
apg-2.2.2
Fixed permissions for source distribution.
apg-2.2.1
Changed manpages of apg and apgd.
apg-2.2.0
Added polish translation for APG PHP frontend.
Added option -p (see apg(1) apgd(8)).
Added option -t (see apg(1) apgd(8)).
Added option -l (see apg(1)).
Changed format of the bloom-filter file. Added
converter utility to convert old format to the
new one (bfconvert).
Added option -i (see apgbfm(1)).
Fixed some bugs.
Some compatibility changes.
Changed default apg options.
Update provided by Leonard Schmidt <lems@gmx.net> in PR#30345, thanks!
|
|
|
|
and maybe other platforms.
Bump PKGREVISION.
|
|
and extra pam file was not included in +CONTENTS.
So moved the include of options.mk to after the PLIST_SRC and
MESSAGE_SRC are defined as empty.
(MESSAGE_SRC is redefined if Interix and if PAM PKG_OPTION was enabled
then this still needs to be fixed.)
|
|
|
|
and LEX is "flex". They break when full paths are passed to the
configure script via YACC and LEX (!!).
|
|
|
|
|
