packages feed

x509-ocsp 0.5.2.1 → 0.5.2.2

raw patch · 3 files changed

+9/−3 lines, 3 filesPVP ok

version bump matches the API change (PVP)

API changes (from Hackage documentation)

Files

Changelog.md view
@@ -1,3 +1,9 @@+### 0.5.2.2++- Update README.md after switching the failed reason in function+  *validateWithOCSPReq* in the *client-ocsp* example from *CacheSaysNo* to+  *OtherReason*.+ ### 0.5.2.1  - Obtain signatures indirectly, via *bitArrayGetData*.
README.md view
@@ -4,7 +4,7 @@ [![Build Status](https://github.com/lyokha/x509-ocsp/workflows/CI/badge.svg)](https://github.com/lyokha/x509-ocsp/actions?query=workflow%3ACI) [![Hackage](https://img.shields.io/hackage/v/x509-ocsp.svg?label=hackage%20%7C%20x509-ocsp&logo=haskell&logoColor=%239580D1)](https://hackage.haskell.org/package/x509-ocsp) -This module helps building OCSP requests and parse OCSP responses in Haskell.+This module helps build OCSP requests and parse OCSP responses in Haskell.  There are many scenarios of OCSP use. One of the simplest practical use cases for clients is sending OCSP requests to the OCSP responder upon validation of@@ -82,7 +82,7 @@   requestVersion       = HTTP/1.1   proxySecureMode      = ProxySecureWithConnect }- (InternalException (HandshakeFailed (Error_Protocol "certificate rejected: [CacheSaysNo \"OCSP: bad certificate status OCSPRespCertRevoked\"]" CertificateUnknown)))+ (InternalException (HandshakeFailed (Error_Protocol "certificate rejected: [OtherReason \"OCSP: bad certificate status OCSPRespCertRevoked\"]; ..." CertificateUnknown))) ```   The certificate has been revoked and the handshake fails.
x509-ocsp.cabal view
@@ -1,7 +1,7 @@ cabal-version:          2.4  name:                   x509-ocsp-version:                0.5.2.1+version:                0.5.2.2 synopsis:               Basic X509 OCSP implementation description:            Build X509 OCSP requests and parse responses homepage:               https://github.com/lyokha/x509-ocsp