Downloads:

43,792

Downloads of v 1.2.4:

935

Last Update:

12 Nov 2019

Package Maintainer(s):

Software Author(s):

  • Mitchell Hashimoto
  • HashiCorp

Tags:

vault hashicorp

Vault

This is not the latest version of Vault available.

1.2.4 | Updated: 12 Nov 2019

Downloads:

43,792

Downloads of v 1.2.4:

935

Maintainer(s):

Software Author(s):

  • Mitchell Hashimoto
  • HashiCorp

Tags:

vault hashicorp

Vault 1.2.4

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: 1.2.4
    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  '1.2.4'
  source   'STEP 3 URL'
end

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


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

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


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

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


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

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


salt '*' chocolatey.install vault version="1.2.4" 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 12 Nov 2019.

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 
$packageArgs = @{
  PackageName         = "vault"
  Url                 = "https://releases.hashicorp.com/vault/$($version)/vault_$($version)_windows_386.zip"
  UnzipLocation       = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
  Url64               = "https://releases.hashicorp.com/vault/$($version)/vault_$($version)_windows_amd64.zip"
  Checksum            = 'ca0c2d6dcb08570e08f7e5154501ac0ce5ab14520086615b4a5767fe12daed30'
  ChecksumType        = 'sha256'
  Checksum64          = '0f8931876b382ba558c5d061442d95df793a28b1c7b7a799b1ab33204670c2a8'
  version             = '1.2.4'  
}

Install-ChocolateyZipPackage @packageArgs

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 1824 Monday, February 1, 2021 Approved
Vault 1.6.1 614 Thursday, January 21, 2021 Approved
Vault 1.5.5 3175 Friday, October 23, 2020 Approved
Vault 1.5.4 1582 Thursday, October 22, 2020 Approved
Vault 1.5.3 230 Thursday, October 22, 2020 Approved
Vault 1.5.2 2210 Wednesday, August 26, 2020 Approved
Vault 1.5.0 1490 Wednesday, July 22, 2020 Approved
Vault 1.4.3 784 Friday, July 3, 2020 Approved
Vault 1.4.1 1628 Monday, May 4, 2020 Approved
Vault 1.4.0 1269 Thursday, April 9, 2020 Approved

1.2.4 (November 7th, 2019)

SECURITY:

* In a non-root namespace, revocation of a token scoped to a non-root namespace did not trigger the expected revocation of dynamic secret leases associated with that token. As a result, dynamic secret leases in non-root namespaces may outlive the token that created them. This vulnerability, CVE-2019-18616, affects Vault Enterprise 0.11.0 and newer.
* Disaster Recovery secondary clusters did not delete already-replicated data after a mount filter has been created on an upstream Performance secondary cluster. As a result, encrypted secrets may remain replicated on a Disaster Recovery secondary cluster after application of a mount filter excluding those secrets from replication. This vulnerability, CVE-2019-18617, affects Vault Enterprise 0.8 and newer.
* Update version of Go to 1.12.12 to fix Go bug golang.org/issue/34960 which corresponds to CVE-2019-17596.

CHANGES:

* auth/aws: If a custom sts_endpoint is configured, Vault Agent and the CLI
should provide the corresponding region via the region parameter (which
already existed as a CLI parameter, and has now been added to Agent). The
automatic region detection added to the CLI and Agent in 1.2 has been removed.

IMPROVEMENTS:

* cli: Ignore existing token during CLI login [GH-7508]
* core: Log proxy settings from environment on startup [GH-7528]
* core: Cache whether we've been initialized to reduce load on storage [GH-7549]

BUG FIXES:

* agent: Fix handling of gzipped responses [GH-7470]
* cli: Fix panic when pgp keys list is empty [GH-7546]
* core: add hook for initializing seals for migration [GH-7666]
* core (enterprise): Migrating from one auto unseal method to another never
worked on enterprise, now it does.
* identity: Add required field response_types_supported to identity token
.well-known/openid-configuration response [GH-7533]
* identity: Fixed nil pointer panic when merging entities [GH-7712]
* replication (Enterprise): Fix issue causing performance standbys nodes
disconnecting when under high loads.
* secrets/azure: Fix panic that could occur if client retries timeout [GH-7793]
* secrets/database: Fix bug in combined DB secrets engine that can result in
writes to static-roles endpoints timing out [GH-7518]
* secrets/pki: Improve tidy to continue when value is nil [GH-7589]
* ui (Enterprise): Allow kv v2 secrets that are gated by Control Groups to be
viewed in the UI [GH-7504]
* cli: Command timeouts are now always specified solely by the
VAULT_CLIENT_TIMEOUT value. [GH-7469]

## 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