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.7.3:
08 Jun 2017
- 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 as a trusted package on 08 Jun 2017.
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 = '6a39b91e72fa8743b76b998ecdf9432acf6f75b98e9975c3f5cad49d5597146d' $checksum64 = '44b9f7b9c87b2c5df71a2462518299bfb165b9c3fd839d2ff817acce9af3a9e4' $url = 'https://releases.hashicorp.com/vault/0.7.3/vault_0.7.3_windows_386.zip' $url64bit = 'https://releases.hashicorp.com/vault/0.7.3/vault_0.7.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.7.3.nupkg (0ae0784a39d5) - ## / 59
- vault.exe (8e03e66e313d) - ## / 61
- vault.exe (403caac94486) - ## / 62
- vault_0.7.3_windows_amd64.zip (44b9f7b9c87b) - ## / 60
- vault_0.7.3_windows_386.zip (6a39b91e72fa) - ## / 60
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||1693||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.7.3 (June 7th, 2017)
- Cert auth backend now checks validity of individual certificates: In previous versions of Vault, validity (e.g. expiration) of individual leaf certificates added for authentication was not checked. This was done to make it easier for administrators to control lifecycles of individual certificates added to the backend, e.g. the authentication material being checked was access to that specific certificate's private key rather than all private keys signed by a CA. However, this behavior is often unexpected and as a result can lead to insecure deployments, so we are now validating these certificates as well.
- App-ID path salting was skipped in 0.7.1/0.7.2: A regression in 0.7.1/0.7.2 caused the HMACing of any App-ID information stored in paths (including actual app-IDs and user-IDs) to be unsalted and written as-is from the API. In 0.7.3 any such paths will be automatically changed to salted versions on access (e.g. login or read); however, if you created new app-IDs or user-IDs in 0.7.1/0.7.2, you may want to consider whether any users with access to Vault's underlying data store may have intercepted these values, and revoke/roll them.
- Step-Down is Forwarded: When a step-down is issued against a non-active node in an HA cluster, it will now forward the request to the active node.
- ed25519 Signing/Verification in Transit with Key Derivation: The
transitbackend now supports generating ed25519 keys for signing and verification functionality. These keys support derivation, allowing you to modify the actual encryption key used by supplying a
- Key Version Specification for Encryption in Transit: You can now specify the version of a key you use to wish to generate a signature, ciphertext, or HMAC. This can be controlled by the
min_encryption_versionkey configuration property.
- Replication Primary Discovery (Enterprise): Replication primaries will now advertise the addresses of their local HA cluster members to replication secondaries. This helps recovery if the primary active node goes down and neither service discovery nor load balancers are in use to steer clients.
- api/health: Add Sys().Health() [GH-2805]
- audit: Add auth information to requests that error out [GH-2754]
- command/auth: Add
-no-storeoption that prevents the auth command from storing the returned token into the configured token helper [GH-2809]
- core/forwarding: Request forwarding now heartbeats to prevent unused connections from being terminated by firewalls or proxies
- plugins/databases: Add MongoDB as an internal database plugin [GH-2698]
- storage/dynamodb: Add a method for checking the existence of children, speeding up deletion operations in the DynamoDB storage backend [GH-2722]
- storage/mysql: Add max_parallel parameter to MySQL backend [GH-2760]
- secret/databases: Support listing connections [GH-2823]
- secret/databases: Support custom renewal statements in Postgres database plugin [GH-2788]
- secret/databases: Use the role name as part of generated credentials [GH-2812]
- ui (Enterprise): Transit key and secret browsing UI handle large lists better
- ui (Enterprise): root tokens are no longer persisted
- ui (Enterprise): support for mounting Database and TOTP secret backends
- auth/app-id: Fix regression causing loading of salts to be skipped
- auth/aws: Improve EC2 describe instances performance [GH-2766]
- auth/aws: Fix lookup of some instance profile ARNs [GH-2802]
- auth/aws: Resolve ARNs to internal AWS IDs which makes lookup at various points (e.g. renewal time) more robust [GH-2814]
- auth/aws: Properly honor configured period when using IAM authentication [GH-2825]
- auth/aws: Check that a bound IAM principal is not empty (in the current state of the role) before requiring it match the previously authenticated client [GH-2781]
- auth/cert: Fix panic on renewal [GH-2749]
- auth/cert: Certificate verification for non-CA certs [GH-2761]
- core/acl: Prevent race condition when compiling ACLs in some scenarios [GH-2826]
- secret/database: Increase wrapping token TTL; in a loaded scenario it could be too short
- secret/generic: Allow integers to be set as the value of
ttlfield as the documentation claims is supported [GH-2699]
- secret/ssh: Added host key callback to ssh client config [GH-2752]
- storage/s3: Avoid a panic when some bad data is returned [GH-2785]
- storage/dynamodb: Fix list functions working improperly on Windows [GH-2789]
- storage/file: Don't leak file descriptors in some error cases
- storage/swift: Fix pre-v3 project/tenant name reading [GH-2803]
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.