|non port: databases/postgresql83-contrib/Makefile
Number of commits found: 6
Thursday, 4 Apr 2013
The PostgreSQL Global Development Group has released a security
update to all current versions of the PostgreSQL database system,
including versions 9.2.4, 9.1.9, 9.0.13, and 8.4.17. This update
fixes a high-exposure security vulnerability in versions 9.0 and
later. All users of the affected versions are strongly urged to apply
the update *immediately*.
A major security issue (for versions 9.x only) fixed in this release,
makes it possible for a connection request containing a database name
that begins with "-" to be crafted that can damage or destroy files
within a server's data directory. Anyone with access to the port the
PostgreSQL server listens on can initiate this request. This issue was
discovered by Mitsumasa Kondo and Kyotaro Horiguchi of NTT Open Source
Two lesser security fixes are also included in this release:
wherein random numbers generated by contrib/pgcrypto functions may be
easy for another database user to guess (all versions), and
which mistakenly allows an unprivileged user to run commands that
could interfere with in-progress backups (for versions 9.x only).
Approved by: portmgr (bdrewery)
Friday, 8 Mar 2013
Convert USE_BISON to USES= bison
It brings bison as a build dependency in case it is set the following way:
USES= bison or USES= bison:build
it brings bison as a run dependency in case it is set the following way:
it brings bison both as a run and build dependency in case it the set the
While here trim some headers
Convert some USE_GNOME= gnomehack to USES= pathfix
Saturday, 20 Oct 2012
- hardcode --with-openssl for slave 83/84 postgresql contrib ports
with hat pgsql@
Spotted by: beatmail (ie. pointyhat)
Feature safe: yes
Sunday, 4 Mar 2012
Over to new team, pgsql@FreeBSD.org
Thursday, 19 Jan 2012
- Reset ports due to maintainer timeouts and lack of response to emails
With hat: portmgr
Thursday, 20 May 2010
Update all PostgreSQL ports to latest version.
Remove postgresql-contrib in favour for postgresqlNN-contrib.
This way we will get packages built, which is nice.
The PostgreSQL Project today released minor versions updating all active
branches of the PostgreSQL object-relational database system, including
versions 8.4.4, 8.3.11, 8.2.17, 8.1.21, 8.0.25, and 7.4.29. This release
fixes moderate-risk security issues with PL/perl and PL/tcl, as well as
a data corruption issue with standby databases. Users of any of these
three features should update their PostgreSQL installations immediately.
The PL/perl security fix closes a security hole in PL/perl
procedures which could allow privilege escalation on the host system,
caused by a flaw in Safe.pm; see CVE-2010-1169 and CVE-2010-1447 for
details. A second patch prevents PL/tcl's pltcl_modules table from
being subverted in order to run arbitrary Tcl scripts; see
CVE-2010-1170. These issues only affect users who have enabled either
of these two stored procedure languages.
Also corrected is use of the command ALTER TABLE SET TABLESPACE, which
previously could cause data corruption on Warm Standby database slaves.
This issue affects only version 8.4.
There are also 21 other bug fixes in this release, some of which apply
only to version 8.4, and a few of which are specifically for Windows.
While these are generally fixes for minor issues, among the changes are:
* Fix for a combinational crash condition
* Prevent normal users from resetting some GUCs in
their own role definitions
* Correctly apply constraint exclusion in UPDATE and DELETE queries
* Minor fixes for WAL archiving
* Update timezone data for 12 zones
See the release notes for a full list of changes with details.
Releasenotes at http://www.postgresql.org/docs/current/static/release.html
Number of commits found: 6