# Remove Gimli and Xoodoo from the standard library \(\#14928\) · gitcafe/zig

[View on GitCafe](https://git.cafe/gitcafe/zig/commit/dff4bbfd2426ce4943972782d2bcffc89b3fd26d)

Repository: [gitcafe/zig](https://git.cafe/gitcafe/zig)

Visibility: public

Requested revision: dff4bbfd2426ce4943972782d2bcffc89b3fd26d

Requested commit: dff4bbfd2426ce4943972782d2bcffc89b3fd26d

Commit: dff4bbfd2426ce4943972782d2bcffc89b3fd26d

Tree: d5432f82eed373e5713add5336464f2d6bfc50f4

Author: Frank Denis

Committer: GitHub

## Message

```
Remove Gimli and Xoodoo from the standard library (#14928)

These are great permutations, and there's nothing wrong with them
from a practical security perspective.

However, both were competing in the NIST lightweight crypto
competition.

Gimli didn't pass the 3rd selection round, and is not much used
in the wild besides Zig and libhydrogen. It will never be
standardized and is unlikely to get more traction in the future.

Xoodyak, that Xoodoo is the permutation of, was a finalist.

It has a lot of advantages and *might* be standardized without NIST.
But this is too early to tell, and too risky to commit to it
in a standard library.

For lightweight crypto, Ascon is the one that we know NIST will
standardize and that we can safely rely on from a usage perspective.

Switch to a traditional ChaCha-based CSPRNG, with an Ascon-based one
as an option for constrained systems.

Add a RNG benchmark by the way.

Gimli and Xoodoo served us well. Their code will be maintained,
but outside the standard library.
```

## Parents

- [bc0f246911a35324473f72b770cc5715902cc912](https://git.cafe/gitcafe/zig/commit/bc0f246911a35324473f72b770cc5715902cc912?format=markdown)

[Source at this commit](https://git.cafe/gitcafe/zig/tree/dff4bbfd2426ce4943972782d2bcffc89b3fd26d?format=markdown)