Daniel Rudolf

> This looks like a shallow clone use real git It indeed is. However, just to make this clear, I'm absolutely fine with this failing and requiring manual intervention. I...

Thanks for merging the PRs Thomas :+1: I just updated the issue title and original text to also reflect the findings in `parse_version()`.

> There is currently only 1 byte that encodes all this information in the repository. And that byte selects the "cipher suite" with the corresponding number. I'm aware of that....

By the way, a note for anyone who might want to pick this up: I'm planning to do a rewrite of the `repo-create` docs to "backport" #9103 to `master` anyway,...

> To avoid fingerprinting of chunk content via the chunks IDs. I see. Thanks for the explanation! :+1: > The fact that borg uses sha256 IDs when no borg key...

AFAIK nobody picked up development yet, so yes, help is very much appreciated! :heart:

That's basically exactly the reason why I'm suggesting it :smile: `benchmark cpu` gives a crypto/hashing-focused view on things. Reality is wildly different, precisely because Borg is doing a whole lot...

> IIRC this was suggested (by me?) and discussed before, check the other issues. I searched before, didn't find anything, searched again now and found it (#7600). I didn't search...

Thanks again :+1: I did some testing with `benchmark crud` on an 8th gen Intel notebook (Intel Core i5-8265U, with AES but without SHA256 hardware acceleration, launched in 10/2018) with...

> Did you see there is now also `borg benchmark cpu`? It's a more synthetic benchmark only for the misc. algorithms, but it shows how fast most of them are...