Chocolatey Community Coffee Break

Join the Chocolatey Team on our regular monthly stream where we discuss all things Community, what we do, how you can get involved and answer your Chocolatey questions.

Learn More

Chocolatey Product Spotlight

Join the Chocolatey Team on our regular monthly stream where we put a spotlight on the most recent Chocolatey product releases. You'll have a chance to have your questions answered in a live Ask Me Anything format.

Learn More

Announcing Chocolatey Central Management 0.10.0

Livestream from
Thursday, 06 October 2022

We recently released our largest update to Chocolatey Central Management so far. Join Gary and Steph to find out more about Chocolatey Central Management and the new features and fixes we've added to this release.

Watch On-Demand
Chocolatey and Intune Overview

Webinar Replay from
Wednesday, 30 March 2022

At Chocolatey Software we strive for simple, and teaching others. Let us teach you just how simple it could be to keep your 3rd party applications updated across your devices, all with Intune!

Watch On-Demand
Chocolatey For Business. In Azure. In One Click.

Livestream from
Thursday, 9 June 2022

Join James and Josh to show you how you can get the Chocolatey For Business recommended infrastructure and workflow, created, in Azure, in around 20 minutes.

Watch On-Demand
The Future of Chocolatey CLI

Livestream from
Thursday, 04 August 2022

Join Paul and Gary to hear more about the plans for the Chocolatey CLI in the not so distant future. We'll talk about some cool new features, long term asks from Customers and Community and how you can get involved!

Watch On-Demand
Hacktoberfest Tuesdays 2022

Livestreams from
October 2022

For Hacktoberfest, Chocolatey ran a livestream every Tuesday! Re-watch Cory, James, Gary, and Rain as they share knowledge on how to contribute to open-source projects such as Chocolatey CLI.

Watch On-Demand
Chocolatey Product Spotlight: Chocolatey 1.2.0 and Chocolatey Licensed Extension 5.0.0

Livestream from
Thursday, 03 November 2022

Join Paul and Gary for this months Chocolatey product livestream where we look at the latest release of Chocolatey 1.2.0, Chocolatey Licensed Extension 5.0.0 and shine a spotlight on the new hook scripts functionality. This opens up so many possibilities for Chocolatey CLI users!

Watch On-Demand
Chocolatey Coding Livestream

Livestream from
Tuesday, 29 November 2022

Join Josh as he adds the ability to manage Chocolatey GUI config and features with the Chocolatey Ansible Collection.

Watch On-Demand
Introduction into Chocolatey with Veeam

Webinar from
Tuesday, 13 December 2022

Join Gary, Paul, and Maurice as they introduce and demonstrate how to use Chocolatey! Questions will be answered live in an Ask Me Anything format.

Watch On-Demand



Downloads of v 0.6.2:


Last Update:

25 Oct 2016

Package Maintainer(s):

Software Author(s):

  • Mitchell Hashimoto
  • HashiCorp


vault hashicorp


This is not the latest version of Vault available.

  • 1
  • 2
  • 3

0.6.2 | Updated: 25 Oct 2016



Downloads of v 0.6.2:



Software Author(s):

  • Mitchell Hashimoto
  • HashiCorp

Vault 0.6.2

This is not the latest version of Vault available.

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests

Validation Testing Passed

Verification Testing Passed


Scan Testing Successful:

No detections found in any package files

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

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:


Deployment Method:


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

1. Enter Your Internal Repository Url

(this should look similar to

2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

  • 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. Copy Your Script

choco upgrade vault -y --source="'INTERNAL REPO URL'" --version="'0.6.2'" [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="'INTERNAL REPO URL'" --version="'0.6.2'" 

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

Exit $exitCode

- name: Install vault
    name: vault
    version: '0.6.2'
    state: present

See docs at

chocolatey_package 'vault' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '0.6.2'

See docs at

cChocoPackageInstaller vault
    Name     = "vault"
    Version  = "0.6.2"
    Source   = "INTERNAL REPO URL"

Requires cChoco DSC Resource. See docs at

package { 'vault':
  ensure   => '0.6.2',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',

Requires Puppet Chocolatey Provider module. See docs at

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

Package Approved

This package was approved by moderator gep13 on 27 Oct 2016.


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 = '0273c2fc6afec1c8e2b62c610b675088d47d26d3a5dda801f23836baf566fe17'
$checksum64 = '66b71cdc72ebea0dc766af252963004fc4959f3a4bebdd2f5f9d67258967b877'
$url = ''
$url64bit = ''
$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.

Add to Builder Version Downloads Last Updated Status
Vault 1.14.3 1968 Thursday, September 14, 2023 Approved
Vault 1.14.2 1953 Wednesday, August 30, 2023 Approved
Vault 1.14.1 4124 Wednesday, July 26, 2023 Approved
Vault 1.14.0 4660 Wednesday, June 21, 2023 Approved
Vault 1.13.3 1563 Friday, June 9, 2023 Approved
Vault 1.13.2 7318 Thursday, April 27, 2023 Approved
Vault 1.13.1 4218 Thursday, March 30, 2023 Approved
Vault 1.13.0 1512 Tuesday, March 7, 2023 Approved
Vault 1.12.3 2109 Thursday, February 23, 2023 Approved
Vault 1.12.2 5871 Saturday, December 17, 2022 Approved
Vault 1.11.1 18699 Wednesday, July 27, 2022 Approved
Vault 1.11.0 2526 Tuesday, June 21, 2022 Approved
Vault 1.10.4 467 Friday, June 17, 2022 Approved
Vault 1.10.3 3144 Friday, May 13, 2022 Approved
Vault 1.10.2 45 Friday, May 13, 2022 Approved
Vault 1.10.1 1510 Monday, April 25, 2022 Approved
Vault 1.10.0 2288 Friday, March 25, 2022 Approved
Vault 1.9.4 1347 Wednesday, March 9, 2022 Approved
Vault 1.9.3 2293 Monday, January 31, 2022 Approved
Vault 1.9.2 1932 Wednesday, December 22, 2021 Approved
Vault 1.9.1 1080 Tuesday, December 14, 2021 Approved
Vault 1.9.0 1575 Tuesday, November 23, 2021 Approved
Vault 1.8.5 74 Tuesday, November 23, 2021 Approved
Vault 1.8.4 3065 Friday, October 8, 2021 Approved
Vault 1.8.3 668 Friday, October 1, 2021 Approved
Vault 1.8.2 612 Thursday, September 30, 2021 Approved
Vault 1.8.1 142 Thursday, September 30, 2021 Approved
Vault 1.8.0 3303 Thursday, July 29, 2021 Approved
Vault 1.7.3 2483 Thursday, June 17, 2021 Approved
Vault 1.7.2 1937 Friday, May 21, 2021 Approved
Vault 1.7.1 1529 Monday, April 26, 2021 Approved
Vault 1.7.0 1559 Tuesday, April 6, 2021 Approved
Vault 1.6.3 440 Thursday, March 25, 2021 Approved
Vault 1.6.2 3991 Monday, February 1, 2021 Approved
Vault 1.6.1 706 Thursday, January 21, 2021 Approved
Vault 1.5.5 5307 Friday, October 23, 2020 Approved
Vault 1.5.4 21842 Thursday, October 22, 2020 Approved
Vault 1.5.3 576 Thursday, October 22, 2020 Approved
Vault 1.5.2 2300 Wednesday, August 26, 2020 Approved
Vault 1.5.0 1646 Wednesday, July 22, 2020 Approved
Vault 1.4.3 875 Friday, July 3, 2020 Approved
Vault 1.4.1 1728 Monday, May 4, 2020 Approved
Vault 1.4.0 1371 Thursday, April 9, 2020 Approved
Vault 1.3.4 207 Wednesday, April 8, 2020 Approved
Vault 1.3.3 901 Monday, March 9, 2020 Approved
Vault 1.3.2 1469 Friday, January 24, 2020 Approved
Vault 1.3.1 1617 Friday, December 20, 2019 Approved
Vault 1.3.0 484 Wednesday, December 11, 2019 Approved
Vault 1.2.4 1013 Tuesday, November 12, 2019 Approved
Vault 1.2.3 3401 Monday, September 16, 2019 Approved
Vault 1.2.2 2344 Friday, August 16, 2019 Approved
Vault 1.2.1 155 Thursday, August 8, 2019 Approved
Vault 1.2.0 935 Wednesday, July 31, 2019 Approved
Vault 1.1.1 5052 Tuesday, April 16, 2019 Approved
Vault 1.1.0 1007 Tuesday, March 19, 2019 Approved
Vault 1.0.3 681 Friday, March 1, 2019 Approved
Vault 0.10.0 3095 Monday, April 16, 2018 Approved
Vault 0.10.0-rc1 289 Saturday, April 7, 2018 Approved
Vault 0.9.6 462 Saturday, April 7, 2018 Approved
Vault 0.9.5 261 Saturday, April 7, 2018 Approved
Vault 0.9.4 334 Saturday, April 7, 2018 Approved
Vault 0.9.3 281 Saturday, April 7, 2018 Approved
Vault 0.9.2 278 Saturday, April 7, 2018 Approved
Vault 0.9.1 987 Saturday, January 13, 2018 Approved
Vault 0.9.0 343 Saturday, January 13, 2018 Approved
Vault 0.8.3 931 Wednesday, September 20, 2017 Approved
Vault 0.8.2 353 Wednesday, September 20, 2017 Approved
Vault 0.8.1 430 Thursday, August 24, 2017 Approved
Vault 0.8.0 417 Thursday, August 24, 2017 Approved
Vault 0.7.3 554 Thursday, June 8, 2017 Approved
Vault 0.7.2 402 Wednesday, June 7, 2017 Approved
Vault 0.7.1 370 Wednesday, June 7, 2017 Approved
Vault 0.7.0 391 Wednesday, June 7, 2017 Approved
Vault 0.6.5 897 Wednesday, February 8, 2017 Approved
Vault 0.6.4 511 Thursday, December 22, 2016 Approved
Vault 0.6.3 391 Wednesday, December 14, 2016 Approved
Vault 0.6.2 468 Tuesday, October 25, 2016 Approved
Vault 0.6.1 460 Tuesday, August 30, 2016 Approved

0.6.2 (October 5, 2016)


  • Convergent Encryption v2: New keys in transit using convergent mode will use a new nonce derivation mechanism rather than require the user to supply a nonce. While not explicitly increasing security, it minimizes the likelihood that a user will use the mode improperly and impact the security of their keys. Keys in convergent mode that were created in v0.6.1 will continue to work with the same mechanism (user-supplied nonce).
  • etcd HA off by default: Following in the footsteps of dynamodb, the etcd storage backend now requires that ha_enabled be explicitly specified in the configuration file. The backend currently has known broken HA behavior, so this flag discourages use by default without explicitly enabling it. If you are using this functionality, when upgrading, you should set ha_enabled to "true" before starting the new versions of Vault.
  • Default/Max lease/token TTLs are now 32 days: In previous versions of Vault the default was 30 days, but moving it to 32 days allows some operations (e.g. reauthenticating, renewing, etc.) to be performed via a monthly cron job.
  • AppRole Secret ID endpoints changed: Secret ID and Secret ID accessors are no longer part of request URLs. The GET and DELETE operations are now moved to new endpoints (/lookup and /destroy) which consumes the input from the body and not the URL.
  • AppRole requires at least one constraint: previously it was sufficient to turn off all AppRole authentication constraints (secret ID, CIDR block) and use the role ID only. It is now required that at least one additional constraint is enabled. Existing roles are unaffected, but any new roles or updated roles will require this.
  • Reading wrapped responses from cubbyhole/response is deprecated. The sys/wrapping/unwrap endpoint should be used instead as it provides additional security, auditing, and other benefits. The ability to read directly will be removed in a future release.
  • Request Forwarding is now on by default: in 0.6.1 this required toggling on, but is now enabled by default. This can be disabled via the "disable_clustering" parameter in Vault's config, or per-request with the X-Vault-No-Request-Forwarding header.
  • In prior versions a bug caused the bound_iam_role_arn value in the aws-ec2 authentication backend to actually use the instance profile ARN. This has been corrected, but as a result there is a behavior change. To match using the instance profile ARN, a new parameter bound_iam_instance_profile_arn has been added. Existing roles will automatically transfer the value over to the correct parameter, but the next time the role is updated, the new meanings will take effect.


  • Secret ID CIDR Restrictions in AppRole: Secret IDs generated under an approle can now specify a list of CIDR blocks from where the requests to generate secret IDs should originate from. If an approle already has CIDR restrictions specified, the CIDR restrictions on the secret ID should be a subset of those specified on the role [GH-1910]
  • Initial Root Token PGP Encryption: Similar to generate-root, the root token created at initialization time can now be PGP encrypted [GH-1883]
  • Support Chained Intermediate CAs in pki: The pki backend now allows, when a CA cert is being supplied as a signed root or intermediate, a trust chain of arbitrary length. The chain is returned as a parameter at certificate issue/sign time and is retrievable independently as well. [GH-1694]
  • Response Wrapping Enhancements: There are new endpoints to look up response wrapped token parameters; wrap arbitrary values; rotate wrapping tokens; and unwrap with enhanced validation. In addition, list operations can now be response-wrapped. [GH-1927]
  • Transit features: The transit backend now supports generating random bytes and SHA sums; HMACs; and signing and verification functionality using EC keys (P-256 curve)


  • api: Return error when an invalid (as opposed to incorrect) unseal key is submitted, rather than ignoring it [GH-1782]
  • api: Add method to call auth/token/create-orphan endpoint [GH-1834]
  • api: Rekey operation now redirects from standbys to master [GH-1862]
  • audit/file: Sending a SIGHUP to Vault now causes Vault to close and re-open the log file, making it easier to rotate audit logs [GH-1953]
  • auth/aws-ec2: EC2 instances can get authenticated by presenting the identity document and its SHA256 RSA digest [GH-1961]
  • auth/aws-ec2: IAM bound parameters on the aws-ec2 backend will perform a prefix match instead of exact match [GH-1943]
  • auth/aws-ec2: Added a new constraint bound_iam_instance_profile_arn to refer to IAM instance profile ARN and fixed the earlier bound_iam_role_arn to refer to IAM role ARN instead of the instance profile ARN [GH-1913]
  • auth/aws-ec2: Backend generates the nonce by default and clients can explicitly disable reauthentication by setting empty nonce [GH-1889]
  • auth/token: Added warnings if tokens and accessors are used in URLs [GH-1806]
  • command/format: The format flag on select CLI commands takes yml as an alias for yaml [GH-1899]
  • core: Allow the size of the read cache to be set via the config file, and change the default value to 1MB (from 32KB) [GH-1784]
  • core: Allow single and two-character path parameters for most places [GH-1811]
  • core: Allow list operations to be response-wrapped [GH-1814]
  • core: Provide better protection against timing attacks in Shamir code [GH-1877]
  • core: Unmounting/disabling backends no longer returns an error if the mount didn't exist. This is line with elsewhere in Vault's API where DELETE is an idempotent operation. [GH-1903]
  • credential/approle: At least one constraint is required to be enabled while creating and updating a role [GH-1882]
  • secret/cassandra: Added consistency level for use with roles [GH-1931]
  • secret/mysql: SQL for revoking user can be configured on the role [GH-1914]
  • secret/transit: Use HKDF (RFC 5869) as the key derivation function for new keys [GH-1812]
  • secret/transit: Empty plaintext values are now allowed [GH-1874]


  • audit: Fix panic being caused by some values logging as underlying Go types instead of formatted strings [GH-1912]
  • auth/approle: Fixed panic on deleting approle that doesn't exist [GH-1920]
  • auth/approle: Not letting secret IDs and secret ID accessors to get logged in plaintext in audit logs [GH-1947]
  • auth/aws-ec2: Allow authentication if the underlying host is in a bad state but the instance is running [GH-1884]
  • auth/token: Fixed metadata getting missed out from token lookup response by gracefully handling token entry upgrade [GH-1924]
  • cli: Don't error on newline in token file [GH-1774]
  • core: Pass back content-type header for forwarded requests [GH-1791]
  • core: Fix panic if the same key was given twice to generate-root [GH-1827]
  • core: Fix potential deadlock on unmount/remount [GH-1793]
  • physical/file: Remove empty directories from the file storage backend [GH-1821]
  • physical/zookeeper: Remove empty directories from the zookeeper storage backend and add a fix to the file storage backend's logic [GH-1964]
  • secret/aws: Added update operation to aws/sts path to consider ttl parameter [39b75c6]
  • secret/aws: Mark STS secrets as non-renewable [GH-1804]
  • secret/cassandra: Properly store session for re-use [GH-1802]
  • secret/ssh: Fix panic when revoking SSH dynamic keys [GH-1781]

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