github
/
certd
mirror of https://github.com/certd/certd
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
certd/packages/core/acme-client/CHANGELOG.md

8.4 KiB
Raw Blame History

Change Log

All notable changes to this project will be documented in this file. See Conventional Commits for commit guidelines.

1.0.6 (2023-05-25)

Note: Version bump only for package @certd/acme-client

1.0.5 (2023-05-25)

Note: Version bump only for package @certd/acme-client

1.0.4 (2023-05-25)

Note: Version bump only for package @certd/acme-client

1.0.3 (2023-05-25)

Note: Version bump only for package @certd/acme-client

1.0.2 (2023-05-24)

Note: Version bump only for package @certd/acme-client

1.0.1 (2023-05-24)

Note: Version bump only for package @certd/acme-client

Changelog

Important upgrade notice

On September 15, 2022, Let's Encrypt will stop accepting Certificate Signing Requests signed using the obsolete SHA-1 hash. This change affects all acme-client versions lower than 3.3.2 and 4.2.4. Please upgrade ASAP to ensure that your certificates can still be issued following this date.

A more detailed explanation can be found at the Let's Encrypt forums.

v5.0.0 (2022-07-28)

  • Upgrade guide here
  • added New native crypto interface, ECC/ECDSA support
  • breaking Remove support for Node v10, v12 and v14
  • breaking Prioritize issuer closest to root during preferred chain selection - #46
  • changed Replace bluebird dependency with native promise APIs
  • changed Replace backo2 dependency with internal utility

v4.2.5 (2022-03-21)

4.2.4 (2022-03-19)

  • fixed Use SHA-256 when signing CSRs

v3.3.2 (2022-03-19)

  • backport Use SHA-256 when signing CSRs

v4.2.3 (2022-01-11)

  • added Directory URLs for ACME providers Buypass and ZeroSSL
  • fixed Skip already valid authorizations when using client.auto()

v4.2.2 (2022-01-10)

  • fixed Upgrade node-forge@1.2.0

v4.2.1 (2022-01-10)

  • fixed ZeroSSL duplicate_domains_in_array error when using client.auto()

v4.2.0 (2022-01-06)

  • added Support for external account binding - RFC 8555 Section 7.3.4
  • added Ability to pass through custom logger function
  • changed Increase default backoffAttempts to 10
  • fixed Deactivate authorizations where challenges can not be completed
  • fixed Attempt authoritative name servers when verifying dns-01 challenges
  • fixed Error verbosity when failing to read ACME directory
  • fixed Correctly recognize ready and processing states - RFC 8555 Section 7.1.6

v4.1.4 (2021-12-23)

v4.1.3 (2021-02-22)

v4.1.2 (2020-11-16)

  • fixed Bug when encoding PEM payloads, potentially causing malformed requests

v4.1.1 (2020-11-13)

  • fixed Missing TypeScript definitions

v4.1.0 (2020-11-12)

  • added Option preferredChain added to client.getCertificate() and client.auto() to indicate which certificate chain is preferred if a CA offers multiple
  • added Method client.getOrder() to refresh order from CA
  • fixed Upgrade axios@0.21.0
  • fixed Error when attempting to revoke a certificate chain
  • fixed Missing URL augmentation in client.finalizeOrder() and client.deactivateAuthorization()
  • fixed Add certificate issuer to response from forge.readCertificateInfo()

v4.0.2 (2020-10-09)

v4.0.1 (2020-09-15)

v4.0.0 (2020-05-29)

  • breaking Remove support for Node v8
  • breaking Remove deprecated openssl crypto module
  • fixed Incorrect TypeScript CertificateInfo definitions
  • fixed Allow trailing whitespace character in http-01 challenge response

v3.3.1 (2020-01-07)

  • fixed Improvements to TypeScript definitions

v3.3.0 (2019-12-19)

v3.2.1 (2019-11-14)

  • added New option skipChallengeVerification added to client.auto() to bypass internal challenge verification

v3.2.0 (2019-08-26)

  • added More extensive testing using letsencrypt/pebble
  • changed When creating a CSR, commonName no longer defaults to 'localhost'
    • This change is not considered breaking since commonName: 'localhost' will result in an error when ordering a certificate
  • fixed Retry signed API requests on urn:ietf:params:acme:error:badNonce - RFC 8555 Section 6.5
  • fixed Minor bugs related to POST-as-GET when calling updateAccount()
  • fixed Ensure subject common name is present in SAN when creating a CSR - CAB v1.2.3 Section 9.2.2
  • fixed Send empty JSON body when responding to challenges - RFC 8555 Section 7.5.1

v2.3.1 (2019-08-26)

  • backport Minor bugs related to POST-as-GET when calling client.updateAccount()
  • backport Send empty JSON body when responding to challenges

v3.1.0 (2019-08-21)

  • added UTF-8 support when generating a CSR subject using forge - RFC 5280
  • fixed Implement POST-as-GET for all ACME API requests - RFC 8555 Section 6.3

v2.3.0 (2019-08-21)

  • backport Implement POST-as-GET for all ACME API requests

v3.0.0 (2019-07-13)

  • added Expose axios instance to allow manipulating HTTP client defaults
  • breaking Remove support for Node v4 and v6
  • breaking Remove Babel transpilation

v2.2.3 (2019-01-25)

  • added DNS CNAME detection when verifying dns-01 challenges

v2.2.2 (2019-01-07)

  • added Support for tls-alpn-01 challenge key authorization

v2.2.1 (2019-01-04)

  • fixed Handle and throw errors from OpenSSL process

v2.2.0 (2018-11-06)

  • added New node-forge crypto interface, removes OpenSSL CLI dependency
  • added Support native crypto.generateKeyPair() API when generating key pairs

v2.1.0 (2018-10-21)

  • added Ability to set and get current account URL
  • fixed Replace HTTP client request with axios
  • fixed Auto-mode no longer tries to create account when account URL exists

v2.0.1 (2018-08-17)

v2.0.0 (2018-04-02)

  • breaking ACMEv2
  • breaking API changes
  • breaking Rewrite to ES6
  • breaking Promises instead of callbacks

v1.0.0 (2017-10-20)

  • API stable

v0.2.1 (2017-09-27)

  • fixed Bug causing invalid anti-replay nonce

v0.2.0 (2017-09-21)

  • breaking OpenSSL method readCsrDomains and readCertificateInfo now return domains as an object
  • fixed Added and fixed some tests

v0.1.0 (2017-09-14)

  • acme-client released