pkgsrc-Changes-HG archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

[pkgsrc/trunk]: pkgsrc/security/vault security/vault: Update to 0.9.6



details:   https://anonhg.NetBSD.org/pkgsrc/rev/ab7f1e548982
branches:  trunk
changeset: 377819:ab7f1e548982
user:      fhajny <fhajny%pkgsrc.org@localhost>
date:      Fri Mar 23 12:00:12 2018 +0000

description:
security/vault: Update to 0.9.6

DEPRECATIONS/CHANGES:

- The AWS authentication backend now allows binds for inputs as either a
  comma-delimited string or a string array. However, to keep consistency with
  input and output, when reading a role the binds will now be returned as
  string arrays rather than strings.
- In order to prefix-match IAM role and instance profile ARNs in AWS auth
  backend, you now must explicitly opt-in by adding a `*` to the end of the
  ARN. Existing configurations will be upgraded automatically, but when
  writing a new role configuration the updated behavior will be used.

FEATURES:

- Replication Activation Enhancements: When activating a replication
  secondary, a public key can now be fetched first from the target cluster.
  This public key can be provided to the primary when requesting the
  activation token. If provided, the public key will be used to perform a
  Diffie-Hellman key exchange resulting in a shared key that encrypts the
  contents of the activation token. The purpose is to protect against
  accidental disclosure of the contents of the token if unwrapped by the wrong
  party, given that the contents of the token are highly sensitive. If
  accidentally unwrapped, the contents of the token are not usable by the
  unwrapping party. It is important to note that just as a malicious operator
  could unwrap the contents of the token, a malicious operator can pretend to
  be a secondary and complete the Diffie-Hellman exchange on their own; this
  feature provides defense in depth but still requires due diligence around
  replication activation, including multiple eyes on the commands/tokens and
  proper auditing.

IMPROVEMENTS:

- api: Update renewer grace period logic. It no longer is static, but rather
  dynamically calculates one based on the current lease duration after each
  renew.
- auth/approle: Allow array input for bound_cidr_list
- auth/aws: Allow using lists in role bind parameters
- auth/aws: Allow binding by EC2 instance IDs
- auth/aws: Allow non-prefix-matched IAM role and instance profile ARNs
- auth/ldap: Set a very large size limit on queries
- core: Log info notifications of revoked leases for all leases/reasons, not
  just expirations
- physical/couchdb: Removed limit on the listing of items
- secret/pki: Support certificate policies
- secret/pki: Add ability to have CA:true encoded into intermediate CSRs, to
  improve compatibility with some ADFS scenarios
- secret/transit: Allow selecting signature algorithm as well as hash
  algorithm when signing/verifying
- server: Make sure `tls_disable_client_cert` is actually a true value rather
  than just set
- storage/dynamodb: Allow specifying max retries for dynamo client
- storage/gcs: Allow specifying chunk size for transfers, which can reduce
  memory utilization
- sys/capabilities: Add the ability to use multiple paths for capability
  checking

BUG FIXES:

- auth/aws: Fix honoring `max_ttl` when a corresponding role `ttl` is not also
  set
- auth/okta: Fix honoring configured `max_ttl` value
- auth/token: If a periodic token being issued has a period greater than the
  max_lease_ttl configured on the token store mount, truncate it. This matches
  renewal behavior; before it was inconsistent between issuance and renewal.
- cli: Improve error messages around `vault auth help` when there is no CLI
  helper for a particular method

diffstat:

 security/vault/Makefile |   5 ++---
 security/vault/distinfo |  10 +++++-----
 2 files changed, 7 insertions(+), 8 deletions(-)

diffs (28 lines):

diff -r ad0f469191cd -r ab7f1e548982 security/vault/Makefile
--- a/security/vault/Makefile   Fri Mar 23 11:55:06 2018 +0000
+++ b/security/vault/Makefile   Fri Mar 23 12:00:12 2018 +0000
@@ -1,7 +1,6 @@
-# $NetBSD: Makefile,v 1.24 2018/03/04 15:52:19 bsiegert Exp $
+# $NetBSD: Makefile,v 1.25 2018/03/23 12:00:12 fhajny Exp $
 
-DISTNAME=      vault-0.9.5
-PKGREVISION=   1
+DISTNAME=      vault-0.9.6
 CATEGORIES=    security
 MASTER_SITES=  ${MASTER_SITE_GITHUB:=hashicorp/}
 
diff -r ad0f469191cd -r ab7f1e548982 security/vault/distinfo
--- a/security/vault/distinfo   Fri Mar 23 11:55:06 2018 +0000
+++ b/security/vault/distinfo   Fri Mar 23 12:00:12 2018 +0000
@@ -1,6 +1,6 @@
-$NetBSD: distinfo,v 1.16 2018/02/27 11:20:42 fhajny Exp $
+$NetBSD: distinfo,v 1.17 2018/03/23 12:00:12 fhajny Exp $
 
-SHA1 (vault-0.9.5.tar.gz) = e2f354049c2e10a2fe7947433b9d3a33e5449cb0
-RMD160 (vault-0.9.5.tar.gz) = 3c5228391283a1bd60f9fba8ff1c3901e3a5422c
-SHA512 (vault-0.9.5.tar.gz) = 1f07835c7e1e0109b1f1f7c5456f3e11ad14f71cb021e8a432e5b9e6ac14f7f25230a8cbc56da085f83cd1936ec6cc7ad9c83dd89d7e205a95fb95780cf7f40c
-Size (vault-0.9.5.tar.gz) = 9669007 bytes
+SHA1 (vault-0.9.6.tar.gz) = 715a361a0547fb1d771a227393c3dd6df9e35fe5
+RMD160 (vault-0.9.6.tar.gz) = 61785d65c3ed311ede75e24a51e1ed5a48f07024
+SHA512 (vault-0.9.6.tar.gz) = 31c6a39f2a5ebce79660f9ba7b673f95042ab283681de016a9540da17b6a938a45762cf4b4625cf35545fe80716e212a9ee362abe5c6fca52eafd5322b6b0de4
+Size (vault-0.9.6.tar.gz) = 10464094 bytes



Home | Main Index | Thread Index | Old Index