Downloads:

43,246

Downloads of v 1.3.0:

393

Last Update:

11 Dec 2019

Package Maintainer(s):

Software Author(s):

  • Mitchell Hashimoto
  • HashiCorp

Tags:

vault hashicorp

Vault

This is not the latest version of Vault available.

1.3.0 | Updated: 11 Dec 2019

Downloads:

43,246

Downloads of v 1.3.0:

393

Maintainer(s):

Software Author(s):

  • Mitchell Hashimoto
  • HashiCorp

Vault 1.3.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.3.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.3.0'
  source   'STEP 3 URL'
end

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


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

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


package { 'vault':
  provider => 'chocolatey',
  ensure   => '1.3.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.3.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 11 Dec 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            = 'e66e17bb9b524c839f8e32018d0c812a75a8a6cb15506ea7f14dced2bd8db47e'
  ChecksumType        = 'sha256'
  Checksum64          = '153c608f5acfdf2a5b9f52c4b45aed4d194074a0598b2a2804a4ac75641516ab'
  version             = '1.3.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 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

1.3 (November 14th, 2019)

CHANGES:

* Secondary cluster activation: There has been a change to the way that activating
performance and DR secondary clusters works when using public keys for
encryption of the parameters rather than a wrapping token. This flow was
experimental and never documented. It is now officially supported and
documented but is not backwards compatible with older Vault releases.
* Cluster cipher suites: On its cluster port, Vault will no longer advertise
the full TLS 1.2 cipher suite list by default. Although this port is only
used for Vault-to-Vault communication and would always pick a strong cipher,
it could cause false flags on port scanners and other security utilities
that assumed insecure ciphers were being used. The previous behavior can be
achieved by setting the value of the (undocumented) cluster_cipher_suites
config flag to tls12.

FEATURES:

* Vault Debug: A new top-level subcommand, debug, is added that allows
operators to retrieve debugging information related to a particular Vault
node. Operators can use this simple workflow to capture triaging information,
which can then be consumed programmatically or by support and engineering teams.
It has the abilitity to probe for config, host, metrics, pprof, server status,
and replication status.
* Recovery Mode: Vault server can be brought up in recovery mode to resolve
outages caused due to data store being in bad state. This is a privileged mode
that allows sys/raw API calls to perform surgical corrections to the data
store. Bad storage state can be caused by bugs. However, this is usually
observed when known (and fixed) bugs are hit by older versions of Vault.
* Entropy Augmentation (Enterprise): Vault now supports sourcing entropy from
external source for critical security parameters. Currently an HSM that
supports PKCS#11 is the only supported source.
* Active Directory Secret Check-In/Check-Out: In the Active Directory secrets
engine, users or applications can check out a service account for use, and its
password will be rotated when it's checked back in.
* Vault Agent Template: Vault Agent now supports rendering templates containing
Vault secrets to disk, similar to Consul Template [GH-7652]
* Transit Key Type Support: Signing and verification is now supported with the P-384
(secp384r1) and P-521 (secp521r1) ECDSA curves [GH-7551] and encryption and
decryption is now supported via AES128-GCM96 [GH-7555]
* SSRF Protection for Vault Agent: Vault Agent has a configuration option to
require a specific header before allowing requests [GH-7627]
* AWS Auth Method Root Rotation: The credential used by the AWS auth method can
now be rotated, to ensure that only Vault knows the credentials it is using [GH-7131]
* New UI Features: The UI now supports managing users and groups for the
Userpass, Cert, Okta, and Radius auth methods.
* Shamir with Stored Master Key: The on disk format for Shamir seals has changed,
allowing for a secondary cluster using Shamir downstream from a primary cluster
using Auto Unseal. [GH-7694]
* Stackdriver Metrics Sink: Vault can now send metrics to
Stackdriver. See the configuration
documentation
for
details. [GH-6957]
* Filtered Paths Replication (Enterprise): Based on the predecessor Filtered Mount Replication,
Filtered Paths Replication allows now filtering of namespaces in addition to mounts.
* Token Renewal via Accessor: Tokens can now be renewed via the accessor value through
the new auth/token/renew-accessor endpoint if the caller's token has
permission to access that endpoint.
* Improved Integrated Storage (Beta): Improved raft write performance, added support for
non-voter nodes, along with UI support for: using raft storage, joining a raft cluster,
and downloading and restoring a snapshot.

IMPROVEMENTS:

* agent: Add ability to set the TLS SNI name used by Agent [GH-7519]
* auth/jwt: The redirect callback host may now be specified for CLI logins
[JWT-71]
* auth/jwt: Bound claims may now contain boolean values [JWT-73]
* auth/jwt: CLI logins can now open the browser when running in WSL [JWT-77]
* core: Exit ScanView if context has been cancelled [GH-7419]
* core: re-encrypt barrier and recovery keys if the unseal key is updated
[GH-7493]
* core: Don't advertise the full set of TLS 1.2 cipher suites on the cluster
port, even though only strong ciphers were used [GH-7487]
* core (enterprise): Add background seal re-wrap
* core/metrics: Add config parameter to allow unauthenticated sys/metrics
access. [GH-7550]
* metrics: Upgrade DataDog library to improve performance [GH-7794]
* replication (enterprise): Write-Ahead-Log entries will not duplicate the
data belonging to the encompassing physical entries of the transaction,
thereby improving the performance and storage capacity.
* replication (enterprise): Added more replication metrics
* replication (enterprise): Reindex process now compares subpages for a more
accurate indexing process.
* replication (enterprise): Reindex API now accepts a new skip_flush parameter
indicating all the changes should not be flushed while the tree is locked.
* secrets/aws: The root config can now be read [GH-7245]
* secrets/aws: Role paths may now contain the '@' character [GH-7553]
* secrets/database/cassandra: Add ability to skip verfication of connection [GH-7614]
* secrets/gcp: Fix panic during rollback if the roleset has been deleted [GCP-52]
* storage/azure: Add config parameter to Azure storage backend to allow
specifying the ARM endpoint [GH-7567]
* storage/cassandra: Improve storage efficiency by eliminating unnecessary
copies of value data [GH-7199]
* storage/raft: Improve raft write performance by utilizing FSM Batching [GH-7527]
* storage/raft: Add support for non-voter nodes [GH-7634]
* sys: Add a new sys/host-info endpoint for querying information about
the host [GH-7330]
* sys: Add a new set of endpoints under sys/pprof/ that allows profiling
information to be extracted [GH-7473]
* sys: Add endpoint that counts the total number of active identity entities [GH-7541]
* sys: sys/seal-status now has a storage_type field denoting what type of storage
the cluster is configured to use
* sys: Add a new sys/internal/counters/tokens endpoint, that counts the
total number of active service token accessors in the shared token storage.
[GH-7541]
* sys/config: Add a new endpoint under sys/config/state/sanitized that
returns the configuration state of the server. It excludes config values
from storage, ha_storage, and seal stanzas and some values
from telemetry due to potential sensitive entries in those fields.
* ui: when using raft storage, you can now join a raft cluster, download a
snapshot, and restore a snapshot from the UI [GH-7410]
* ui: clarify when secret version is deleted in the secret version history dropdown [GH-7714]

BUG FIXES:

* agent: Fix a data race on the token value for inmemsink [GH-7707]
* api: Fix Go API using lease revocation via URL instead of body [GH-7777]
* api: Allow setting a function to control retry behavior [GH-7331]
* auth/gcp: Fix a bug where region information in instance groups names could
cause an authorization attempt to fail [GCP-74]
* cli: Fix a bug where a token of an unknown format (e.g. in ~/.vault-token)
could cause confusing error messages during vault login [GH-7508]
* cli: Fix a bug where the namespace list command with JSON formatting
always returned an empty object [GH-7705]
* cli: Command timeouts are now always specified solely by the
VAULT_CLIENT_TIMEOUT value. [GH-7469]
* core: Don't allow registering a non-root zero TTL token lease. This is purely
defense in depth as the lease would be revoked immediately anyways, but
there's no real reason to allow registration. [GH-7524]
* core: Correctly revoke the token that's present in the response auth from a
auth/token/ request if there's partial failure during the process. [GH-7835]
* identity (enterprise): Fixed identity case sensitive loading in secondary
cluster [GH-7327]
* identity: Ensure only replication primary stores the identity case sensitivity state [GH-7820]
* raft: Fixed VAULT_CLUSTER_ADDR env being ignored at startup [GH-7619]
* secrets/pki: Don't allow duplicate SAN names in issued certs [GH-7605]
* sys/health: Pay attention to the values provided for standbyok and
perfstandbyok rather than simply using their presence as a key to flip on
that behavior [GH-7323]
* ui: using the wrapped_token query param will work with redirect_to and
will automatically log in as intended [GH-7398]
* ui: fix an error when initializing from the UI using PGP keys [GH-7542]
* ui: show all active kv v2 secret versions even when delete_version_after is configured [GH-7685]
* ui: Ensure that items in the top navigation link to pages that users have access to [GH-7590]

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