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.9.1:
13 Jan 2018
- 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
Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...
This package was approved as a trusted package on 04 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 = 'fecac943606c9549d026ce6aa6b98baf659b5f78f284e8ddcef81bb21199b24b' $checksum64 = '5181a518ab1a8516ec1b155128282763a7794baa92b4c8cf502e5effc933383e' $url = 'https://releases.hashicorp.com/vault/0.9.1/vault_0.9.1_windows_386.zip' $url64bit = 'https://releases.hashicorp.com/vault/0.9.1/vault_0.9.1_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.9.1.nupkg (3bec4a099ee3) - ## / 61
- vault_0.9.1_windows_amd64.zip (5181a518ab1a) - ## / 61
- vault_0.9.1_windows_386.zip (fecac943606c) - ## / 62
- vault.exe (becccb730130) - ## / 66
- vault.exe (b01507d8f955) - ## / 67
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||1539||Monday, February 1, 2021||Approved|
|Vault 1.6.1||613||Thursday, January 21, 2021||Approved|
|Vault 1.5.5||3174||Friday, October 23, 2020||Approved|
|Vault 1.5.4||1465||Thursday, October 22, 2020||Approved|
|Vault 1.5.3||176||Thursday, October 22, 2020||Approved|
|Vault 1.5.2||2209||Wednesday, August 26, 2020||Approved|
|Vault 1.5.0||1489||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||1267||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||1353||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||71||Thursday, August 8, 2019||Approved|
|Vault 1.2.0||852||Wednesday, July 31, 2019||Approved|
|Vault 1.1.1||4934||Tuesday, April 16, 2019||Approved|
|Vault 1.1.0||893||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||188||Saturday, April 7, 2018||Approved|
|Vault 0.9.4||239||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||893||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||268||Wednesday, September 20, 2017||Approved|
|Vault 0.8.1||349||Thursday, August 24, 2017||Approved|
|Vault 0.8.0||314||Thursday, August 24, 2017||Approved|
|Vault 0.7.3||467||Thursday, June 8, 2017||Approved|
|Vault 0.7.2||315||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||415||Thursday, December 22, 2016||Approved|
|Vault 0.6.3||311||Wednesday, December 14, 2016||Approved|
|Vault 0.6.2||379||Tuesday, October 25, 2016||Approved|
|Vault 0.6.1||367||Tuesday, August 30, 2016||Approved|
0.9.1 (December 21st, 2017)
- AppRole Case Sensitivity: In prior versions of Vault,
listoperations against AppRole roles would require preserving case in the role name, even though most other operations within AppRole are case-insensitive with respect to the role name. This has been fixed; existing roles will behave as they have in the past, but new roles will act case-insensitively in these cases.
- Token Auth Backend Roles parameter types: For
disallowed_policiesin role definitions in the token auth backend, input can now be a comma-separated string or an array of strings. Reading a role will now return arrays for these parameters.
- Transit key exporting: You can now mark a key in the
exportableat any time, rather than just at creation time; however, once this value is set, it still cannot be unset.
- PKI Secret Backend Roles parameter types: For
key_usagein role definitions in the PKI secret backend, input can now be a comma-separated string or an array of strings. Reading a role will now return arrays for these parameters.
- SSH Dynamic Keys Method Defaults to 2048-bit Keys: When using the dynamic key method in the SSH backend, the default is now to use 2048-bit keys if no specific key bit size is specified.
- Consul Secret Backend lease handling: The
consulsecret backend can now accept both strings and integer numbers of seconds for its lease value. The value returned on a role read will be an integer number of seconds instead of a human-friendly string.
- Unprintable characters not allowed in API paths: Unprintable characters are no longer allowed in names in the API (paths and path parameters), with an extra restriction on whitespace characters. Allowed characters are those that are considered printable by Unicode plus spaces.
- Transit Backup/Restore: The
transitbackend now supports a backup operation that can export a given key, including all key versions and configuration, as well as a restore operation allowing import into another Vault.
- gRPC Database Plugins: Database plugins now use gRPC for transport, allowing them to be written in other languages.
- Nomad Secret Backend: Nomad ACL tokens can now be generated and revoked using Vault.
- TLS Cert Auth Backend Improvements: The
certauth backend can now match against custom certificate extensions via exact or glob matching, and additionally supports max_ttl and periodic token toggles.
- auth/cert: Support custom certificate constraints [GH-3634]
- auth/cert: Support setting
- audit/file: Setting a file mode of
0000will now disable Vault from automatically
chmoding the log file [GH-3649]
- auth/github: The legacy MFA system can now be used with the GitHub auth backend [GH-3696]
- auth/okta: The legacy MFA system can now be used with the Okta auth backend [GH-3653]
disallowed_policiescan now be specified as a comma-separated string or an array of strings [GH-3641]
- command/server: The log level can now be specified with
- core: Period values from auth backends will now be checked and applied to the TTL value directly by core on login and renewal requests [GH-3677]
- database/mongodb: Add optional
write_concernparameter, which can be set during database configuration. This establishes a session-wide write concern for the lifecycle of the mount [GH-3646]
- http: Request path containing non-printable characters will return 400 - Bad Request [GH-3697]
- mfa/okta: Filter a given email address as a login filter, allowing operation when login email and account email are different
- plugins: Make Vault more resilient when unsealing when plugins are unavailable [GH-3686]
key_usagecan now be specified as a comma-separated string or an array of strings [GH-3642]
- secret/ssh: Allow 4096-bit keys to be used in dynamic key method [GH-3593]
- secret/consul: The Consul secret backend now uses the value of
leaseset on the role, if set, when renewing a secret. [GH-3796]
- storage/mysql: Don't attempt database creation if it exists, which can help under certain permissions constraints [GH-3716]
- api/status (enterprise): Fix status reporting when using an auto seal
- auth/approle: Fix case-sensitive/insensitive comparison issue [GH-3665]
- auth/cert: Return
allowed_nameson role read [GH-3654]
- auth/ldap: Fix incorrect control information being sent [GH-3402] [GH-3496] [GH-3625] [GH-3656]
- core: Fix seal status reporting when using an autoseal
- core: Add creation path to wrap info for a control group token
- core: Fix potential panic that could occur using plugins when a node transitioned from active to standby [GH-3638]
- core: Fix memory ballooning when a connection would connect to the cluster port and then go away -- redux! [GH-3680]
- core: Replace recursive token revocation logic with depth-first logic, which can avoid hitting stack depth limits in extreme cases [GH-2348]
- core: When doing a read on configured audited-headers, properly handle case insensitivity [GH-3701]
- core/pkcs11 (enterprise): Fix panic when PKCS#11 library is not readable
- database/mysql: Allow the creation statement to use commands that are not yet supported by the prepare statement protocol [GH-3619]
- plugin/auth-gcp: Fix IAM roles when using
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.