Welcome to the Chocolatey Community Package Repository! The packages found in this section of the site are provided, maintained, and moderated by the community.
Every version of each package undergoes a rigorous moderation process before it goes live that typically includes:
- Security, consistency, and quality checking
- Installation testing
- Virus checking through VirusTotal
- Human moderators who give final review and sign off
If you are an organization using Chocolatey, we want your experience to be fully reliable. Due to the nature of this publicly offered repository, reliability cannot be guaranteed. Packages offered here are subject to distribution rights, which means they may need to reach out further to the internet to the official locations to download files at runtime.
Fortunately, distribution rights do not apply for internal use. With any edition of Chocolatey (including the free open source edition), you can host your own packages and cache or internalize existing community packages.
Your use of the packages on this site means you understand they are not supported or guaranteed in any way. Learn more...
Downloads of v 0.6.3:
14 Dec 2016
- Mitchell Hashimoto
This is not the latest version of Vault available.
To edit the metadata for a package, please upload an updated version of the package.
Chocolatey's Community Package Repository currently does not allow updating package metadata on the website. This helps ensure that the package itself (and the source used to build the package) remains the one true source of package metadata.
This does require that you increment the package version.
This is not the latest version of Vault available.
All Checks are Passing
2 Passing Test
Validation Testing Passed
Verification Testing PassedDetails
This package was approved by moderator gep13 on 19 Dec 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 = '487e98ff32930f86083286fcd91cad8cb31f6639974eeb8f6c443eb40e5fde1b' $checksum64 = '56cdfbfee5526def65d29c142dd76eae1451addc11ff3d980a07ccacddb6e142' $url = 'https://releases.hashicorp.com/vault/0.6.3/vault_0.6.3_windows_386.zip' $url64bit = 'https://releases.hashicorp.com/vault/0.6.3/vault_0.6.3_windows_amd64.zip' $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.
- vault.0.6.3.nupkg (8e035e3e300f) - ## / 54
- vault.exe (27b0a4503ebc) - ## / 57
- vault.exe (547d5c643654) - ## / 57
- vault_0.6.3_windows_amd64.zip (56cdfbfee552) - ## / 57
- vault_0.6.3_windows_386.zip (487e98ff3293) - ## / 57
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.
|Vault 1.6.2||1698||Monday, February 1, 2021||Approved|
|Vault 1.6.1||614||Thursday, January 21, 2021||Approved|
|Vault 1.5.5||3174||Friday, October 23, 2020||Approved|
|Vault 1.5.4||1510||Thursday, October 22, 2020||Approved|
|Vault 1.5.3||180||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||1627||Monday, May 4, 2020||Approved|
|Vault 1.4.0||1269||Thursday, April 9, 2020||Approved|
|Vault 1.3.4||134||Wednesday, April 8, 2020||Approved|
|Vault 1.3.3||795||Monday, March 9, 2020||Approved|
|Vault 1.3.2||1357||Friday, January 24, 2020||Approved|
|Vault 1.3.1||1492||Friday, December 20, 2019||Approved|
|Vault 1.3.0||393||Wednesday, December 11, 2019||Approved|
|Vault 1.2.4||934||Tuesday, November 12, 2019||Approved|
|Vault 1.2.3||3315||Monday, September 16, 2019||Approved|
|Vault 1.2.2||2258||Friday, August 16, 2019||Approved|
|Vault 1.2.1||72||Thursday, August 8, 2019||Approved|
|Vault 1.2.0||855||Wednesday, July 31, 2019||Approved|
|Vault 1.1.1||4934||Tuesday, April 16, 2019||Approved|
|Vault 1.1.0||894||Tuesday, March 19, 2019||Approved|
|Vault 1.0.3||588||Friday, March 1, 2019||Approved|
|Vault 0.10.0||3003||Monday, April 16, 2018||Approved|
|Vault 0.10.0-rc1||206||Saturday, April 7, 2018||Approved|
|Vault 0.9.6||376||Saturday, April 7, 2018||Approved|
|Vault 0.9.5||189||Saturday, April 7, 2018||Approved|
|Vault 0.9.4||240||Saturday, April 7, 2018||Approved|
|Vault 0.9.3||188||Saturday, April 7, 2018||Approved|
|Vault 0.9.2||192||Saturday, April 7, 2018||Approved|
|Vault 0.9.1||894||Saturday, January 13, 2018||Approved|
|Vault 0.9.0||238||Saturday, January 13, 2018||Approved|
|Vault 0.8.3||832||Wednesday, September 20, 2017||Approved|
|Vault 0.8.2||269||Wednesday, September 20, 2017||Approved|
|Vault 0.8.1||349||Thursday, August 24, 2017||Approved|
|Vault 0.8.0||317||Thursday, August 24, 2017||Approved|
|Vault 0.7.3||467||Thursday, June 8, 2017||Approved|
|Vault 0.7.2||316||Wednesday, June 7, 2017||Approved|
|Vault 0.7.1||280||Wednesday, June 7, 2017||Approved|
|Vault 0.7.0||295||Wednesday, June 7, 2017||Approved|
|Vault 0.6.5||802||Wednesday, February 8, 2017||Approved|
|Vault 0.6.4||416||Thursday, December 22, 2016||Approved|
|Vault 0.6.3||312||Wednesday, December 14, 2016||Approved|
|Vault 0.6.2||379||Tuesday, October 25, 2016||Approved|
|Vault 0.6.1||371||Tuesday, August 30, 2016||Approved|
0.6.3 (December 6, 2016)
- Request size limitation: A maximum request size of 32MB is imposed to prevent a denial of service attack with arbitrarily large requests [GH-2108]
- LDAP denies passwordless binds by default: In new LDAP mounts, or when existing LDAP mounts are rewritten, passwordless binds will be denied by default. The new
deny_null_bindparameter can be set to
falseto allow these. [GH-2103]
- Any audit backend activated satisfies conditions: Previously, when a new Vault node was taking over service in an HA cluster, all audit backends were required to be loaded successfully to take over active duty. This behavior now matches the behavior of the audit logging system itself: at least one audit backend must successfully be loaded. The server log contains an error when this occurs. This helps keep a Vault HA cluster working when there is a misconfiguration on a standby node. [GH-2083]
- Google Cloud Storage Physical Backend: You can now use GCS for storing Vault data [GH-2099]
- auth/github: Policies can now be assigned to users as well as to teams [GH-2079]
- cli: Set the number of retries on 500 down to 0 by default (no retrying). It can be very confusing to users when there is a pause while the retries happen if they haven't explicitly set it. With request forwarding the need for this is lessened anyways. [GH-2093]
- core: Response wrapping is now allowed to be specified by backend responses (requires backends gaining support) [GH-2088]
- physical/consul: When announcing service, use the scheme of the Vault server rather than the Consul client [GH-2146]
- secret/consul: Added listing functionality to roles [GH-2065]
- secret/postgresql: Added
revocation_sqlparameter on the role endpoint to enable customization of user revocation SQL statements [GH-2033]
- secret/transit: Add listing of keys [GH-1987]
- api/unwrap, command/unwrap: Increase compatibility of
unwrapcommand with Vault 0.6.1 and older [GH-2014]
- api/unwrap, command/unwrap: Fix error when no client token exists [GH-2077]
- auth/approle: Creating the index for the role_id properly [GH-2004]
- auth/aws-ec2: Handle the case of multiple upgrade attempts when setting the instance-profile ARN [GH-2035]
- auth/ldap: Avoid leaking connections on login [GH-2130]
- command/path-help: Use the actual error generated by Vault rather than always using 500 when there is a path help error [GH-2153]
- command/ssh: Use temporary file for identity and ensure its deletion before the command returns [GH-2016]
- cli: Fix error printing values with
-fieldif the values contained formatting directives [GH-2109]
- command/server: Don't say mlock is supported on OSX when it isn't. [GH-2120]
- core: Fix bug where a failure to come up as active node (e.g. if an audit backend failed) could lead to deadlock [GH-2083]
- physical/mysql: Fix potential crash during setup due to a query failure [GH-2105]
- secret/consul: Fix panic on user error [GH-2145]
For more information on previous releases, check out the changelog on GitHub.
This package has no dependencies.
- 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.