## 0.11.2 (October 2nd, 2018)

CHANGES:

- `sys/seal-status` now includes an `initialized` boolean in the
  output. If Vault is not initialized, it will return a `200` with
  this value set `false` instead of a `400`.
- `passthrough_request_headers` will now deny certain headers from
  being provided to backends based on a global denylist.

FEATURES:

- AWS Secret Engine Root Credential Rotation: The credential used by
  the AWS secret engine can now be rotated, to ensure that only Vault
  knows the credentials it is using.
- Storage Backend Migrator: A new `operator migrate` command allows
  offline migration of data between two storage backends.
- AliCloud KMS Auto Unseal and Seal Wrap Support (Enterprise):
  AliCloud KMS can now be used a support seal for  Auto Unseal and
  Seal Wrapping.

BUG FIXES:

- auth/okta: Fix reading deprecated `token` parameter if a token was
  previously set in the configuration
- core: Re-add deprecated capabilities information for now
- core: Fix handling of cyclic token relationships
- storage/mysql: Fix locking on MariaDB
- replication: Fix DR API when using a token
- identity: Ensure old group alias is removed when a new one is
  written
- storage/alicloud: Don't call uname on package init
- secrets/jwt: Fix issue where request context would be canceled too
  early
- ui: fix need to have update for aws iam creds generation
- ui: fix calculation of token expiry

IMPROVEMENTS:

- auth/aws: The identity alias name can now configured to be either
  IAM unique ID of the IAM Principal, or ARN of the caller identity
- auth/cert: Add allowed_organizational_units support
- cli: Format TTLs for non-secret responses
- identity: Support operating on entities and groups by their names
- plugins: Add `env` parameter when registering plugins to the catalog
  to allow operators to include environment variables during plugin
  execution.
- secrets/aws: WAL Rollback improvements
- secrets/aws: Allow specifying STS role-default TTLs
- secrets/pki: Add configuration support for setting NotBefore
- core: Support for passing the Vault token via an Authorization
  Bearer header
- replication: Reindex process now runs in the background and does not
  block other vault operations
- storage/zookeeper: Enable TLS based communication with Zookeeper
- ui: you can now init a cluster with a seal config
- ui: added the option to force promote replication clusters
- replication: Allow promotion of a secondary when data is syncing
  with a "force" flag

2 files changed, 7 insertions, 7 deletions

diff --git a/security/vault/Makefile b/security/vault/Makefile
index 5ea13c9e263..7f3302041c6 100644
--- a/security/vault/Makefile
+++ b/security/vault/Makefile
@@ -1,6 +1,6 @@
-# $NetBSD: Makefile,v 1.32 2018/09/06 20:41:53 fhajny Exp $
+# $NetBSD: Makefile,v 1.33 2018/10/07 20:19:38 fhajny Exp $
 
-DISTNAME=	vault-0.11.1
+DISTNAME=	vault-0.11.2
 CATEGORIES=	security
 MASTER_SITES=	${MASTER_SITE_GITHUB:=hashicorp/}
 
diff --git a/security/vault/distinfo b/security/vault/distinfo
index 4f725d7b340..f3a06254e64 100644
--- a/security/vault/distinfo
+++ b/security/vault/distinfo
@@ -1,6 +1,6 @@
-$NetBSD: distinfo,v 1.21 2018/09/06 20:41:53 fhajny Exp $
+$NetBSD: distinfo,v 1.22 2018/10/07 20:19:38 fhajny Exp $
 
-SHA1 (vault-0.11.1.tar.gz) = 06bcc72f2f4cbcc03ce9f3be6e986e75be481681
-RMD160 (vault-0.11.1.tar.gz) = ccfb2809b2ab0245a9a7cd834cea13b32e094747
-SHA512 (vault-0.11.1.tar.gz) = b9cbd8862d6bfe4f6e41f6fb916497af0429dde3ce15bb8c808cd57ca6c0e52e95ba165f4d57fd7051a611ac869e54d7b5758f6fc059ad6474c93353a4b14201
-Size (vault-0.11.1.tar.gz) = 24595293 bytes
+SHA1 (vault-0.11.2.tar.gz) = edf3693416121ed75244afab37db1bad491733b1
+RMD160 (vault-0.11.2.tar.gz) = 27c7f6a5a8148c993c746b4be7198caa6b37a4f0
+SHA512 (vault-0.11.2.tar.gz) = 2feacee3180aee48a868e40fe295bb96196c84b0cfb4b6486dee5c0899f5baaa4f45a1a1ca0939fad8ca062ca97d5e256b66dd6e91f88471816e41ccf991dc03
+Size (vault-0.11.2.tar.gz) = 24804472 bytes