Unpacking Software Livestream

Join our monthly Unpacking Software livestream to hear about the latest news, chat and opinion on packaging, software deployment and lifecycle management!

Learn More

Chocolatey Product Spotlight

Join the Chocolatey Team on our regular monthly stream where we put a spotlight on the most recent Chocolatey product releases. You'll have a chance to have your questions answered in a live Ask Me Anything format.

Learn More

Chocolatey Coding Livestream

Join us for the Chocolatey Coding Livestream, where members of our team dive into the heart of open source development by coding live on various Chocolatey projects. Tune in to witness real-time coding, ask questions, and gain insights into the world of package management. Don't miss this opportunity to engage with our team and contribute to the future of Chocolatey!

Learn More

Calling All Chocolatiers! Whipping Up Windows Automation with Chocolatey Central Management

Webinar from
Wednesday, 17 January 2024

We are delighted to announce the release of Chocolatey Central Management v0.12.0, featuring seamless Deployment Plan creation, time-saving duplications, insightful Group Details, an upgraded Dashboard, bug fixes, user interface polishing, and refined documentation. As an added bonus we'll have members of our Solutions Engineering team on-hand to dive into some interesting ways you can leverage the new features available!

Watch On-Demand
Chocolatey Community Coffee Break

Join the Chocolatey Team as we discuss all things Community, what we do, how you can get involved and answer your Chocolatey questions.

Watch The Replays
Chocolatey and Intune Overview

Webinar Replay from
Wednesday, 30 March 2022

At Chocolatey Software we strive for simple, and teaching others. Let us teach you just how simple it could be to keep your 3rd party applications updated across your devices, all with Intune!

Watch On-Demand
Chocolatey For Business. In Azure. In One Click.

Livestream from
Thursday, 9 June 2022

Join James and Josh to show you how you can get the Chocolatey For Business recommended infrastructure and workflow, created, in Azure, in around 20 minutes.

Watch On-Demand
The Future of Chocolatey CLI

Livestream from
Thursday, 04 August 2022

Join Paul and Gary to hear more about the plans for the Chocolatey CLI in the not so distant future. We'll talk about some cool new features, long term asks from Customers and Community and how you can get involved!

Watch On-Demand
Hacktoberfest Tuesdays 2022

Livestreams from
October 2022

For Hacktoberfest, Chocolatey ran a livestream every Tuesday! Re-watch Cory, James, Gary, and Rain as they share knowledge on how to contribute to open-source projects such as Chocolatey CLI.

Watch On-Demand

Downloads:

260,753

Downloads of v 0.9.0:

391

Last Update:

13 Jan 2018

Package Maintainer(s):

Software Author(s):

  • Mitchell Hashimoto
  • HashiCorp

Tags:

vault hashicorp

Vault

This is not the latest version of Vault available.

  • 1
  • 2
  • 3

0.9.0 | Updated: 13 Jan 2018

Downloads:

260,753

Downloads of v 0.9.0:

391

Maintainer(s):

Software Author(s):

  • Mitchell Hashimoto
  • HashiCorp

Vault 0.9.0

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

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed


Validation Testing Passed


Verification Testing Passed

Details

Scan Testing Resulted in Flagged:

This package was submitted (and approved) prior to automated virus scanning integration into the package moderation processs.

We recommend clicking the "Details" link to make your own decision on installing this package.

Details
Learn More

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:

NOTE

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

  • 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

3. Copy Your Script

choco upgrade vault -y --source="'INTERNAL REPO URL'" --version="'0.9.0'" [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="'0.9.0'" 
$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: '0.9.0'
    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  '0.9.0'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


cChocoPackageInstaller vault
{
    Name     = "vault"
    Version  = "0.9.0"
    Source   = "INTERNAL REPO URL"
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'vault':
  ensure   => '0.9.0',
  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.

Package Approved

This package was approved as a trusted package on 13 Jan 2018.

Description

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.


tools\chocolateyInstall.ps1
$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.

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.0 3953 Thursday, October 10, 2024 Approved
Vault 1.17.6 3052 Thursday, September 26, 2024 Approved
Vault 1.17.5 4194 Saturday, August 31, 2024 Approved
Vault 1.17.4 165 Friday, August 30, 2024 Approved
Vault 1.17.3 3579 Thursday, August 8, 2024 Approved
Vault 1.17.2 4706 Thursday, July 11, 2024 Approved
Vault 1.17.1 2030 Thursday, June 27, 2024 Approved
Vault 1.17.0 2274 Thursday, June 13, 2024 Approved
Vault 1.16.3 1914 Thursday, May 30, 2024 Approved
Vault 1.16.2 4570 Wednesday, April 24, 2024 Approved
Vault 1.16.1 2619 Friday, April 5, 2024 Approved
Vault 1.16.0 1432 Wednesday, March 27, 2024 Approved
Vault 1.15.6 4456 Friday, March 1, 2024 Approved
Vault 1.15.5 8052 Wednesday, January 31, 2024 Approved
Vault 1.15.4 21060 Wednesday, December 6, 2023 Approved
Vault 1.15.3 927 Friday, December 1, 2023 Approved
Vault 1.15.2 6056 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 2302 Thursday, September 14, 2023 Approved
Vault 1.14.2 1992 Wednesday, August 30, 2023 Approved
Vault 1.14.1 4159 Wednesday, July 26, 2023 Approved
Vault 1.14.0 4690 Wednesday, June 21, 2023 Approved
Vault 1.13.3 1607 Friday, June 9, 2023 Approved
Vault 1.13.2 13506 Thursday, April 27, 2023 Approved
Vault 1.13.1 4248 Thursday, March 30, 2023 Approved
Vault 1.13.0 1553 Tuesday, March 7, 2023 Approved
Vault 1.12.3 2146 Thursday, February 23, 2023 Approved
Vault 1.12.2 6003 Saturday, December 17, 2022 Approved
Vault 1.11.1 25042 Wednesday, July 27, 2022 Approved
Vault 1.11.0 2559 Tuesday, June 21, 2022 Approved
Vault 1.10.4 534 Friday, June 17, 2022 Approved
Vault 1.10.3 3373 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 1434 Wednesday, March 9, 2022 Approved
Vault 1.9.3 2359 Monday, January 31, 2022 Approved
Vault 1.9.2 1964 Wednesday, December 22, 2021 Approved
Vault 1.9.1 1105 Tuesday, December 14, 2021 Approved
Vault 1.9.0 1610 Tuesday, November 23, 2021 Approved
Vault 1.8.5 102 Tuesday, November 23, 2021 Approved
Vault 1.8.4 3135 Friday, October 8, 2021 Approved
Vault 1.8.3 690 Friday, October 1, 2021 Approved
Vault 1.8.2 715 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 2709 Thursday, June 17, 2021 Approved
Vault 1.7.2 1975 Friday, May 21, 2021 Approved
Vault 1.7.1 1561 Monday, April 26, 2021 Approved
Vault 1.7.0 1596 Tuesday, April 6, 2021 Approved
Vault 1.6.3 467 Thursday, March 25, 2021 Approved
Vault 1.6.2 4024 Monday, February 1, 2021 Approved
Vault 1.6.1 744 Thursday, January 21, 2021 Approved
Vault 1.5.5 5644 Friday, October 23, 2020 Approved
Vault 1.5.4 21900 Thursday, October 22, 2020 Approved
Vault 1.5.3 619 Thursday, October 22, 2020 Approved
Vault 1.5.2 2353 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 252 Wednesday, April 8, 2020 Approved
Vault 1.3.3 943 Monday, March 9, 2020 Approved
Vault 1.3.2 1513 Friday, January 24, 2020 Approved
Vault 1.3.1 1670 Friday, December 20, 2019 Approved
Vault 1.3.0 528 Wednesday, December 11, 2019 Approved
Vault 1.2.4 1048 Tuesday, November 12, 2019 Approved
Vault 1.2.3 3436 Monday, September 16, 2019 Approved
Vault 1.2.2 2378 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 1055 Tuesday, March 19, 2019 Approved
Vault 1.0.3 730 Friday, March 1, 2019 Approved
Vault 0.10.0 3155 Monday, April 16, 2018 Approved
Vault 0.10.0-rc1 325 Saturday, April 7, 2018 Approved
Vault 0.9.6 512 Saturday, April 7, 2018 Approved
Vault 0.9.5 295 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 1025 Saturday, January 13, 2018 Approved
Vault 0.9.0 391 Saturday, January 13, 2018 Approved
Vault 0.8.3 984 Wednesday, September 20, 2017 Approved
Vault 0.8.2 398 Wednesday, September 20, 2017 Approved
Vault 0.8.1 472 Thursday, August 24, 2017 Approved
Vault 0.8.0 468 Thursday, August 24, 2017 Approved
Vault 0.7.3 590 Thursday, June 8, 2017 Approved
Vault 0.7.2 449 Wednesday, June 7, 2017 Approved
Vault 0.7.1 408 Wednesday, June 7, 2017 Approved
Vault 0.7.0 429 Wednesday, June 7, 2017 Approved
Vault 0.6.5 954 Wednesday, February 8, 2017 Approved
Vault 0.6.4 566 Thursday, December 22, 2016 Approved
Vault 0.6.3 429 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

0.9.0 (November 14th, 2017)

DEPRECATIONS/CHANGES:

  • API HTTP client behavior: When calling NewClient the 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 DefaultConfig as 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 disallow_reauthentication and allow_instance_migration.
  • SSH CA role read changes: When reading back a role from the ssh backend, 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 ssh backend via the API, the response data will additionally return a key_info map that will contain a map of each key with a corresponding object containing the key_type.
  • More granularity in audit logs: Audit request and response entires are still in RFC3339 format but now have a granularity of nanoseconds.

FEATURES:

  • 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 rekey operation 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.

IMPROVEMENTS:

  • 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 700 as permissions when creating directories. The files themselves were 600 and 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 pki as 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 none hash 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

BUG FIXES:

  • api: Fix panic when setting a custom HTTP client but with a nil transport [GH-3435] [GH-3437]
  • api: Fix authing to the cert backend 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

Previous Releases

For more information on previous releases, check out the changelog on GitHub.


This package has no dependencies.

Discussion for the Vault Package

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.
comments powered by Disqus