Downloads:

43,272

Downloads of v 0.8.2:

268

Last Update:

20 Sep 2017

Package Maintainer(s):

Software Author(s):

  • Mitchell Hashimoto
  • HashiCorp

Tags:

vault hashicorp

Vault

This is not the latest version of Vault available.

0.8.2 | Updated: 20 Sep 2017

Downloads:

43,272

Downloads of v 0.8.2:

268

Maintainer(s):

Software Author(s):

  • Mitchell Hashimoto
  • HashiCorp

Tags:

vault hashicorp

Vault 0.8.2

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.8.2
    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.8.2'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: vault,
    Version: 0.8.2,
    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.8.2'
   Source   = 'STEP 3 URL'
}

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


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

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


salt '*' chocolatey.install vault version="0.8.2" 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.

This package was approved as a trusted package on 20 Sep 2017.

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 = 'a29e86465cca8293f803aed62f25a34295e0ed79122ca855cedc5d3fb6611b12'
$checksum64 = '5395c306bfb033a426f3752a1070ec641372b32134e34f6cd43c53a3f2ed4946'
$url = 'https://releases.hashicorp.com/vault/0.8.2/vault_0.8.2_windows_386.zip'
$url64bit = 'https://releases.hashicorp.com/vault/0.8.2/vault_0.8.2_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.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

0.8.2 (September 5th, 2017)

SECURITY:

  • In prior versions of Vault, if authenticating via AWS IAM and requesting a periodic token, the period was not properly respected. This could lead to tokens expiring unexpectedly, or a token lifetime being longer than expected. Upon token renewal with Vault 0.8.2 the period will be properly enforced.

DEPRECATIONS/CHANGES:

  • vault ssh users should supply -mode and -role to reduce the number of API calls. A future version of Vault will mark these optional values are required. Failure to supply -mode or -role will result in a warning.
  • Vault plugins will first briefly run a restricted version of the plugin to fetch metadata, and then lazy-load the plugin on first request to prevent crash/deadlock of Vault during the unseal process. Plugins will need to be built with the latest changes in order for them to run properly.

FEATURES:

  • Lazy Lease Loading: On startup, Vault will now load leases from storage in a lazy fashion (token checks and revocation/renewal requests still force an immediate load). For larger installations this can significantly reduce downtime when switching active nodes or bringing Vault up from cold start.
  • SSH CA Login with vault ssh: vault ssh now supports the SSH CA backend for authenticating to machines. It also supports remote host key verification through the SSH CA backend, if enabled.
  • Signing of Self-Issued Certs in PKI: The pki backend now supports signing self-issued CA certs. This is useful when switching root CAs.

IMPROVEMENTS:

  • audit/file: Allow specifying stdout as the file_path to log to standard output [GH-3235]
  • auth/aws: Allow wildcards in bound_iam_principal_id [GH-3213]
  • auth/okta: Compare groups case-insensitively since Okta is only case-preserving [GH-3240]
  • auth/okta: Standarize Okta configuration APIs across backends [GH-3245]
  • cli: Add subcommand autocompletion that can be enabled with vault -autocomplete-install [GH-3223]
  • cli: Add ability to handle wrapped responses when using vault auth. What is output depends on the other given flags; see the help output for that command for more information. [GH-3263]
  • core: TLS cipher suites used for cluster behavior can now be set via cluster_cipher_suites in configuration [GH-3228]
  • core: The plugin_name can now either be specified directly as part of the parameter or within the config object when mounting a secret or auth backend via sys/mounts/:path or sys/auth/:path respectively [GH-3202]
  • core: It is now possible to update the description of a mount when mount-tuning, although this must be done through the HTTP layer [GH-3285]
  • secret/databases/mongo: If an EOF is encountered, attempt reconnecting and retrying the operation [GH-3269]
  • secret/pki: TTLs can now be specified as a string or an integer number of seconds [GH-3270]
  • secret/pki: Self-issued certs can now be signed via pki/root/sign-self-issued [GH-3274]
  • storage/gcp: Use application default credentials if they exist [GH-3248]

BUG FIXES:

  • auth/aws: Properly use role-set period values for IAM-derived token renewals [GH-3220]
  • auth/okta: Fix updating organization/ttl/max_ttl after initial setting [GH-3236]
  • core: Fix PROXY when underlying connection is TLS [GH-3195]
  • core: Policy-related commands would sometimes fail to act case-insensitively [GH-3210]
  • storage/consul: Fix parsing TLS configuration when using a bare IPv6 address [GH-3268]
  • plugins: Lazy-load plugins to prevent crash/deadlock during unseal process. [GH-3255]
  • plugins: Skip mounting plugin-based secret and credential mounts when setting up mounts if the plugin is no longer present in the catalog. [GH-3255]

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