You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: CHANGELOG.md
+59-5
Original file line number
Diff line number
Diff line change
@@ -4,16 +4,70 @@ All notable changes to this project will be documented in this file.
4
4
The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/)
5
5
and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.html).
6
6
7
-
## [Unreleased - 0.18.3] - DATE
7
+
### TEMPLATE -- do not alter or remove
8
+
---
9
+
## [x.y.z] - aaaa-bb-cc
8
10
### Added
9
-
- Added support for renew after expiry using the claim `allowRenewAfterExpiry`.
11
+
### Changed
12
+
### Deprecated
13
+
### Removed
14
+
### Fixed
15
+
### Security
16
+
---
17
+
18
+
## [Unreleased]
19
+
### Changed
20
+
- Certificates signed by an issuer using an RSA key will be signed using the same algorithm as the issuer certificate was signed with. The signature will no longer default to PKCS #1. For example, if the issuer certificate was signed using RSA-PSS with SHA-256, a new certificate will also be signed using RSA-PSS with SHA-256.
21
+
22
+
## [0.20.0] - 2022-05-26
23
+
### Added
24
+
- Added Kubernetes auth method for Vault RAs.
25
+
- Added support for reporting provisioners to linkedca.
26
+
- Added support for certificate policies on authority level.
27
+
- Added a Dockerfile with a step-ca build with HSM support.
28
+
- A few new WithXX methods for instantiating authorities
29
+
### Changed
30
+
- Context usage in HTTP APIs.
31
+
- Changed authentication for Vault RAs.
32
+
- Error message returned to client when authenticating with expired certificate.
33
+
- Strip padding from ACME CSRs.
34
+
### Deprecated
35
+
- HTTP API handler types.
36
+
### Fixed
37
+
- Fixed SSH revocation.
38
+
- CA client dial context for js/wasm target.
39
+
- Incomplete `extraNames` support in templates.
40
+
- SCEP GET request support.
41
+
- Large SCEP request handling.
42
+
43
+
## [0.19.0] - 2022-04-19
44
+
### Added
45
+
- Added support for certificate renewals after expiry using the claim `allowRenewalAfterExpiry`.
10
46
- Added support for `extraNames` in X.509 templates.
47
+
- Added `armv5` builds.
48
+
- Added RA support using a Vault instance as the CA.
49
+
- Added `WithX509SignerFunc` authority option.
50
+
- Added a new `/roots.pem` endpoint to download the CA roots in PEM format.
51
+
- Added support for Azure `Managed Identity` tokens.
52
+
- Added support for automatic configuration of linked RAs.
53
+
- Added support for the `--context` flag. It's now possible to start the
54
+
CA with `step-ca --context=abc` to use the configuration from context `abc`.
55
+
When a context has been configured and no configuration file is provided
56
+
on startup, the configuration for the current context is used.
57
+
- Added startup info logging and option to skip it (`--quiet`).
58
+
- Added support for renaming the CA (Common Name).
11
59
### Changed
12
-
- Made SCEP CA URL paths dynamic
13
-
- Support two latest versions of Go (1.17, 1.18)
60
+
- Made SCEP CA URL paths dynamic.
61
+
- Support two latest versions of Go (1.17, 1.18).
62
+
- Upgrade go.step.sm/crypto to v0.16.1.
63
+
- Upgrade go.step.sm/linkedca to v0.15.0.
14
64
### Deprecated
65
+
- Go 1.16 support.
15
66
### Removed
16
67
### Fixed
68
+
- Fixed admin credentials on RAs.
69
+
- Fixed ACME HTTP-01 challenges for IPv6 identifiers.
70
+
- Various improvements under the hood.
17
71
### Security
18
72
19
73
## [0.18.2] - 2022-03-01
@@ -49,7 +103,7 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.
49
103
- Support for multiple certificate authority contexts.
50
104
- Support for generating extractable keys and certificates on a pkcs#11 module.
51
105
### Changed
52
-
- Support two latest versions of golang (1.16, 1.17)
Copy file name to clipboardexpand all lines: README.md
+2-1
Original file line number
Diff line number
Diff line change
@@ -54,7 +54,7 @@ Setting up a *public key infrastructure* (PKI) is out of reach for many small te
54
54
-[Short-lived certificates](https://smallstep.com/blog/passive-revocation.html) with automated enrollment, renewal, and passive revocation
55
55
- Capable of high availability (HA) deployment using [root federation](https://smallstep.com/blog/step-v0.8.3-federation-root-rotation.html) and/or multiple intermediaries
56
56
- Can operate as [an online intermediate CA for an existing root CA](https://smallstep.com/docs/tutorials/intermediate-ca-new-ca)
57
-
-[Badger, BoltDB, and MySQL database backends](https://smallstep.com/docs/step-ca/configuration#databases)
57
+
-[Badger, BoltDB, Postgres, and MySQL database backends](https://smallstep.com/docs/step-ca/configuration#databases)
58
58
59
59
### ⚙️ Many ways to automate
60
60
@@ -68,6 +68,7 @@ You can issue certificates in exchange for:
68
68
-[Cloud instance identity documents](https://smallstep.com/blog/embarrassingly-easy-certificates-on-aws-azure-gcp/), for VMs on AWS, GCP, and Azure
69
69
-[Single-use, short-lived JWK tokens](https://smallstep.com/docs/step-ca/provisioners#jwk) issued by your CD tool — Puppet, Chef, Ansible, Terraform, etc.
70
70
- A trusted X.509 certificate (X5C provisioner)
71
+
- A host certificate from your Nebula network
71
72
- A SCEP challenge (SCEP provisioner)
72
73
- An SSH host certificates needing renewal (the SSHPOP provisioner)
73
74
- Learn more in our [provisioner documentation](https://smallstep.com/docs/step-ca/provisioners)
0 commit comments