# std.crypto: improve KT documentation, use key_length for B3 key length \(\#25807\) · gitcafe/zig

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

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

Visibility: public

Requested revision: 4b593a6c24797484e68a668818736b0f6a8d81a2

Requested commit: 4b593a6c24797484e68a668818736b0f6a8d81a2

Commit: 4b593a6c24797484e68a668818736b0f6a8d81a2

Tree: d140c424346e4dd46688c00023d9a3b39ee99a1f

Author: Frank Denis

Committer: GitHub

## Message

```
std.crypto: improve KT documentation, use key_length for B3 key length (#25807)

It was not obvious that the KT128/KT256 customization string can be
used to set a key, or what it was designed to be used for at all.

Also properly use key_length and not digest_length for the BLAKE3
key length (no practical changes as they are both 32, but that was
confusing).

Remove unneeded simd_degree copies by the way, and that doesn't need
to be in the public interface.
```

## Parents

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

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