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.0:
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
This package was approved as a trusted package on 13 Jan 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 = 'fd5bd46eb10951cf3d35cbff4d00e6c4e1110311d6e86968d997d4bf294db8b9' $checksum64 = '118fa03cbdc9629da151d42f8b023751ac7cdf94b072f584f1513f1748bdf8e8' $url = 'https://releases.hashicorp.com/vault/0.9.0/vault_0.9.0_windows_386.zip' $url64bit = 'https://releases.hashicorp.com/vault/0.9.0/vault_0.9.0_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.0.nupkg (53bb568dfddf) - ## / 61
- vault_0.9.0_windows_amd64.zip (118fa03cbdc9) - ## / 62
- vault_0.9.0_windows_386.zip (fd5bd46eb109) - ## / 61
- vault.exe (02b1243eb83f) - ## / 67
- vault.exe (1adce5241e70) - ## / 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.0 (November 14th, 2017)
- API HTTP client behavior: When calling
NewClientthe API no longer modifies the provided client/transport. In particular this means it will no longer enable redirection limiting and HTTP/2 support on custom clients. It is suggested that if you want to make changes to an HTTP client that you use one created by
DefaultConfigas a starting point.
- AWS EC2 client nonce behavior: The client nonce generated by the backend that gets returned along with the authentication response will be audited in plaintext. If this is undesired, the clients can choose to supply a custom nonce to the login endpoint. The custom nonce set by the client will from now on, not be returned back with the authentication response, and hence not audit logged.
- AWS Auth role options: The API will now error when trying to create or update a role with the mutually-exclusive options
- SSH CA role read changes: When reading back a role from the
sshbackend, the TTL/max TTL values will now be an integer number of seconds rather than a string. This better matches the API elsewhere in Vault.
- SSH role list changes: When listing roles from the
sshbackend via the API, the response data will additionally return a
key_infomap that will contain a map of each key with a corresponding object containing the
- More granularity in audit logs: Audit request and response entires are still in RFC3339 format but now have a granularity of nanoseconds.
- RSA Support for Transit Backend: Transit backend can now generate RSA keys which can be used for encryption and signing. [GH-3489]
- Identity System: Now in open source and with significant enhancements, Identity is an integrated system for understanding users across tokens and enabling easier management of users directly and via groups.
- External Groups in Identity: Vault can now automatically assign users and systems to groups in Identity based on their membership in external groups.
- Seal Wrap / FIPS 140-2 Compatibility (Enterprise): Vault can now take advantage of FIPS 140-2-certified HSMs to ensure that Critical Security Parameters are protected in a compliant fashion. Vault's implementation has received a statement of compliance from Leidos.
- Control Groups (Enterprise): Require multiple members of an Identity group to authorize a requested action before it is allowed to run.
- Cloud Auto-Unseal (Enterprise): Automatically unseal Vault using AWS KMS and GCP CKMS.
- Sentinel Integration (Enterprise): Take advantage of HashiCorp Sentinel to create extremely flexible access control policies -- even on unauthenticated endpoints.
- Barrier Rekey Support for Auto-Unseal (Enterprise): When using auto-unsealing functionality, the
rekeyoperation is now supported; it uses recovery keys to authorize the master key rekey.
- Operation Token for Disaster Recovery Actions (Enterprise): When using Disaster Recovery replication, a token can be created that can be used to authorize actions such as promotion and updating primary information, rather than using recovery keys.
- Trigger Auto-Unseal with Recovery Keys (Enterprise): When using auto-unsealing, a request to unseal Vault can be triggered by a threshold of recovery keys, rather than requiring the Vault process to be restarted.
- UI Redesign (Enterprise): All new experience for the Vault Enterprise UI. The look and feel has been completely redesigned to give users a better experience and make managing secrets fast and easy.
- UI: SSH Secret Backend (Enterprise): Configure an SSH secret backend, create and browse roles. And use them to sign keys or generate one time passwords.
- UI: AWS Secret Backend (Enterprise): You can now configure the AWS backend via the Vault Enterprise UI. In addition you can create roles, browse the roles and Generate IAM Credentials from them in the UI.
- api: Add ability to set custom headers on each call [GH-3394]
- command/server: Add config option to disable requesting client certificates [GH-3373]
- core: Disallow mounting underneath an existing path, not just over [GH-2919]
- physical/file: Use
700as permissions when creating directories. The files themselves were
600and are all encrypted, but this doesn't hurt.
- secret/aws: Add ability to use custom IAM/STS endpoints [GH-3416]
- secret/cassandra: Work around Cassandra ignoring consistency levels for a user listing query [GH-3469]
- secret/pki: Private keys can now be marshalled as PKCS#8 [GH-3518]
- secret/pki: Allow entering URLs for
pkias both comma-separated strings and JSON arrays [GH-3409]
- secret/ssh: Role TTL/max TTL can now be specified as either a string or an integer [GH-3507]
- secret/transit: Sign and verify operations now support a
nonehash algorithm to allow signing/verifying pre-hashed data [GH-3448]
- secret/database: Add the ability to glob allowed roles in the Database Backend [GH-3387]
- ui (enterprise): Support for RSA keys in the transit backend
- ui (enterprise): Support for DR Operation Token generation, promoting, and updating primary on DR Secondary clusters
- api: Fix panic when setting a custom HTTP client but with a nil transport [GH-3435] [GH-3437]
- api: Fix authing to the
certbackend when the CA for the client cert is not known to the server's listener [GH-2946]
- auth/approle: Create role ID index during read if a role is missing one [GH-3561]
- auth/aws: Don't allow mutually exclusive options [GH-3291]
- auth/radius: Fix logging in in some situations [GH-3461]
- core: Fix memleak when a connection would connect to the cluster port and then go away [GH-3513]
- core: Fix panic if a single-use token is used to step-down or seal [GH-3497]
- core: Set rather than add headers to prevent some duplicated headers in responses when requests were forwarded to the active node [GH-3485]
- physical/etcd3: Fix some listing issues due to how etcd3 does prefix matching [GH-3406]
- physical/etcd3: Fix case where standbys can lose their etcd client lease [GH-3031]
- physical/file: Fix listing when underscores are the first component of a path [GH-3476]
- plugins: Allow response errors to be returned from backend plugins [GH-3412]
- secret/transit: Fix panic if the length of the input ciphertext was less than the expected nonce length [GH-3521]
- ui (enterprise): Reinstate support for generic secret backends - this was erroneously removed in a previous release
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.