Thomas Montaigu 748dac511c fix(csprng)!: start from TableIndex::FIRST and not SECOND ...

Now that the csprng can start from FIRST, we make it
start from FIRST.

Other changes are:
1) Using std::ops::Bound as the type of the bound/end in AesCtrGenerator
and State makes it more explicit for the caller what bound it uses
(Excluded, Included, Unbounded).

2) add proper overflow check in skip_bytes/check_fork

Without these overflow checks the state would wrap, it could lead to
misuses

This means by default data generated from previous versions
is not compatible with newer versions unless explicitely constructed
with the correct AesCtrParams (starting at SECOND).

This is fine for compressed data generated by tfhe-rs thanks
to the versionning system.

The test-vectors had to be regenerated as they did change
Backward data for xof has also been regenerated, as its was only added
in main branch (not release) thus data is considered not stable yet
Added a full server key to the backward data that uses this new generator

2026-03-10 10:43:34 +01:00

..

test-vectors

fix(csprng)!: start from TableIndex::FIRST and not SECOND

2026-03-10 10:43:34 +01:00

trivium

chore(ci): fix typos in documentation

2026-01-16 18:06:37 +01:00