Downloads:

46,772

Downloads of v 1.7.0:

487

Last Update:

06 Apr 2021

Package Maintainer(s):

Software Author(s):

  • Mitchell Hashimoto
  • HashiCorp

Tags:

vault hashicorp

Vault

1.7.0 | Updated: 06 Apr 2021

Downloads:

46,772

Downloads of v 1.7.0:

487

Maintainer(s):

Software Author(s):

  • Mitchell Hashimoto
  • HashiCorp

Vault 1.7.0

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

To install Vault, run the following command from the command line or from PowerShell:

>

To upgrade Vault, run the following command from the command line or from PowerShell:

>

To uninstall Vault, run the following command from the command line or from PowerShell:

>

NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to https://community.chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade vault -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade vault -y --source="'STEP 3 URL'"
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode

- name: Ensure vault installed
  win_chocolatey:
    name: vault
    state: present
    version: 1.7.0
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.


chocolatey_package 'vault' do
  action    :install
  version  '1.7.0'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: vault,
    Version: 1.7.0,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller vault
{
   Name     = 'vault'
   Ensure   = 'Present'
   Version  = '1.7.0'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'vault':
  provider => 'chocolatey',
  ensure   => '1.7.0',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install vault version="1.7.0" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package was approved as a trusted package on 06 Apr 2021.

Description

Vault is a tool for securely accessing secrets. A secret is anything that you want to tightly control access to, such as API keys, passwords, certificates, and more. Vault provides a unified interface to any secret, while providing tight access control and recording a detailed audit log.

A modern system requires access to a multitude of secrets: database credentials, API keys for external services, credentials for service-oriented architecture communication, etc. Understanding who is accessing what secrets is already very difficult and platform-specific. Adding on key rolling, secure storage, and detailed audit logs is almost impossible without a custom solution. This is where Vault steps in.

The key features of Vault are:

* Secure Secret Storage: Arbitrary key/value secrets can be stored in Vault. Vault encrypts these secrets prior to writing them to persistent storage, so gaining access to the raw storage isn't enough to access your secrets. Vault can write to disk, Consul, and more.
* Dynamic Secrets: Vault can generate secrets on-demand for some systems, such as AWS or SQL databases. For example, when an application needs to access an S3 bucket, it asks Vault for credentials, and Vault will generate an AWS keypair with valid permissions on demand. After creating these dynamic secrets, Vault will also automatically revoke them after the lease is up.
* Data Encryption: Vault can encrypt and decrypt data without storing it. This allows security teams to define encryption parameters and developers to store encrypted data in a location such as SQL without having to design their own encryption methods.
* Leasing and Renewal: All secrets in Vault have a lease associated with it. At the end of the lease, Vault will automatically revoke that secret. Clients are able to renew leases via built-in renew APIs.
* Revocation: Vault has built-in support for secret revocation. Vault can revoke not only single secrets, but a tree of secrets, for example all secrets read by a specific user, or all secrets of a particular type. Revocation assists in key rolling as well as locking down systems in the case of an intrusion.

For more information, see the introduction section of the Vault website.


tools\chocolateyInstall.ps1
$packageArgs = @{
  PackageName         = "vault"
  Url                 = "https://releases.hashicorp.com/vault/$($version)/vault_$($version)_windows_386.zip"
  UnzipLocation       = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
  Url64               = "https://releases.hashicorp.com/vault/$($version)/vault_$($version)_windows_amd64.zip"
  Checksum            = '00f5ebf7660ff93013cfb7c1d904e0fb7feb909cdf22b9fafd78d058b6898c52'
  ChecksumType        = 'sha256'
  Checksum64          = 'b192e31e2c0ddc001ca39b25fb4b3c99e916f41e7dc2713ab1b542ce7304bf37'
  version             = '1.7.0'  
}

Install-ChocolateyZipPackage @packageArgs

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
Vault 1.6.3 383 Thursday, March 25, 2021 Approved
Vault 1.6.2 3135 Monday, February 1, 2021 Approved
Vault 1.6.1 617 Thursday, January 21, 2021 Approved
Vault 1.5.5 3184 Friday, October 23, 2020 Approved
Vault 1.5.4 2042 Thursday, October 22, 2020 Approved
Vault 1.5.3 236 Thursday, October 22, 2020 Approved
Vault 1.5.2 2216 Wednesday, August 26, 2020 Approved
Vault 1.5.0 1532 Wednesday, July 22, 2020 Approved
Vault 1.4.3 787 Friday, July 3, 2020 Approved

1.7.0

### 24 March 2021

CHANGES:

* go: Update Go version to 1.15.10

FEATURES:

* Aerospike Storage Backend: Add support for using Aerospike as a storage backend
* Autopilot for Integrated Storage: A set of features has been added to allow for automatic operator-friendly management of Vault servers. This is only applicable when integrated storage is in use.
* Dead Server Cleanup: Dead servers will periodically be cleaned up and removed from the Raft peer set, to prevent them from interfering with the quorum size and leader elections.
* Server Health Checking: An API has been added to track the state of servers, including their health.
* New Server Stabilization: When a new server is added to the cluster, there will be a waiting period where it must be healthy and stable for a certain amount of time before being promoted to a full, voting member.
* Tokenization Secrets Engine (Enterprise): The Tokenization Secrets Engine is now generally available. We have added support for MySQL, key rotation, and snapshot/restore.
* agent: Support for persisting the agent cache to disk
* auth/jwt: Adds max_age role parameter and auth_time claim validation.
* core (enterprise): X-Vault-Index and related headers can be used by clients to manage eventual consistency.
* kmip (enterprise): Use entropy augmentation to generate kmip certificates
* sdk: Private key generation in the certutil package now allows custom io.Readers to be used.
* secrets/aws: add IAM tagging support for iam_user roles
* secrets/database/cassandra: Add ability to customize dynamic usernames
* secrets/database/couchbase: Add ability to customize dynamic usernames
* secrets/database/mongodb: Add ability to customize dynamic usernames
* secrets/database/mssql: Add ability to customize dynamic usernames
* secrets/database/mysql: Add ability to customize dynamic usernames
* secrets/database/postgresql: Add ability to customize dynamic usernames
* secrets/db/snowflake: Added support for Snowflake to the Database Secret Engine
* secrets/keymgmt (enterprise): Adds beta support for distributing and managing keys in AWS KMS.
* secrets/keymgmt (enterprise): Adds general availability for distributing and managing keys in Azure Key Vault.
* secrets/openldap: Added dynamic roles to OpenLDAP similar to the combined database engine
* secrets/terraform: New secret engine for managing Terraform Cloud API tokens
* ui: Adds check for feature flag on application, and updates namespace toolbar on login if present
* ui: Adds the wizard to the Database Secret Engine
* ui: Database secrets engine, supporting MongoDB only

IMPROVEMENTS:

* agent: Add template-retry stanza to agent config.
* agent: Agent can now run as a Windows service.
* agent: Better concurrent request handling on identical requests proxied through Agent.
* agent: Route templating server through cache when persistent cache is enabled.
* agent: change auto-auth to preload an existing token on start
* auth/ldap: Improve consistency in error messages
* auth/okta: Adds support for Okta Verify TOTP MFA.
* changelog: Add dependencies listed in dependencies/2-25-21
* command/debug: Now collects logs (at level trace) as a periodic output.
* core (enterprise): "vault status" command works when a namespace is set.
* core (enterprise): Update Trial Enterprise license from 30 minutes to 6 hours
* core/metrics: Added "vault operator usage" command.
* core/metrics: New telemetry metrics reporting lease expirations by time interval and namespace
* core: Added active since timestamp to the status output of active nodes.
* core: Check audit device with a test message before adding it.
* core: Track barrier encryption count and automatically rotate after a large number of operations or on a schedule
* core: add metrics for active entity count
* core: add partial month client count api
* core: dev mode listener allows unauthenticated sys/metrics requests
* core: reduce memory used by leases
* secrets/gcp: Truncate ServiceAccount display names longer than 100 characters.
* storage/raft (enterprise): Listing of peers is now allowed on DR secondary
cluster nodes, as an update operation that takes in DR operation token for
authenticating the request.
* transform (enterprise): Improve FPE transformation performance
* transform (enterprise): Use transactions with batch tokenization operations for improved performance
* ui: Clarify language on usage metrics page empty state
* ui: Customize MongoDB input fields on Database Secrets Engine
* ui: Upgrade Ember-cli from 3.8 to 3.22.
* ui: Upgrade Storybook from 5.3.19 to 6.1.17.
* ui: Upgrade date-fns from 1.3.0 to 2.16.1.
* ui: Upgrade dependencies to resolve potential JS vulnerabilities
* ui: better errors on Database secrets engine role create

BUG FIXES:

* agent: Only set the namespace if the VAULT_NAMESPACE env var isn't present
* agent: Set TokenParent correctly in the Index to be cached.
* agent: Set namespace for template server in agent.
* api/sys/config/ui: Fixes issue where multiple UI custom header values are ignored and only the first given value is used
* api: Fixes CORS API methods that were outdated and invalid
* auth/jwt: Fixes bound_claims validation for provider-specific group and user info fetching.
* auth/jwt: Fixes an issue where JWT verification keys weren't updated after a jwks_url change.
* auth/jwt: Fixes an issue where jwt_supported_algs were not being validated for JWT auth using
jwks_url and jwt_validation_pubkeys.
* auth/oci: Fixes alias name to use the role name, and not the literal string name
* consul-template: Update consul-template vendor version and associated dependencies to master,
* core (enterprise): Limit entropy augmentation during token generation to root tokens.
* core (enterprise): Vault EGP policies attached to path * were not correctly scoped to the namespace.
* core/identity: Fix deadlock in entity merge endpoint.
* core: Avoid deadlocks by ensuring that if grabLockOrStop returns stopped=true, the lock will not be held.
* core: Avoid disclosing IP addresses in the errors of unauthenticated requests
* core: Fix client.Clone() to include the address
* core: Fix duplicate quotas on performance standby nodes.
* core: Fix rate limit resource quota migration from 1.5.x to 1.6.x by ensuring purgeInterval and
staleAge are set appropriately.
* core: Make all APIs that report init status consistent, and make them report
initialized=true when a Raft join is in progress.
* core: Make the response to an unauthenticated request to sys/internal endpoints consistent regardless of mount existence.
* core: Turn off case sensitivity for allowed entity alias check during token create operation.
* http: change max_request_size to be unlimited when the config value is less than 0
* license: Fix license caching issue that prevents new licenses to get picked up by the license manager
* metrics: Protect emitMetrics from panicking during post-seal
* quotas/rate-limit: Fix quotas enforcing old rate limit quota paths
* replication (enterprise): Fix bug with not starting merkle sync while requests are in progress
* secrets/database/influxdb: Fix issue where not all errors from InfluxDB were being handled
* secrets/database/mysql: Fixes issue where the DisplayName within generated usernames was the incorrect length
* secrets/database: Sanitize private_key field when reading database plugin config
* secrets/gcp: Fix issue with account and iam_policy roleset WALs not being removed after attempts when GCP project no longer exists
* secrets/transit: allow for null string to be used for optional parameters in encrypt and decrypt
* serviceregistration: Fix race during shutdown of Consul service registration.
* storage/raft (enterprise): Automated snapshots with Azure required specifying
azure_blob_environment, which should have had as a default AZUREPUBLICCLOUD.
* storage/raft (enterprise): Reading a non-existent auto snapshot config now returns 404.
* storage/raft (enterprise): The parameter aws_s3_server_kms_key was misnamed and
didn't work. Renamed to aws_s3_kms_key, and make it work so that when provided
the given key will be used to encrypt the snapshot using AWS KMS.
* transform (enterprise): Fix bug tokenization handling metadata on exportable stores
* transform (enterprise): Fix bug where tokenization store changes are persisted but don't take effect
* transform (enterprise): Fix transform configuration not handling stores parameter on the legacy path
* transform (enterprise): Make expiration timestamps human readable
* transform (enterprise): Return false for invalid tokens on the validate endpoint rather than returning an HTTP error
* ui: Add role from database connection automatically populates the database for new role
* ui: Fix bug in Transform secret engine when a new role is added and then removed from a transformation
* ui: Fix bug that double encodes secret route when there are spaces in the path and makes you unable to view the version history.
* ui: Fix expected response from feature-flags endpoint
* ui: Fix footer URL linking to the correct version changelog.

## Previous Releases
For more information on previous releases, check out the changelog on GitHub.


This package has no dependencies.

Discussion for the Vault Package

Ground Rules:

  • This discussion is only about Vault and the Vault package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or Vault, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus