Downloads of v 0.10.0-rc1:


Last Update:

07 Apr 2018

Package Maintainer(s):

Software Author(s):

  • Mitchell Hashimoto
  • HashiCorp


vault hashicorp


This is a prerelease version of Vault.

0.10.0-rc1 | Updated: 07 Apr 2018



Downloads of v 0.10.0-rc1:



Software Author(s):

  • Mitchell Hashimoto
  • HashiCorp

Vault 0.10.0-rc1

This is a prerelease version of Vault.

All Checks are Passing

2 Passing Test

Validation Testing Passed

Verification Testing Passed


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 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

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'"

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

Exit $exitCode

- name: Ensure vault installed
    name: vault
    state: present
    version: 0.10.0-rc1
    source: STEP 3 URL

See docs at

Coming early 2020! Central Managment Reporting available now! More information...

chocolatey_package 'vault' do
  action    :install
  version  '0.10.0-rc1'
  source   'STEP 3 URL'

See docs at

    Name: vault,
    Version: 0.10.0-rc1,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller vault
   Name     = 'vault'
   Ensure   = 'Present'
   Version  = '0.10.0-rc1'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'vault':
  provider => 'chocolatey',
  ensure   => '0.10.0-rc1',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install vault version="0.10.0-rc1" source="STEP 3 URL"

See docs at

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 07 Apr 2018.


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.

$checksum = '269b56a3a956b4648f450881577d3c50d1808a5adede995819bc682763711b85'
$checksum64 = 'df19cf317809ab42561d5ef41c48ab337f5ec26ccc519ceb9d18a73e8bb825ee'
$version = '0.10.0-rc1'
$url = "$($version)/vault_$($version)"
$url64bit = "$($version)/vault_$($version)"

$unzipLocation = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"

Install-ChocolateyZipPackage -PackageName "vault" -Url "$url" -UnzipLocation "$unzipLocation" -Url64 "$url64bit" -ChecksumType 'sha256' -Checksum "$checksum" -Checksum64 "$checksum64"

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.1 614 Thursday, January 21, 2021 Approved
Vault 1.5.5 3175 Friday, October 23, 2020 Approved
Vault 1.5.4 1582 Thursday, October 22, 2020 Approved
Vault 1.5.3 230 Thursday, October 22, 2020 Approved
Vault 1.5.2 2210 Wednesday, August 26, 2020 Approved
Vault 1.5.0 1490 Wednesday, July 22, 2020 Approved
Vault 1.4.3 784 Friday, July 3, 2020 Approved
Vault 1.4.1 1628 Monday, May 4, 2020 Approved
Vault 1.4.0 1269 Thursday, April 9, 2020 Approved

0.10.0-RC1 (April 4th, 2018)


  • Removal of returned secret information: For a long time Vault has returned configuration given to various secret engines and auth methods with secret values (such as secret API keys or passwords) still intact, and with a warning to the user on write that anyone with read access could see the secret. This was mostly done to make it easy for tools like Terraform to judge whether state had drifted. However, it also feels quite un-Vault-y to do this and we've never felt very comfortable doing so. In 0.10 we have gone through and removed this bevhavior from the various backends; fields which contained secret values are simply no longer returned on read. We are working with the Terraform team to make changes to their provider to accommodate this as best as possible, and users of other tools may have to make adjustments, but in the end we felt that the ends did not justify the means and we needed to prioritize security over operational convenience.
  • LDAP auth method case sensitivity: We now treat usernames and groups configured locally for policy assignment in a case insensitive fashion by default. Existing configurations will continue to work as they do now; however, the next time a configuration is written case_sensitive_names will need to be explicitly set to true.


  • Versioned K/V: The kv backend has been completely revamped, featuring flexible versioning of values, check-and-set protections, and more. A new vault kv subcommand allows friendly interactions with it. Existing mounts of the kv backend can be upgraded to the new versioned mode (downgrades are not currently supported). The old "passthrough" mode is still the default for new mounts; versioning can be turned on by setting the -options flag for the vault secrets enable command to specify versioned=true. This may become the default between the beta and final release.
  • Database Root Credential Rotation: Database configurations can now rotate their own configured admin/root credentials, allowing configured credentials for a database connection to be rotated immediately after sending them into Vault, invalidating the old credentials and ensuring only Vault knows the actual valid values.
  • Azure Authentication Plugin: There is now a plugin (pulled in to Vault) that allows authenticating Azure machines to Vault using their Azure-provided credentials. See the plugin repository for more information.
  • GCP Secrets Plugin: There is now a plugin (pulled in to Vault) that allows generating secrets to allow access to GCP. See the plugin repository for more information.
  • Selective Audit HMACing of Request and Response Data Keys: HMACing in audit logs can be turned off for specific keys in the request input map and response data map on a per-mount basis.
  • Passthrough Request Headers: Request headers can now be selectively passed through to backends on a per-mount basis. This is useful in various cases when plugins are interacting with external services.
  • HA for Google Cloud Storage: The GCS storage type now supports HA.
  • UI support for identity - add and edit entities, groups, and their associated aliases.
  • UI auth method support - enable, disable, and configure all of the built-in authentication methods.
  • UI (Enterprise) - View and edit Sentinel policies.


  • core: Centralize TTL generation for leases in core [GH-4230]
  • identity: API to update group-alias by ID [GH-4237]
  • secret/cassandra: Update Cassandra storage delete function to not use batch operations [GH-4054]
  • storage/mysql: Allow setting max idle connections and connection lifetime [GH-4211]
  • storage/gcs: Add HA support [GH-4226]
  • ui - add Nomad to the list of available secret engines


  • auth/token: Revoke-orphan and tidy operations now correctly cleans up the parent prefix entry in the underlying storage backend. These operations also mark corresponding child tokens as orphans by removing the parent/secondary index from the entries. [GH-4193]
  • command: Re-add -mfa flag and migrate to OSS binary [GH-4223]
  • core: Fix issue occurring from mounting two auth backends with the same path with one mount having auth/ in front [GH-4206]
  • mfa: Invalidation of MFA configurations (Enterprise)
  • replication: Fix a panic on some non-64-bit platforms
  • replication: Fix invalidation of policies on performance secondaries
  • secret/pki: When tidying if a value is unexpectedly nil, delete it and move on [GH-4214]
  • storage/s3: Fix panic if S3 returns no Content-Length header [GH-4222]
  • ui: Fixed an issue where the UI was checking incorrect paths when operating on transit keys. Capabilities are now checked when attempting to encrypt / decrypt, etc.
  • ui: Fixed IE 11 layout issues and JS errors that would stop the application from running.
  • ui: Fixed the link that gets rendered when a user doesn't have permissions to view the root of a secret engine. The link now sends them back to the list of secret engines.

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