Downloads:

40,240

Downloads of v 0.9.4:

236

Last Update:

07 Apr 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.4 | Updated: 07 Apr 2018

Downloads:

40,240

Downloads of v 0.9.4:

236

Maintainer(s):

Software Author(s):

  • Mitchell Hashimoto
  • HashiCorp

Vault 0.9.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: 0.9.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  '0.9.4'
  source   'STEP 3 URL'
end

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


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

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


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

This package was approved as a trusted package on 07 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 = '0f175e7c90de03cb022a82116c9bb60d542cac4d8bfb0e30c9b0eeccc2343083'
$checksum64 = '4d0b517907f708eae43b85f96ea5a6c92842a7350aaa20a88600d9e2589a1afb'
$version = '0.9.4'
$url = "https://releases.hashicorp.com/vault/$($version)/vault_$($version)_windows_386.zip"
$url64bit = "https://releases.hashicorp.com/vault/$($version)/vault_$($version)_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.5.4 972 Thursday, October 22, 2020 Approved
Vault 1.5.3 86 Thursday, October 22, 2020 Approved
Vault 1.5.2 2204 Wednesday, August 26, 2020 Approved
Vault 1.5.0 1479 Wednesday, July 22, 2020 Approved
Vault 1.4.3 773 Friday, July 3, 2020 Approved
Vault 1.4.1 1622 Monday, May 4, 2020 Approved
Vault 1.4.0 1262 Thursday, April 9, 2020 Approved
Vault 1.3.4 133 Wednesday, April 8, 2020 Approved
Vault 1.3.3 792 Monday, March 9, 2020 Approved

0.9.4 (February 20th, 2018)

SECURITY:

  • Role Tags used with the EC2 style of AWS auth were being improperly parsed; as a result they were not being used to properly restrict values. Implementations following our suggestion of using these as defense-in-depth rather than the only source of restriction should not have significant impact.

FEATURES:

  • ChaCha20-Poly1305 support in transit: You can now encrypt and decrypt with ChaCha20-Poly1305 in transit. Key derivation and convergent encryption is also supported.
  • Okta Push support in Okta Auth Backend: If a user account has MFA required within Okta, an Okta Push MFA flow can be used to successfully finish authentication.
  • PKI Improvements: Custom OID subject alternate names can now be set, subject to allow restrictions that support globbing. Additionally, Country, Locality, Province, Street Address, and Postal Code can now be set in certificate subjects.
  • Manta Storage: Joyent Triton Manta can now be used for Vault storage
  • Google Cloud Spanner Storage: Google Cloud Spanner can now be used for Vault storage

IMPROVEMENTS:

  • auth/centrify: Add CLI helper
  • audit: Always log failure metrics, even if zero, to ensure the values appear on dashboards [GH-3937]
  • cli: Disable color when output is not a TTY [GH-3897]
  • cli: Add -format flag to all subcommands [GH-3897]
  • cli: Do not display deprecation warnings when the format is not table [GH-3897]
  • core: If over a predefined lease count (256k), log a warning not more than once a minute. Too many leases can be problematic for many of the storage backends and often this number of leases is indicative of a need for workflow improvements. [GH-3957]
  • secret/nomad: Have generated ACL tokens cap out at 64 characters [GH-4009]
  • secret/pki: Country, Locality, Province, Street Address, and Postal Code can now be set on certificates [GH-3992]
  • secret/pki: UTF-8 Other Names can now be set in Subject Alternate Names in issued certs; allowed values can be set per role and support globbing [GH-3889]
  • secret/pki: Add a flag to make the common name optional on certs [GH-3940]
  • secret/pki: Ensure only DNS-compatible names go into DNS SANs; additionally, properly handle IDNA transformations for these DNS names [GH-3953]
  • secret/ssh: Add valid-principles flag to CLI for CA mode [GH-3922]
  • storage/manta: Add Manta storage [GH-3270]
  • ui (Enterprise): Support for ChaCha20-Poly1305 keys in the transit engine.

BUG FIXES:

  • api/renewer: Honor increment value in renew auth calls [GH-3904]
  • auth/approle: Fix inability to use limited-use-count secret IDs on replication performance secondaries
  • auth/approle: Cleanup of secret ID accessors during tidy and removal of dangling accessor entries [GH-3924]
  • auth/aws-ec2: Avoid masking of role tag response [GH-3941]
  • auth/cert: Verify DNS SANs in the authenticating certificate [GH-3982]
  • auth/okta: Return configured durations as seconds, not nanoseconds [GH-3871]
  • auth/token: Token creation via the CLI no longer forces periodic token creation. Passing an explicit zero value for the period no longer create periodic tokens. [GH-3880]
  • command/rekey: Re-add lost stored-shares parameter [GH-3974]
  • command/ssh: Create and reuse the api client [GH-3909]
  • command/status: Fix panic when status returns 500 from leadership lookup [GH-3998]
  • identity: Fix race when creating entities [GH-3932]
  • plugin/gRPC: Fixed an issue with list requests and raw responses coming from plugins using gRPC transport [GH-3881]
  • plugin/gRPC: Fix panic when special paths are not set [GH-3946]
  • secret/pki: Verify a name is a valid hostname before adding to DNS SANs [GH-3918]
  • secret/transit: Fix auditing when reading a key after it has been backed up or restored [GH-3919]
  • secret/transit: Fix storage/memory consistency when persistence fails [GH-3959]
  • storage/consul: Validate that service names are RFC 1123 compliant [GH-3960]
  • storage/etcd3: Fix memory ballooning with standby instances [GH-3798]
  • storage/etcd3: Fix large lists (like token loading at startup) not being handled [GH-3772]
  • storage/postgresql: Fix compatibility with versions using custom string version tags [GH-3949]
  • storage/zookeeper: Update vendoring to fix freezing issues [GH-3896]
  • ui (Enterprise): Decoding the replication token should no longer error and prevent enabling of a secondary replication cluster via the ui.
  • plugin/gRPC: Add connection info to the request object [GH-3997]

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