kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/security/vault/Makefile

31 lines
689 B
Makefile
Raw Normal View History

security/vault: Update to 0.9.5 ## 0.9.5 (February 26th, 2018) IMPROVEMENTS: - auth: Allow sending default_lease_ttl and max_lease_ttl values when enabling auth methods. - secret/database: Add list functionality to `database/config` endpoint - physical/consul: Allow setting a specific service address - replication: When bootstrapping a new secondary, if the initial cluster connection fails, Vault will attempt to roll back state so that bootstrapping can be tried again, rather than having to recreate the downstream cluster. This will still require fetching a new secondary activation token. BUG FIXES: - auth/aws: Update libraries to fix regression verifying PKCS#7 identity documents - listener: Revert to Go 1.9 for now to allow certificates with non-DNS names in their DNS SANs to be used for Vault's TLS connections - replication: Fix issue with a performance secondary/DR primary node losing its DR primary status when performing an update-primary operation - replication: Fix issue where performance secondaries could be unable to automatically connect to a performance primary after that performance primary has been promoted to a DR primary from a DR secondary - ui: Fix behavior when a value contains a `.` ## 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 - cli: Disable color when output is not a TTY - cli: Add `-format` flag to all subcommands - cli: Do not display deprecation warnings when the format is not table - 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. - secret/nomad: Have generated ACL tokens cap out at 64 characters - secret/pki: Country, Locality, Province, Street Address, and Postal Code can now be set on certificates - 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 - secret/pki: Add a flag to make the common name optional on certs - secret/pki: Ensure only DNS-compatible names go into DNS SANs; additionally, properly handle IDNA transformations for these DNS names - secret/ssh: Add `valid-principles` flag to CLI for CA mode - storage/manta: Add Manta storage - ui (Enterprise): Support for ChaCha20-Poly1305 keys in the transit engine. BUG FIXES: - api/renewer: Honor increment value in renew auth calls - 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 - auth/aws-ec2: Avoid masking of role tag response - auth/cert: Verify DNS SANs in the authenticating certificate - auth/okta: Return configured durations as seconds, not nanoseconds - auth/okta: Get all okta groups for a user vs. default 200 limit - 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. - command: Fix interpreted formatting directives when printing raw fields - command: Correctly format output when using -field and -format flags at the same time - command/rekey: Re-add lost `stored-shares` parameter - command/ssh: Create and reuse the api client - command/status: Fix panic when status returns 500 from leadership lookup - identity: Fix race when creating entities - plugin/gRPC: Fixed an issue with list requests and raw responses coming from plugins using gRPC transport - plugin/gRPC: Fix panic when special paths are not set - secret/pki: Verify a name is a valid hostname before adding to DNS SANs - secret/transit: Fix auditing when reading a key after it has been backed up or restored - secret/transit: Fix storage/memory consistency when persistence fails - storage/consul: Validate that service names are RFC 1123 compliant - storage/etcd3: Fix memory ballooning with standby instances - storage/etcd3: Fix large lists (like token loading at startup) not being handled - storage/postgresql: Fix compatibility with versions using custom string version tags - storage/zookeeper: Update vendoring to fix freezing issues - 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
2018-02-27 12:20:42 +01:00
# $NetBSD: Makefile,v 1.22 2018/02/27 11:20:42 fhajny Exp $
Import vault-0.5.2 as security/vault. 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.
2016-05-06 15:35:52 +02:00
security/vault: Update to 0.9.5 ## 0.9.5 (February 26th, 2018) IMPROVEMENTS: - auth: Allow sending default_lease_ttl and max_lease_ttl values when enabling auth methods. - secret/database: Add list functionality to `database/config` endpoint - physical/consul: Allow setting a specific service address - replication: When bootstrapping a new secondary, if the initial cluster connection fails, Vault will attempt to roll back state so that bootstrapping can be tried again, rather than having to recreate the downstream cluster. This will still require fetching a new secondary activation token. BUG FIXES: - auth/aws: Update libraries to fix regression verifying PKCS#7 identity documents - listener: Revert to Go 1.9 for now to allow certificates with non-DNS names in their DNS SANs to be used for Vault's TLS connections - replication: Fix issue with a performance secondary/DR primary node losing its DR primary status when performing an update-primary operation - replication: Fix issue where performance secondaries could be unable to automatically connect to a performance primary after that performance primary has been promoted to a DR primary from a DR secondary - ui: Fix behavior when a value contains a `.` ## 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 - cli: Disable color when output is not a TTY - cli: Add `-format` flag to all subcommands - cli: Do not display deprecation warnings when the format is not table - 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. - secret/nomad: Have generated ACL tokens cap out at 64 characters - secret/pki: Country, Locality, Province, Street Address, and Postal Code can now be set on certificates - 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 - secret/pki: Add a flag to make the common name optional on certs - secret/pki: Ensure only DNS-compatible names go into DNS SANs; additionally, properly handle IDNA transformations for these DNS names - secret/ssh: Add `valid-principles` flag to CLI for CA mode - storage/manta: Add Manta storage - ui (Enterprise): Support for ChaCha20-Poly1305 keys in the transit engine. BUG FIXES: - api/renewer: Honor increment value in renew auth calls - 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 - auth/aws-ec2: Avoid masking of role tag response - auth/cert: Verify DNS SANs in the authenticating certificate - auth/okta: Return configured durations as seconds, not nanoseconds - auth/okta: Get all okta groups for a user vs. default 200 limit - 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. - command: Fix interpreted formatting directives when printing raw fields - command: Correctly format output when using -field and -format flags at the same time - command/rekey: Re-add lost `stored-shares` parameter - command/ssh: Create and reuse the api client - command/status: Fix panic when status returns 500 from leadership lookup - identity: Fix race when creating entities - plugin/gRPC: Fixed an issue with list requests and raw responses coming from plugins using gRPC transport - plugin/gRPC: Fix panic when special paths are not set - secret/pki: Verify a name is a valid hostname before adding to DNS SANs - secret/transit: Fix auditing when reading a key after it has been backed up or restored - secret/transit: Fix storage/memory consistency when persistence fails - storage/consul: Validate that service names are RFC 1123 compliant - storage/etcd3: Fix memory ballooning with standby instances - storage/etcd3: Fix large lists (like token loading at startup) not being handled - storage/postgresql: Fix compatibility with versions using custom string version tags - storage/zookeeper: Update vendoring to fix freezing issues - 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
2018-02-27 12:20:42 +01:00
DISTNAME= vault-0.9.5
Import vault-0.5.2 as security/vault. 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.
2016-05-06 15:35:52 +02:00
CATEGORIES= security
MASTER_SITES= ${MASTER_SITE_GITHUB:=hashicorp/}
MAINTAINER= filip@joyent.com
Follow some redirects.
2017-09-06 11:02:59 +02:00
HOMEPAGE= https://www.vaultproject.io/
Import vault-0.5.2 as security/vault. 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.
2016-05-06 15:35:52 +02:00
COMMENT= Tool for managing secrets
LICENSE= mpl-2.0
GITHUB_TAG= v${PKGVERSION_NOREV}
Update security/vault to 0.7.2. 0.7.2 (May 8th, 2017) BUG FIXES: - audit: Fix auditing entries containing certain kinds of time values 0.7.1 (May 5th, 2017) DEPRECATIONS/CHANGES: - LDAP Auth Backend: Group membership queries will now run as the binddn user when binddn/bindpass are configured, rather than as the authenticating user as was the case previously. FEATURES: - AWS IAM Authentication - MSSQL Physical Backend - Lease Listing and Lookup - TOTP Secret Backend - Database Secret Backend & Secure Plugins (Beta) IMPROVEMENTS: - auth/cert: Support for constraints on subject Common Name and DNS/email Subject Alternate Names in certificates - auth/ldap: Use the binding credentials to search group membership rather than the user credentials - cli/revoke: Add -self option to allow revoking the currently active token - core: Randomize x coordinate in Shamir shares - tidy: Improvements to auth/token/tidy and sys/leases/tidy to handle more cleanup cases - secret/pki: Add no_store option that allows certificates to be issued without being stored. This removes the ability to look up and/or add to a CRL but helps with scaling to very large numbers of certificates. - secret/pki: If used with a role parameter, the sign-verbatim/<role> endpoint honors the values of generate_lease, no_store, ttl and max_ttl from the given role - secret/pki: Add role parameter allow_glob_domains that enables defining names in allowed_domains containing * glob patterns - secret/pki: Update certificate storage to not use characters that are not supported on some filesystems - storage/etcd3: Add discovery_srv option to query for SRV records to find servers - storage/s3: Support max_parallel option to limit concurrent outstanding requests - storage/s3: Use pooled transport for http client - storage/swift: Allow domain values for V3 authentication BUG FIXES: - api: Respect a configured path in Vault's address - auth/aws-ec2: New bounds added as criteria to allow role creation - auth/ldap: Don't lowercase groups attached to users - cli: Don't panic if vault write is used with the force flag but no path - core: Help operations should request forward since standbys may not have appropriate info - replication: Fix enabling secondaries when certain mounts already existed on the primary - secret/mssql: Update mssql driver to support queries with colons - secret/pki: Don't lowercase O/OU values in certs - secret/pki: Don't attempt to validate IP SANs if none are provided
2017-05-10 20:21:27 +02:00
GO_DIST_BASE= ${DISTNAME}
GO_SRCPATH= github.com/hashicorp/vault
Import vault-0.5.2 as security/vault. 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.
2016-05-06 15:35:52 +02:00
USE_TOOLS+= bash gmake
MAKE_ENV+= GOPATH=${WRKDIR}:${PREFIX}/gopkg
INSTALLATION_DIRS+= bin
do-build:
cd ${WRKSRC} && ${SETENV} ${MAKE_ENV} go build -o bin/vault
do-install:
${INSTALL_PROGRAM} ${WRKSRC}/bin/vault ${DESTDIR}${PREFIX}/bin
Update security/vault to 0.7.2. 0.7.2 (May 8th, 2017) BUG FIXES: - audit: Fix auditing entries containing certain kinds of time values 0.7.1 (May 5th, 2017) DEPRECATIONS/CHANGES: - LDAP Auth Backend: Group membership queries will now run as the binddn user when binddn/bindpass are configured, rather than as the authenticating user as was the case previously. FEATURES: - AWS IAM Authentication - MSSQL Physical Backend - Lease Listing and Lookup - TOTP Secret Backend - Database Secret Backend & Secure Plugins (Beta) IMPROVEMENTS: - auth/cert: Support for constraints on subject Common Name and DNS/email Subject Alternate Names in certificates - auth/ldap: Use the binding credentials to search group membership rather than the user credentials - cli/revoke: Add -self option to allow revoking the currently active token - core: Randomize x coordinate in Shamir shares - tidy: Improvements to auth/token/tidy and sys/leases/tidy to handle more cleanup cases - secret/pki: Add no_store option that allows certificates to be issued without being stored. This removes the ability to look up and/or add to a CRL but helps with scaling to very large numbers of certificates. - secret/pki: If used with a role parameter, the sign-verbatim/<role> endpoint honors the values of generate_lease, no_store, ttl and max_ttl from the given role - secret/pki: Add role parameter allow_glob_domains that enables defining names in allowed_domains containing * glob patterns - secret/pki: Update certificate storage to not use characters that are not supported on some filesystems - storage/etcd3: Add discovery_srv option to query for SRV records to find servers - storage/s3: Support max_parallel option to limit concurrent outstanding requests - storage/s3: Use pooled transport for http client - storage/swift: Allow domain values for V3 authentication BUG FIXES: - api: Respect a configured path in Vault's address - auth/aws-ec2: New bounds added as criteria to allow role creation - auth/ldap: Don't lowercase groups attached to users - cli: Don't panic if vault write is used with the force flag but no path - core: Help operations should request forward since standbys may not have appropriate info - replication: Fix enabling secondaries when certain mounts already existed on the primary - secret/mssql: Update mssql driver to support queries with colons - secret/pki: Don't lowercase O/OU values in certs - secret/pki: Don't attempt to validate IP SANs if none are provided
2017-05-10 20:21:27 +02:00
.include "../../lang/go/go-package.mk"
Import vault-0.5.2 as security/vault. 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.
2016-05-06 15:35:52 +02:00
.include "../../mk/bsd.pkg.mk"
Reference in a new issue Copy permalink