From 8241a6971e6051ba10040af6b50f9236faa0c892 Mon Sep 17 00:00:00 2001 From: Noah Kantrowitz Date: Tue, 31 May 2022 18:35:28 -0700 Subject: =?UTF-8?q?=F0=9F=93=9D=20Make=20sure=20the=20phrase=20"constant-t?= =?UTF-8?q?ime=20compare"=20actually=20appears=20in=20the=20docs=20(GH-933?= =?UTF-8?q?96)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit This is purely for SEO as this is the actual generic name for this kind of method and it currently does not appear in a Google search for "python constant time compare". Not creating an issue or setting this up for backports as its trivial (I think) and not a functional change. --- Doc/library/secrets.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Doc/library/secrets.rst b/Doc/library/secrets.rst index c22da72..eda4616 100644 --- a/Doc/library/secrets.rst +++ b/Doc/library/secrets.rst @@ -129,7 +129,7 @@ Other functions .. function:: compare_digest(a, b) Return ``True`` if strings *a* and *b* are equal, otherwise ``False``, - in such a way as to reduce the risk of + using a "constant-time compare" to reduce the risk of `timing attacks `_. See :func:`hmac.compare_digest` for additional details. -- cgit v0.12