Hey guys, I am new to Certbot and was wondering why it always uses SHA1 to check certificates instead of a more secure algorithm. source code I know it has better compatibility. However, is it feasible to add sha256(or other algorithm) support? Also found a similar history commit. Remove use of s…

I believe Let's Encrypt (and other CAs) are implementing the so called lightweight OCSP profile from RFC 5019 . Thus Certbot is "limited" by what OCSP profiles are implemented by CAs. The usage of SHA1 with regard to Let's Encrypt has been discussed earlier, see OCSP Responder support for SHA2 hashe…

Sha256(or other algorithm) support for certbot ocsp validation

Feature Requests

system Closed May 1, 2024, 5:16pm 6

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

Topic		Replies	Views
OCSP Responder support for SHA2 hashes in CertID Issuance Tech	3	1418	November 17, 2021
Certbot 2.11.1 point release Client dev	6	142	April 3, 2025
Certbot Version 0.7.0	0	2018	May 27, 2016
OCSP Responder ‘unauthorized’ error Help	3	5249	January 2, 2021
Certbot 1.25.0 Release Client dev	3	1028	April 17, 2022

Sha256(or other algorithm) support for certbot ocsp validation

Related topics