Downloads:
266,584
Downloads of v 1.6.2:
4,024
Last Update:
01 Feb 2021
Package Maintainer(s):
Software Author(s):
- Mitchell Hashimoto
- HashiCorp
Tags:
vault hashicorp- Software Specific:
- Software Site
- Software Source
- Software License
- Software Docs
- Software Issues
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Vault
This is not the latest version of Vault available.
- 1
- 2
- 3
1.6.2 | Updated: 01 Feb 2021
- Software Specific:
- Software Site
- Software Source
- Software License
- Software Docs
- Software Issues
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
266,584
Downloads of v 1.6.2:
4,024
Maintainer(s):
Software Author(s):
- Mitchell Hashimoto
- HashiCorp
Vault 1.6.2
This is not the latest version of Vault available.
Legal Disclaimer: Neither this package nor Chocolatey Software, Inc. are affiliated with or endorsed by Mitchell Hashimoto, HashiCorp. The inclusion of Mitchell Hashimoto, HashiCorp trademark(s), if any, upon this webpage is solely to identify Mitchell Hashimoto, HashiCorp goods or services and not for commercial purposes.
- 1
- 2
- 3
All Checks are Passing
3 Passing Tests
Deployment Method: Individual Install, Upgrade, & Uninstall
To install Vault, run the following command from the command line or from PowerShell:
To upgrade Vault, run the following command from the command line or from PowerShell:
To uninstall Vault, run the following command from the command line or from PowerShell:
Deployment Method:
This applies to both open source and commercial editions of Chocolatey.
1. Enter Your Internal Repository Url
(this should look similar to https://community.chocolatey.org/api/v2/)
2. Setup Your Environment
1. Ensure you are set for organizational deployment
Please see the organizational deployment guide
2. Get the package into your environment
Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)-
Open Source or Commercial:
- Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2/. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
- You can also just download the package and push it to a repository Download
-
Open Source
-
Download the package:
Download - Follow manual internalization instructions
-
-
Package Internalizer (C4B)
-
Run: (additional options)
choco download vault --internalize --version=1.6.2 --source=https://community.chocolatey.org/api/v2/
-
For package and dependencies run:
choco push --source="'INTERNAL REPO URL'"
- Automate package internalization
-
Run: (additional options)
3. Copy Your Script
choco upgrade vault -y --source="'INTERNAL REPO URL'" --version="'1.6.2'" [other options]
See options you can pass to upgrade.
See best practices for scripting.
Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.
If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:
choco upgrade vault -y --source="'INTERNAL REPO URL'" --version="'1.6.2'"
$exitCode = $LASTEXITCODE
Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
Exit 0
}
Exit $exitCode
- name: Install vault
win_chocolatey:
name: vault
version: '1.6.2'
source: INTERNAL REPO URL
state: present
See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
chocolatey_package 'vault' do
action :install
source 'INTERNAL REPO URL'
version '1.6.2'
end
See docs at https://docs.chef.io/resource_chocolatey_package.html.
cChocoPackageInstaller vault
{
Name = "vault"
Version = "1.6.2"
Source = "INTERNAL REPO URL"
}
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
package { 'vault':
ensure => '1.6.2',
provider => 'chocolatey',
source => 'INTERNAL REPO URL',
}
Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.
4. If applicable - Chocolatey configuration/installation
See infrastructure management matrix for Chocolatey configuration elements and examples.
Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...
This package was approved as a trusted package on 01 Feb 2021.
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.
Log in or click on link to see number of positives.
- vault.1.6.2.nupkg (382f0f817d3d) - ## / 63
- vault_1.6.2_windows_amd64.zip (0cf6cf125b54) - ## / 57
- vault_1.6.2_windows_386.zip (4dfa12f1a36d) - ## / 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.
Add to Builder | Version | Downloads | Last Updated | Status |
---|---|---|---|---|
Vault 1.18.2 | 1486 | Friday, November 22, 2024 | Approved | |
Vault 1.18.1 | 3638 | Thursday, October 31, 2024 | Approved | |
Vault 1.18.0 | 3962 | Thursday, October 10, 2024 | Approved | |
Vault 1.17.6 | 3286 | Thursday, September 26, 2024 | Approved | |
Vault 1.17.5 | 4326 | Saturday, August 31, 2024 | Approved | |
Vault 1.17.4 | 170 | Friday, August 30, 2024 | Approved | |
Vault 1.17.3 | 3580 | Thursday, August 8, 2024 | Approved | |
Vault 1.17.2 | 4710 | Thursday, July 11, 2024 | Approved | |
Vault 1.17.1 | 2038 | Thursday, June 27, 2024 | Approved | |
Vault 1.17.0 | 2276 | Thursday, June 13, 2024 | Approved | |
Vault 1.16.3 | 1919 | Thursday, May 30, 2024 | Approved | |
Vault 1.16.2 | 4578 | Wednesday, April 24, 2024 | Approved | |
Vault 1.16.1 | 2620 | Friday, April 5, 2024 | Approved | |
Vault 1.16.0 | 1434 | Wednesday, March 27, 2024 | Approved | |
Vault 1.15.6 | 4457 | Friday, March 1, 2024 | Approved | |
Vault 1.15.5 | 8052 | Wednesday, January 31, 2024 | Approved | |
Vault 1.15.4 | 21061 | Wednesday, December 6, 2023 | Approved | |
Vault 1.15.3 | 927 | Friday, December 1, 2023 | Approved | |
Vault 1.15.2 | 6057 | Thursday, November 9, 2023 | Approved | |
Vault 1.15.1 | 2982 | Thursday, October 26, 2023 | Approved | |
Vault 1.15.0 | 5348 | Wednesday, September 27, 2023 | Approved | |
Vault 1.14.3 | 2341 | Thursday, September 14, 2023 | Approved | |
Vault 1.14.2 | 1992 | Wednesday, August 30, 2023 | Approved | |
Vault 1.14.1 | 4162 | Wednesday, July 26, 2023 | Approved | |
Vault 1.14.0 | 4690 | Wednesday, June 21, 2023 | Approved | |
Vault 1.13.3 | 1609 | Friday, June 9, 2023 | Approved | |
Vault 1.13.2 | 13510 | Thursday, April 27, 2023 | Approved | |
Vault 1.13.1 | 4253 | Thursday, March 30, 2023 | Approved | |
Vault 1.13.0 | 1554 | Tuesday, March 7, 2023 | Approved | |
Vault 1.12.3 | 2146 | Thursday, February 23, 2023 | Approved | |
Vault 1.12.2 | 6008 | Saturday, December 17, 2022 | Approved | |
Vault 1.11.1 | 25123 | Wednesday, July 27, 2022 | Approved | |
Vault 1.11.0 | 2559 | Tuesday, June 21, 2022 | Approved | |
Vault 1.10.4 | 536 | Friday, June 17, 2022 | Approved | |
Vault 1.10.3 | 3378 | Friday, May 13, 2022 | Approved | |
Vault 1.10.2 | 64 | Friday, May 13, 2022 | Approved | |
Vault 1.10.1 | 1542 | Monday, April 25, 2022 | Approved | |
Vault 1.10.0 | 2334 | Friday, March 25, 2022 | Approved | |
Vault 1.9.4 | 1435 | Wednesday, March 9, 2022 | Approved | |
Vault 1.9.3 | 2363 | Monday, January 31, 2022 | Approved | |
Vault 1.9.2 | 1967 | Wednesday, December 22, 2021 | Approved | |
Vault 1.9.1 | 1106 | Tuesday, December 14, 2021 | Approved | |
Vault 1.9.0 | 1611 | Tuesday, November 23, 2021 | Approved | |
Vault 1.8.5 | 102 | Tuesday, November 23, 2021 | Approved | |
Vault 1.8.4 | 3139 | Friday, October 8, 2021 | Approved | |
Vault 1.8.3 | 691 | Friday, October 1, 2021 | Approved | |
Vault 1.8.2 | 718 | Thursday, September 30, 2021 | Approved | |
Vault 1.8.1 | 172 | Thursday, September 30, 2021 | Approved | |
Vault 1.8.0 | 3330 | Thursday, July 29, 2021 | Approved | |
Vault 1.7.3 | 2711 | Thursday, June 17, 2021 | Approved | |
Vault 1.7.2 | 1975 | Friday, May 21, 2021 | Approved | |
Vault 1.7.1 | 1562 | Monday, April 26, 2021 | Approved | |
Vault 1.7.0 | 1596 | Tuesday, April 6, 2021 | Approved | |
Vault 1.6.3 | 468 | Thursday, March 25, 2021 | Approved | |
Vault 1.6.2 | 4024 | Monday, February 1, 2021 | Approved | |
Vault 1.6.1 | 745 | Thursday, January 21, 2021 | Approved | |
Vault 1.5.5 | 5748 | Friday, October 23, 2020 | Approved | |
Vault 1.5.4 | 21900 | Thursday, October 22, 2020 | Approved | |
Vault 1.5.3 | 621 | Thursday, October 22, 2020 | Approved | |
Vault 1.5.2 | 2354 | Wednesday, August 26, 2020 | Approved | |
Vault 1.5.0 | 1689 | Wednesday, July 22, 2020 | Approved | |
Vault 1.4.3 | 912 | Friday, July 3, 2020 | Approved | |
Vault 1.4.1 | 1768 | Monday, May 4, 2020 | Approved | |
Vault 1.4.0 | 1410 | Thursday, April 9, 2020 | Approved | |
Vault 1.3.4 | 254 | Wednesday, April 8, 2020 | Approved | |
Vault 1.3.3 | 948 | Monday, March 9, 2020 | Approved | |
Vault 1.3.2 | 1514 | Friday, January 24, 2020 | Approved | |
Vault 1.3.1 | 1671 | Friday, December 20, 2019 | Approved | |
Vault 1.3.0 | 529 | Wednesday, December 11, 2019 | Approved | |
Vault 1.2.4 | 1048 | Tuesday, November 12, 2019 | Approved | |
Vault 1.2.3 | 3439 | Monday, September 16, 2019 | Approved | |
Vault 1.2.2 | 2379 | Friday, August 16, 2019 | Approved | |
Vault 1.2.1 | 197 | Thursday, August 8, 2019 | Approved | |
Vault 1.2.0 | 980 | Wednesday, July 31, 2019 | Approved | |
Vault 1.1.1 | 5094 | Tuesday, April 16, 2019 | Approved | |
Vault 1.1.0 | 1057 | Tuesday, March 19, 2019 | Approved | |
Vault 1.0.3 | 730 | Friday, March 1, 2019 | Approved | |
Vault 0.10.0 | 3157 | Monday, April 16, 2018 | Approved | |
Vault 0.10.0-rc1 | 325 | Saturday, April 7, 2018 | Approved | |
Vault 0.9.6 | 513 | Saturday, April 7, 2018 | Approved | |
Vault 0.9.5 | 297 | Saturday, April 7, 2018 | Approved | |
Vault 0.9.4 | 378 | Saturday, April 7, 2018 | Approved | |
Vault 0.9.3 | 319 | Saturday, April 7, 2018 | Approved | |
Vault 0.9.2 | 317 | Saturday, April 7, 2018 | Approved | |
Vault 0.9.1 | 1026 | Saturday, January 13, 2018 | Approved | |
Vault 0.9.0 | 394 | Saturday, January 13, 2018 | Approved | |
Vault 0.8.3 | 986 | Wednesday, September 20, 2017 | Approved | |
Vault 0.8.2 | 398 | Wednesday, September 20, 2017 | Approved | |
Vault 0.8.1 | 477 | Thursday, August 24, 2017 | Approved | |
Vault 0.8.0 | 470 | Thursday, August 24, 2017 | Approved | |
Vault 0.7.3 | 590 | Thursday, June 8, 2017 | Approved | |
Vault 0.7.2 | 450 | Wednesday, June 7, 2017 | Approved | |
Vault 0.7.1 | 409 | Wednesday, June 7, 2017 | Approved | |
Vault 0.7.0 | 429 | Wednesday, June 7, 2017 | Approved | |
Vault 0.6.5 | 958 | Wednesday, February 8, 2017 | Approved | |
Vault 0.6.4 | 568 | Thursday, December 22, 2016 | Approved | |
Vault 0.6.3 | 430 | Wednesday, December 14, 2016 | Approved | |
Vault 0.6.2 | 505 | Tuesday, October 25, 2016 | Approved | |
Vault 0.6.1 | 503 | Tuesday, August 30, 2016 | Approved |
HashiCorp 2015-2021
1.6.2
### January 29, 2021
SECURITY:
* IP Address Disclosure: We fixed a vulnerability where, under some error
conditions, Vault would return an error message disclosing internal IP
addresses. This vulnerability affects Vault and Vault Enterprise and is fixed in
1.6.2 (CVE-2021-3024).
* Limited Unauthenticated Remove Peer: As of Vault 1.6, the remove-peer command
on DR secondaries did not require authentication. This issue impacts the
stability of HA architecture, as a bad actor could remove all standby
nodes from a DR
secondary. This issue affects Vault Enterprise 1.6.0 and 1.6.1, and is fixed in
1.6.2 (CVE-2021-3282).
* Mount Path Disclosure: Vault previously returned different HTTP status codes for
existent and non-existent mount paths. This behavior would allow unauthenticated
brute force attacks to reveal which paths had valid mounts. This issue affects
Vault and Vault Enterprise and is fixed in 1.6.2 (CVE-2020-25594).
CHANGES:
* go: Update go version to 1.15.7 [GH-10730]
FEATURES:
* ui: Adds check for feature flag on application, and updates namespace toolbar on login if present [GH-10588]
IMPROVEMENTS:
* core (enterprise): "vault status" command works when a namespace is set. [GH-10725]
* core: reduce memory used by leases [GH-10726]
* storage/raft (enterprise): Listing of peers is now allowed on DR secondary
cluster nodes, as an update operation that takes in DR operation token for
authenticating the request.
BUG FIXES:
* agent: Set namespace for template server in agent. [GH-10757]
* core: Make the response to an unauthenticated request to sys/internal endpoints consistent regardless of mount existence. [GH-10650]
* metrics: Protect emitMetrics from panicking during post-seal [GH-10708]
* secrets/gcp: Fix issue with account and iam_policy roleset WALs not being removed after attempts when GCP project no longer exists [GH-10759]
* storage/raft (enterprise): Automated snapshots with Azure required specifying
azure_blob_environment
, which should have had as a default AZUREPUBLICCLOUD
.
* storage/raft (enterprise): Autosnapshots config and storage weren't excluded from
performance replication, causing conflicts and errors.
* ui: Fix bug that double encodes secret route when there are spaces in the path and makes you unable to view the version history. [GH-10596]
* ui: Fix expected response from feature-flags endpoint [GH-10684]
## Previous Releases
For more information on previous releases, check out the changelog on GitHub.
This package has no dependencies.
Ground Rules:
- 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.