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.0:
07 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 07 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 = '50541390d4de9e8906ad60eab2f527ec18660a5e91c3845f7d15e83416706730' $checksum64 = 'c4d4556665709e0e5b11000413f046e23b365eb97eed9ee04f1a5c2598649356' $url = 'https://releases.hashicorp.com/vault/0.7.0/vault_0.7.0_windows_386.zip' $url64bit = 'https://releases.hashicorp.com/vault/0.7.0/vault_0.7.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.7.0.nupkg (f0cd924dcda1) - ## / 59
- vault.exe (ee53319cfb74) - ## / 62
- vault.exe (51385851ef49) - ## / 61
- vault_0.7.0_windows_amd64.zip (c4d455666570) - ## / 58
- vault_0.7.0_windows_386.zip (50541390d4de) - ## / 59
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.7.0 (Early Access; final release March 21th, 2017)
- Common name not being validated when
exclude_cn_from_sansoption used in
pkibackend: When using a role in the
pkibackend that specified the
exclude_cn_from_sansoption, the common name would not then be properly validated against the role's constraints. This has been fixed. We recommend any users of this feature to upgrade to 0.7 as soon as feasible.
- List Operations Always Use Trailing Slash: Any list operation, whether via the
LISTHTTP verb, will now internally canonicalize the path to have a trailing slash. This makes policy writing more predictable, as it means clients will no longer work or fail based on which client they're using or which HTTP verb they're using. However, it also means that policies allowing
listcapability must be carefully checked to ensure that they contain a trailing slash; some policies may need to be split into multiple stanzas to accommodate.
- PKI Defaults to Unleased Certificates: When issuing certificates from the PKI backend, by default, no leases will be issued. If you want to manually revoke a certificate, its serial number can be used with the
pki/revokeendpoint. Issuing leases is still possible by enabling the
generate_leasetoggle in PKI role entries (this will default to
truefor upgrades, to keep existing behavior), which will allow using lease IDs to revoke certificates. For installations issuing large numbers of certificates (tens to hundreds of thousands, or millions), this will significantly improve Vault startup time since leases associated with these certificates will not have to be loaded; however note that it also means that revocation of a token used to issue certificates will no longer add these certificates to a CRL. If this behavior is desired or needed, consider keeping leases enabled and ensuring lifetimes are reasonable, and issue long-lived certificates via a different role with leases disabled.
- Replication (Enterprise): Vault Enterprise now has support for creating a multi-datacenter replication set between clusters. The current replication offering is based on an asynchronous primary/secondary (1:N) model that replicates static data while keeping dynamic data (leases, tokens) cluster-local, focusing on horizontal scaling for high-throughput and high-fanout deployments.
- Response Wrapping & Replication in the Vault Enterprise UI: Vault Enterprise UI now supports looking up and rotating response wrapping tokens, as well as creating tokens with arbitrary values inside. It also now supports replication functionality, enabling the configuration of a replication set in the UI.
- Expanded Access Control Policies: Access control policies can now specify allowed and denied parameters -- and, optionally, their values -- to control what a client can and cannot submit during an API call. Policies can also specify minimum/maximum response wrapping TTLs to both enforce the use of response wrapping and control the duration of resultant wrapping tokens. See the policies concepts page for more information.
- SSH Backend As Certificate Authority: The SSH backend can now be configured to sign host and user certificates. Each mount of the backend acts as an independent signing authority. The CA key pair can be configured for each mount and the public key is accessible via an unauthenticated API call; additionally, the backend can generate a public/private key pair for you. We recommend using separate mounts for signing host and user certificates.
- api/request: Passing username and password information in API request [GH-2469]
- audit: Logging the token's use count with authentication response and logging the remaining uses of the client token with request [GH-2437]
- auth/approle: Support for restricting the number of uses on the tokens issued [GH-2435]
- auth/aws-ec2: AWS EC2 auth backend now supports constraints for VPC ID, Subnet ID and Region [GH-2407]
- auth/ldap: Use the value of the
USERenv vars for the username if not explicitly set on the command line when authenticating [GH-2154]
- audit: Support adding a configurable prefix (such as
@cee) before each line [GH-2359]
- core: Canonicalize list operations to use a trailing slash [GH-2390]
- core: Add option to disable caching on a per-mount level [GH-2455]
- core: Add ability to require valid client certs in listener config [GH-2457]
- physical/dynamodb: Implement a session timeout to avoid having to use
recovery mode in the case of an unclean shutdown, which makes HA much safer [GH-2141]
- secret/pki: O (Organization) values can now be set to role-defined values for issued/signed certificates [GH-2369]
- secret/pki: Certificates issued/signed from PKI backend do not generate leases by default [GH-2403]
- secret/pki: When using DER format, still return the private key type [GH-2405]
- secret/pki: Add an intermediate to the CA chain even if it lacks an authority key ID [GH-2465]
- secret/pki: Add role option to use CSR SANs [GH-2489]
- secret/ssh: SSH backend as CA to sign user and host certificates [GH-2208]
- secret/ssh: Support reading of SSH CA public key from
config/caendpoint and also return it when CA key pair is generated [GH-2483]
- audit: When auditing headers use case-insensitive comparisons [GH-2362]
- auth/aws-ec2: Return role period in seconds and not nanoseconds [GH-2374]
- auth/okta: Fix panic if user had no local groups and/or policies set [GH-2367]
- command/server: Fix parsing of redirect address when port is not mentioned [GH-2354]
- physical/postgresql: Fix listing returning incorrect results if there were multiple levels of children [GH-2393]
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.