Downloads:

43,272

Downloads of v 0.9.1:

893

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.

0.9.1 | Updated: 13 Jan 2018

Downloads:

43,272

Downloads of v 0.9.1:

893

Maintainer(s):

Software Author(s):

  • Mitchell Hashimoto
  • HashiCorp

Vault 0.9.1

This is not the latest version of Vault available.

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

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:

>

NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • 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://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. Enter your internal repository url

(this should look similar to https://chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade vault -y --source="'STEP 3 URL'" [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="'STEP 3 URL'"
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode

- name: Ensure vault installed
  win_chocolatey:
    name: vault
    state: present
    version: 0.9.1
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'vault' do
  action    :install
  version  '0.9.1'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: vault,
    Version: 0.9.1,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller vault
{
   Name     = 'vault'
   Ensure   = 'Present'
   Version  = '0.9.1'
   Source   = 'STEP 3 URL'
}

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


package { 'vault':
  provider => 'chocolatey',
  ensure   => '0.9.1',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install vault version="0.9.1" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. 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 04 Apr 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 = 'fecac943606c9549d026ce6aa6b98baf659b5f78f284e8ddcef81bb21199b24b'
$checksum64 = '5181a518ab1a8516ec1b155128282763a7794baa92b4c8cf502e5effc933383e'
$url = 'https://releases.hashicorp.com/vault/0.9.1/vault_0.9.1_windows_386.zip'
$url64bit = 'https://releases.hashicorp.com/vault/0.9.1/vault_0.9.1_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.

Version Downloads Last Updated Status
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

0.9.1 (December 21st, 2017)

DEPRECATIONS/CHANGES:

  • AppRole Case Sensitivity: In prior versions of Vault, list operations against AppRole roles would require preserving case in the role name, even though most other operations within AppRole are case-insensitive with respect to the role name. This has been fixed; existing roles will behave as they have in the past, but new roles will act case-insensitively in these cases.
  • Token Auth Backend Roles parameter types: For allowed_policies and disallowed_policies in role definitions in the token auth backend, input can now be a comma-separated string or an array of strings. Reading a role will now return arrays for these parameters.
  • Transit key exporting: You can now mark a key in the transit backend as exportable at any time, rather than just at creation time; however, once this value is set, it still cannot be unset.
  • PKI Secret Backend Roles parameter types: For allowed_domains and key_usage in role definitions in the PKI secret backend, input can now be a comma-separated string or an array of strings. Reading a role will now return arrays for these parameters.
  • SSH Dynamic Keys Method Defaults to 2048-bit Keys: When using the dynamic key method in the SSH backend, the default is now to use 2048-bit keys if no specific key bit size is specified.
  • Consul Secret Backend lease handling: The consul secret backend can now accept both strings and integer numbers of seconds for its lease value. The value returned on a role read will be an integer number of seconds instead of a human-friendly string.
  • Unprintable characters not allowed in API paths: Unprintable characters are no longer allowed in names in the API (paths and path parameters), with an extra restriction on whitespace characters. Allowed characters are those that are considered printable by Unicode plus spaces.

FEATURES:

  • Transit Backup/Restore: The transit backend now supports a backup operation that can export a given key, including all key versions and configuration, as well as a restore operation allowing import into another Vault.
  • gRPC Database Plugins: Database plugins now use gRPC for transport, allowing them to be written in other languages.
  • Nomad Secret Backend: Nomad ACL tokens can now be generated and revoked using Vault.
  • TLS Cert Auth Backend Improvements: The cert auth backend can now match against custom certificate extensions via exact or glob matching, and additionally supports max_ttl and periodic token toggles.

IMPROVEMENTS:

  • auth/cert: Support custom certificate constraints [GH-3634]
  • auth/cert: Support setting max_ttl and period [GH-3642]
  • audit/file: Setting a file mode of 0000 will now disable Vault from automatically chmoding the log file [GH-3649]
  • auth/github: The legacy MFA system can now be used with the GitHub auth backend [GH-3696]
  • auth/okta: The legacy MFA system can now be used with the Okta auth backend [GH-3653]
  • auth/token: allowed_policies and disallowed_policies can now be specified as a comma-separated string or an array of strings [GH-3641]
  • command/server: The log level can now be specified with VAULT_LOG_LEVEL [GH-3721]
  • core: Period values from auth backends will now be checked and applied to the TTL value directly by core on login and renewal requests [GH-3677]
  • database/mongodb: Add optional write_concern parameter, which can be set during database configuration. This establishes a session-wide write concern for the lifecycle of the mount [GH-3646]
  • http: Request path containing non-printable characters will return 400 - Bad Request [GH-3697]
  • mfa/okta: Filter a given email address as a login filter, allowing operation when login email and account email are different
  • plugins: Make Vault more resilient when unsealing when plugins are unavailable [GH-3686]
  • secret/pki: allowed_domains and key_usage can now be specified as a comma-separated string or an array of strings [GH-3642]
  • secret/ssh: Allow 4096-bit keys to be used in dynamic key method [GH-3593]
  • secret/consul: The Consul secret backend now uses the value of lease set on the role, if set, when renewing a secret. [GH-3796]
  • storage/mysql: Don't attempt database creation if it exists, which can help under certain permissions constraints [GH-3716]

BUG FIXES:

  • api/status (enterprise): Fix status reporting when using an auto seal
  • auth/approle: Fix case-sensitive/insensitive comparison issue [GH-3665]
  • auth/cert: Return allowed_names on role read [GH-3654]
  • auth/ldap: Fix incorrect control information being sent [GH-3402] [GH-3496] [GH-3625] [GH-3656]
  • core: Fix seal status reporting when using an autoseal
  • core: Add creation path to wrap info for a control group token
  • core: Fix potential panic that could occur using plugins when a node transitioned from active to standby [GH-3638]
  • core: Fix memory ballooning when a connection would connect to the cluster port and then go away -- redux! [GH-3680]
  • core: Replace recursive token revocation logic with depth-first logic, which can avoid hitting stack depth limits in extreme cases [GH-2348]
  • core: When doing a read on configured audited-headers, properly handle case insensitivity [GH-3701]
  • core/pkcs11 (enterprise): Fix panic when PKCS#11 library is not readable
  • database/mysql: Allow the creation statement to use commands that are not yet supported by the prepare statement protocol [GH-3619]
  • plugin/auth-gcp: Fix IAM roles when using allow_gce_inference [VPAG-19]

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