From ab04fcb33356262f1ab582be5c2005066f20c6f9 Mon Sep 17 00:00:00 2001 From: Eduard Bagdasaryan Date: Wed, 1 Feb 2023 19:25:10 +0000 Subject: [PATCH] Remove broken -sha1 option from server_cert_fingerprint (#1249) server_cert_fingerprint support for the sha1 parameter has been broken for years, probably since its inception (2012 commit 42d3334). The bug was known since at least 2018 when it was mentioned in Bug 4847 discussion. The single-dash syntax violates the double-dash pattern used for other --long ACL options. If fixed, using the option would not change Squid behavior because SHA1 is the default (and the only supported) fingerprinting algorithm. The option was meant to allow admins to be explicit about that default in case it changes in the future, but implementation bugs derailed that plan. The fix is not straightforward, and we should be focusing on more important things. --- doc/release-notes/release-6.sgml | 3 ++- src/AclRegs.cc | 2 +- src/cf.data.pre | 5 ++--- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/doc/release-notes/release-6.sgml b/doc/release-notes/release-6.sgml index 6ca8b0f086..e043936fc3 100644 --- a/doc/release-notes/release-6.sgml +++ b/doc/release-notes/release-6.sgml @@ -63,7 +63,8 @@ This section gives an account of those changes in three categories: Changes to existing directives