From: Junio C Hamano <gitster@pobox.com>
To: "D. Ben Knoble" <ben.knoble@gmail.com>
Cc: git@vger.kernel.org, Mae Eckert <mae.eckert@albellus.de>
Subject: Re: [PATCH] doc: fix shattered.io link
Date: Tue, 06 Oct 2026 14:50:48 -0700 [thread overview]
Message-ID: <xmqq4ieycxc7.fsf@gitster.g> (raw)
In-Reply-To: <89f21a129df21b115d5faded2a74a8a5921d62cf.1791307032.git.ben.knoble@gmail.com> (D. Ben Knoble's message of "Tue, 6 Oct 2026 13:17:19 -0400")
"D. Ben Knoble" <ben.knoble@gmail.com> writes:
> Since we published this document the domain has been taken over and no
> longer reflects the original content. Link to the last good Web Archive
> snapshot so folks can still retrieve the SHAttered information.
>
> Suggested-by: Mae Eckert <mae.eckert@albellus.de>
> Signed-off-by: D. Ben Knoble <ben.knoble@gmail.com>
> ---
> Documentation/technical/hash-function-transition.adoc | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/technical/hash-function-transition.adoc b/Documentation/technical/hash-function-transition.adoc
> index 241d2f763d..f6b38ddd50 100644
> --- a/Documentation/technical/hash-function-transition.adoc
> +++ b/Documentation/technical/hash-function-transition.adoc
> @@ -29,7 +29,8 @@ advantages:
>
> Over time some flaws in SHA-1 have been discovered by security
> researchers. On 23 February 2017 the SHAttered attack
> -(https://shattered.io) demonstrated a practical SHA-1 hash collision.
> +(https://web.archive.org/web/20260207211148/https://shattered.io/)
> +demonstrated a practical SHA-1 hash collision.
Thanks. Will queue.
>
> Git v2.13.0 and later subsequently moved to a hardened SHA-1
> implementation by default, which isn't vulnerable to the SHAttered
prev parent reply other threads:[~2026-10-06 21:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-06 14:49 Hash function transition page links to hijacked domain Mae Eckert
2026-10-06 17:17 ` [PATCH] doc: fix shattered.io link D. Ben Knoble
2026-10-06 21:50 ` Junio C Hamano [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq4ieycxc7.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=ben.knoble@gmail.com \
--cc=git@vger.kernel.org \
--cc=mae.eckert@albellus.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox