Git 3.0 is coming. Are your tools ready? 🛡️

In our latest SmartGit Preview 26.1.011, we’ve officially introduced #Git 3.0 compatibility, targeting the 2 biggest architectural changes:

✅ SHA-256 Support: Moving beyond SHA-1 to ensure long-term cryptographic security and collision resistance.

✅ Reftable Support: A new storage format for refs that solves the "thousands of branches" performance bottleneck. No more scanning thousands of tiny files in .git/refs.

#Git3 #SmartGit #DevOps #SHA256

1/2 Exciting news: we just published a new paper: "Preimage attacks on round-reduced MD5, SHA-1, and SHA-256 using parameterized SAT solver", by Oleg Zaikin

If you are interested in security, cryptology, or Constraint Programming, definitely give this paper a read!

https://link.springer.com/article/10.1007/s10601-025-09383-0

#ConstraintProgramming #Security #Cryptology #Cryptography #CryptographicHashFunctions #ConflictDrivenClauseLearning #BooleanSatisfiability #MD5 #SHA1 #SHA256

Git 3.0: Major Changes Ahead | Ron Northcutt posted on the topic | LinkedIn

Git 3.0 is on the horizon, and it is bringing some of the biggest changes we have seen in a decade. I recently followed a deep dive into the future of Git based on Patrick Steinhardt’s session at FOSDEM 2026. The focus is shifting from just maintaining the tool to evolving it for massive scale and better developer experience. Git 3.0 is about making the tool more robust for the next ten years of software development. Author: ennael Source: OSSFlow Link in the comments

Thanks to @Monorepo for doing most of this, which needed changes to both the release process and the website: releases since 13th January now show SHA-256 checksums instead of MD5!

https://www.python.org/downloads/release/python-3150a4/

#Python #SHA256 #MD5

Release of hshwd

hshwd is an open-source offline tool that generates strong, unique passwords from weak ones in a deterministic way, using the properties of hash functions.

https://ailyaut.com/blog/hshwd_release.html

#password #hshwd #hash #sha256 #rust #godot #godotengine #python #cryptography #opensource

Moxxy becomes expressive – Ailyaut's blog

A lot has happened since I last worked on Moxxy, the most important for us today being the release of Material 3 Expressive. I personally love the direction Google is taking by making the UI fun for users (and designers!) while still focusing on and improving ease of use and readability.

[Перевод] Пишем свой git: минимальная реализация на Rust

Контроль версий долгое время был для меня «чёрным ящиком»: я не понимал, как именно хранятся файлы, как формируются diff’ы и из чего состоят коммиты. А поскольку я люблю изобретать велосипеды, почему бы не попробовать реализовать git самому?

https://habr.com/ru/companies/cloud4y/articles/990052/

#git #rust #контроль_версий #sha256 #zstd #хеширование #petproject #системы_контроля_версий #объекты_git #commit

Пишем свой git: минимальная реализация на Rust

Контроль версий долгое время был для меня «чёрным ящиком»: я не понимал, как именно хранятся файлы, как формируются diff’ы и из чего состоят коммиты. А поскольку я люблю изобретать велосипеды, почему...

Хабр

My #2026 resolution was field-testing sha256 git repos and I converted one of my minor projects, but since Github only supports sha1 I've moved the repository to codeberg:

https://codeberg.org/kpcyrd/ssh-keyonly

Everything else worked well. I'm also mirroring the repo to Arch Linux' Gitlab. Gitlab's UI didn't support creating sha256 repos, but this can be bypassed through the "import repository" feature.

I've used this guide, which was very helpful: https://cybrkyd.com/post/how-to-convert-a-sha1-git-repository-to-sha256/

#git #sha256 #sha1 #rust #codeberg

ssh-keyonly

Audit an ssh server for supported authentication methods

Codeberg.org
Running a GitLab CI/CD Pipeline in a fork of a Git SHA256 project does not work - surprised nobody ran into this before #gitlab #git #sha256 https://gitlab.com/gitlab-org/gitlab/-/issues/584941
CI failure in SHA256 Git fork: fatal: mismatched algorithms: client sha1; server sha256 (#584941) · Issues · GitLab.org / GitLab · GitLab

Hi! I get the following error directly when running a pipeline in a fork of Git SHA256 project, after making the first commit: https://gitlab.com/debdistutils/tacos/build-containers/-/jobs/12588541074...

GitLab
13326eac626097fef815ef00c5840a52df5820067dd31c1842f07882c8282696
#sha256