Downloads:

43,792

Downloads of v 1.4.0:

1,269

Last Update:

09 Apr 2020

Package Maintainer(s):

Software Author(s):

  • Mitchell Hashimoto
  • HashiCorp

Tags:

vault hashicorp

Vault

This is not the latest version of Vault available.

1.4.0 | Updated: 09 Apr 2020

Downloads:

43,792

Downloads of v 1.4.0:

1,269

Maintainer(s):

Software Author(s):

  • Mitchell Hashimoto
  • HashiCorp

Vault 1.4.0

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

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


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

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


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

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


salt '*' chocolatey.install vault version="1.4.0" 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 09 Apr 2020.

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            = '99a3a30db2508ff75fc52b1976f4144baeaf668ccbba0d73c38ff6c984921773'
  ChecksumType        = 'sha256'
  Checksum64          = 'fc4ebb5c0473359effda328556763e5bc5d5da526e4b035d7f892d05b045c0a2'
  version             = '1.4.0'  
}

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.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.4.0 (April 7th, 2020)

CHANGES:

* cli: The raft configuration command has been renamed to list-peers to avoid confusion.

FEATURES:

* Kerberos Authentication: Vault now supports Kerberos authentication using a SPNEGO token. Login can be performed using the Vault CLI, API, or agent.
* Kubernetes Service Discovery: A new Kubernetes service discovery feature where, if configured, Vault will tag Vault pods with their current health status.
* MongoDB Atlas Secrets: Vault can now generate dynamic credentials for both MongoDB Atlas databases as well as the Atlas programmatic interface.
* OpenLDAP Secrets Engine: We now support password management of existing OpenLDAP user entries.
* Redshift Database Secrets Engine: The database secrets engine now supports static and dynamic secrets for the Amazon Web Services (AWS) Redshift service.
* Service Registration Config: A newly introduced service_registration configuration stanza, that allows for service registration to be configured separately from the storage backend.
* Transform Secrets Engine (Enterprise): A new secrets engine that handles secure data transformation and tokenization against provided input value.
* Integrated Storage: Promoted out of beta and into general availability for both open-source and enterprise workloads.

IMPROVEMENTS:

* agent: add option to force the use of the auth-auth token, and ignore the Vault token in the request GH-8101.
* api: Restore and fix DNS SRV Lookup GH-8520
* audit: HMAC http_raw_body in audit log; this ensures that large authenticated Prometheus metrics responses get replaced with short HMAC values GH-8130
* audit: Generate-root, generate-recovery-token, and generate-dr-operation-token requests and responses are now audited. GH-8301
* auth/aws: Reduce the number of simultaneous STS client credentials needed GH-8161
* auth/azure: subscription ID, resource group, vm and vmss names are now stored in alias metadata GH-30
* auth/jwt: Additional OIDC callback parameters available for CLI logins GH-80 GH-86
* auth/jwt: Bound claims may be optionally configured using globs GH-89
* auth/jwt: Timeout during OIDC CLI login if process doesn't complete within 2 minutes GH-97
* auth/jwt: Add support for the form_post response mode GH-98
* auth/jwt: add optional client_nonce to authorization flow GH-104
* auth/okta: Upgrade okta sdk lib, which should improve handling of groups GH-8143
* aws: Add support for v2 of the instance metadata service (see issue 7924 for all linked PRs)
* core: Separate out service discovery interface from storage interface to allow new types of service discovery not coupled to storage GH-7887
* core: Add support for telemetry option metrics_prefix GH-8340
* core: Entropy Augmentation can now be used with AWS KMS and Vault Transit seals
* core: Allow tls_min_version to be set to TLS 1.3 GH-8305
* cli: Incorrect TLS configuration will now correctly fail GH-8025
* identity: Allow specifying a custom client_id for identity tokens GH-8165
* metrics/prometheus: improve performance with high volume of metrics updates GH-8507
* replication (enterprise): Fix race condition causing clusters with high throughput writes to sometimes fail to enter streaming-wal mode
* replication (enterprise): Secondary clusters can now perform an extra gRPC call to all nodes in a primary cluster in an attempt to resolve the active node's address
* replication (enterprise): The replication status API now outputs last_performance_wal, last_dr_wal, and connection_state values
* replication (enterprise): DR secondary clusters can now be recovered by the replication/dr/secondary/recover API
* replication (enterprise): We now allow for an alternate means to create a Disaster Recovery token, by using a batch token that is created with an ACL that allows for access to one or more of the DR endpoints.
* secrets/database/mongodb: Switched internal MongoDB driver to mongo-driver GH-8140
* secrets/database/mongodb: Add support for x509 client authorization to MongoDB GH-8329
* secrets/database/oracle: Add support for static credential rotation GH-26
* secrets/consul: Add support to specify TLS options per Consul backend GH-4800
* secrets/gcp: Allow specifying the TTL for a service key GH-54
* secrets/gcp: Add support for rotating root keys GH-53
* secrets/gcp: Handle version 3 policies for Resource Manager IAM requests GH-77
* secrets/nomad: Add support to specify TLS options per Nomad backend GH-8083
* secrets/ssh: Allowed users can now be templated with identity information GH-7548
* secrets/transit: Adding RSA3072 key support GH-8151
* storage/consul: Vault returns now a more descriptive error message when only a client cert or a client key has been provided GH-4930
* storage/raft: Nodes in the raft cluster can all be given possible leader addresses for them to continuously try and join one of them, thus automating
the process of join to a greater extent GH-7856
* storage/raft: Fix a potential deadlock that could occur on leadership transition GH-8547
* storage/raft: Refresh TLS keyring on snapshot restore GH-8546
* storage/etcd: Bumped etcd client API SDK GH-7931 GH-4961 GH-4349 GH-7582
* ui: Make Transit Key actions more prominent GH-8304
* ui: Add Core Usage Metrics GH-8347
* ui: Add refresh Namespace list on the Namespace dropdown, and redesign of Namespace dropdown menu GH-8442
* ui: Update transit actions to codeblocks and automatically encode plaintext unless indicated GH-8462
* ui: Display the results of transit key actions in a modal window GH-8462
* ui: Transit key version styling updates and ability to copy key from dropdown GH-8480

BUG FIXES:

* agent: Fix issue where TLS options are ignored for agent template feature GH-7889
* auth/jwt: Use lower case role names for default_role to match the role case convention GH-100
* auth/ldap: Fix a bug where the UPNDOMAIN parameter was wrongly used to lookup the group membership of the given user GH-6325
* cli: Support autocompletion for nested mounts GH-8303
* cli: Fix CLI namespace autocompletion GH-8315
* identity: Fix incorrect caching of identity token JWKS responses GH-8412
* metrics/stackdriver: Fix issue that prevents the stackdriver metrics library to create unnecessary stackdriver descriptors GH-8073
* replication: Fix issue causing cubbyholes in namespaces on performance secondaries to not work.
* seal (enterprise): Fix seal migration when transactional seal wrap backend is in use.
* secrets/database/influxdb: Fix potential panic if connection to the InfluxDB database cannot be established GH-8282
* secrets/database/mysql: Ensures default static credential rotation statements are used GH-8240
* secrets/database/mysql: Fix inconsistent query parameter names: name or username for different queries. Now it allows for either for backwards compatibility GH-8240
* secrets/database/postgres: Fix inconsistent query parameter names: name or username for different queries. Now it allows for either for backwards compatibility GH-8240
* secrets/pki: Support FQDNs in DNS Name GH-8288
* storage/raft: Allow seal migration to be performed on Vault clusters using raft storage GH-8103
* telemetry: Prometheus requests on standby nodes will now return an error instead of forwarding the request to the active node GH-8280
* ui: Fix broken popup menu on the transit secrets list page GH-8348
* ui: Update headless Chrome flag to fix yarn run test:oss GH-8035
* ui: Update CLI to accept empty strings as param value to reset previously-set values
* ui: Fix bug where error states don't clear when moving between action tabs on Transit GH-8354

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