Add full-fledged deterministic PRNG support for testing.

In several places, the tests override crypto_rand() or crypto_fast_prng() for one reason or another. We should provide a standard way for the tests to do this.

changed milestone to %Tor: 0.4.1.x-final

added actualpoints::1 component::core tor/tor dgoulet-merge milestone::Tor: 0.4.1.x-final owner::nickm priority::medium resolution::fixed reviewer::ahf severity::normal status::closed type::enhancement labels

I have a branch called "ticket29732", but the CI won't pass until we merge #29668 (moved)

New version at ticket29732_v2 with PR at https://github.com/torproject/tor/pull/909 .

Trac:
Status: assigned to needs_review

Trac:
Actualpoints: N/A to 1

Trac:
Reviewer: N/A to catalyst

Taking this per network-team meeting discussion.

Trac:
Reviewer: catalyst to ahf

I think this code looks good and can be merged. I've been focusing on checking to ensure that the API cannot be used wrongly in a non-testing setup and it seems like the important functions here are all protected using the TOR_UNIT_TESTS guard. If the reseeding mechanism, outside of the unit test setup, is disabled, Tor will crash with an unreached assertion in "production", which is what we want I think.

Trac:
Status: needs_review to merge_ready

Trac:
Keywords: N/A deleted, dgoulet-merge added

Merged! Great feature to have! Agree with ahf assessment, this can't be used in production afaict!

Trac:
Status: merge_ready to closed
Resolution: N/A to fixed

closed

added 8h of time spent

moved to tpo/core/tor#29732 (closed)