Downloads:

31,596

Downloads of v 1.5.0:

764

Last Update:

22 Jul 2020

Package Maintainer(s):

Software Author(s):

  • Mitchell Hashimoto
  • HashiCorp

Tags:

vault hashicorp

Vault

1.5.0 | Updated: 22 Jul 2020

Downloads:

31,596

Downloads of v 1.5.0:

764

Maintainer(s):

Software Author(s):

  • Mitchell Hashimoto
  • HashiCorp

Vault 1.5.0

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

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


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

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


package { 'vault':
  provider => 'chocolatey',
  ensure   => '1.5.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.5.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 22 Jul 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            = 'dbaefb222f9e69303a95230d5ae4d5eb2a845aeb4a281d00d971f68849dba318'
  ChecksumType        = 'sha256'
  Checksum64          = 'e870752221027a23c44302b4ab98ef0fd0435f78a901c22d85c6f43429f0047f'
  version             = '1.5.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.4.3 748 Friday, July 3, 2020 Approved
Vault 1.4.1 1588 Monday, May 4, 2020 Approved
Vault 1.4.0 1105 Thursday, April 9, 2020 Approved
Vault 1.3.4 111 Wednesday, April 8, 2020 Approved
Vault 1.3.3 763 Monday, March 9, 2020 Approved
Vault 1.3.2 1320 Friday, January 24, 2020 Approved
Vault 1.3.1 1420 Friday, December 20, 2019 Approved
Vault 1.3.0 344 Wednesday, December 11, 2019 Approved
Vault 1.2.4 908 Tuesday, November 12, 2019 Approved

1.5.0

### July 21st, 2020

CHANGES:

* audit: Token TTL and issue time are now provided in the auth portion of audit logs.
* auth/gcp: Changes the default name of the entity alias that gets created to be the role ID for both IAM and GCE authentication.
* core: Remove the addition of newlines to parsed configuration when using integer/boolean values
* cubbyhole: Reject reads and writes to an empty ("") path.
* storage/gcs: The credentials_file config option has been removed. The GOOGLE_APPLICATION_CREDENTIALS environment variable or default credentials may be used instead
* storage/raft: The storage configuration now accepts a new max_entry_size config that will limit the total size in bytes of any entry committed via raft. It defaults to "1048576" (1MiB).
* token: Token creation with custom token ID via id will no longer allow periods (.) as part of the input string. The final generated token value may contain periods, such as the s. prefix for service token indication.
* token: Token renewals will now return token policies within the token_policies , identity policies within identity_policies, and the full policy set within policies.

IMPROVEMENTS:

* audit: Replication status requests are no longer audited.
* audit: Added mount_type field to requests and responses.
* auth/aws: Add support for Web Identity credentials
* auth/jwt: Support users that are members of more than 200 groups on Azure
* auth/kerberos: Support identities without userPrincipalName
* auth/kubernetes: Allow disabling iss validation
* auth/kubernetes: Try reading the ca.crt and TokenReviewer JWT from the default service account
* cli: Support reading TLS parameters from file for the vault operator raft join command.
* cli: Add a new subcommand, vault monitor, for tailing server logs in the console.
* core: Add the Go version used to build a Vault binary to the server message output.
* core: Added Password Policies for user-configurable password generation
* core: New telemetry metrics covering token counts, token creation, KV secret counts, lease creation.
* physical/gcs: The storage backend now uses a dedicated client for HA lock updates to prevent lock table update failures when flooded by other client requests.
* physical/spanner: The storage backend now uses a dedicated client for HA lock updates to prevent lock table update failures when flooded by other client requests.
* plugin: Add SDK method, Sys.ReloadPlugin, and CLI command, vault plugin reload, for reloading plugins.
* plugin (enterprise): Add a scope field to plugin reload, which when global, reloads the plugin anywhere in a cluster.
* sdk/framework: Support accepting TypeFloat parameters over the API
* secrets/aws: Add iam_groups parameter to role create/update
* secrets/database: Add static role rotation for MongoDB Atlas database plugin
* secrets/database: Add static role rotation for MSSQL database plugin
* secrets/database: Allow InfluxDB to use insecure TLS without cert bundle
* secrets/gcp: Support BigQuery dataset ACLs in absence of IAM endpoints
* secrets/pki: Allow 3072-bit RSA keys
* secrets/ssh: Add a CA-mode role option to specify signing algorithm
* secrets/ssh: The Vault SSH Helper can now be configured to reference a mount in a namespace
* secrets/transit: Transit requests that make use of keys now include a new field key_version in their responses
* secrets/transit: Improving transit batch encrypt and decrypt latencies
* sentinel: Add a sentinel config section, and "additional_enabled_modules", a list of Sentinel modules that may be imported in addition to the defaults.
* ui: Update TTL picker styling on SSH secret engine
* ui: Only render the JWT input field of the Vault login form on mounts configured for JWT auth
* ui: Add replication dashboards. Improve replication management workflows.
* ui: Update alert banners to match design systems black text.

BUG FIXES:

* auth/oci: Fix issue where users of the Oracle Cloud Infrastructure (OCI) auth method could not authenticate when the plugin backend was mounted at a non-default path.
* core: Extend replicated cubbyhole fix in 1.4.0 to cover case where a performance primary is also a DR primary
* seal/awskms: fix AWS KMS auto-unseal when AWS_ROLE_SESSION_NAME not set
* sentinel: fix panic due to concurrent map access when rules iterate over metadata maps
* secrets/aws: Fix issue where performance standbys weren't able to generate STS credentials after an IAM access key rotation in AWS and root IAM credential update in Vault
* secrets/database: Fix issue where rotating root database credentials while Vault's storage backend is unavailable causes Vault to lose access to the database
* secrets/database: Fix issue that prevents performance standbys from connecting to databases after a root credential rotation
* secrets/gcp: Fix issue were updates were not being applied to the token_scopes of a roleset.
* secrets/kv: Return the value of delete_version_after when reading kv/config, even if it is set to the default.
* ui: Add Toggle component into core addon so it is available in KMIP and other Ember Engines.
* ui: Disallow max versions value of large than 9999999999999999 on kv2 secrets engine.
* ui: Add and upgrade missing dependencies to resolve a failure with make static-dist.

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