postgis (2.1.3+dfsg-1) unstable; urgency=high

  It has come to our attention that the PostGIS Raster support
  may give more privileges to users than an administrator is
  willing to grant.

  These include reading files from the filesystem and opening
  connections to network hosts.

  Both issues can be limited in existing installations by setting
  the GDAL_SKIP variable (in the PostgreSQL server environment)
  to the list of all gdal drivers, but some drivers would still be
  forceably loaded by some operations.

  This release strengthens the code to load no drivers by default
  and allows for a fine-grained tuning of what's allowed and what
  not through postgis-specific environment variables:

  - POSTGIS_GDAL_ENABLED_DRIVERS
    Specifies a list of GDAL drivers to _enable_ (rather than _skip_)
    By default all drivers are disabled.
    Example value: "GTiff PNG JPEG"

  - POSTGIS_ENABLE_OUTDB_RASTERS
    Enables read support for out-db raster bands if set to 1.
    By default out-db raster bands reading is disabled.

  On Debian, you can easily set these via the following file:
  /etc/postgresql/${PG_VERSION}/${CLUSTER_NAME}/environment

 -- Markus Wanner <markus@bluegap.ch>  Wed, 21 May 2014 10:49:10 +0200