dkg at fifthhorseman
Oct 28, 2009, 7:59 AM
Post #3 of 3
On 10/28/2009 09:35 AM, Werner Koch wrote:
> Okay, the docs are not clear. I changed it to say "before
> Let me know if you find other unclear documentation.
line 523 of gcrypt.texi appears to claim that the full set of
functionality allowed before gcry_check_version is
GCRYCTL_SET_THREAD_CBS. Maybe it should mention GCRYCTL_FORCE_FIPS_MODE
and GCRYCTL_ENABLE_M_GUARD and GCRYCTL_ANY_INITIALIZATION_P (and others?)
Alternately, if there really are valid phases of initialization, maybe
it'd be useful to define them (with more semantically-meaningful names
than my earlier "A,B,C"), and indicate which commands belong to which phase?
Another thing that might be useful to document is what the relationship
is between the other gcry_control() calls and
GCRYCTL_INITIALIZATION_FINISHED -- at the moment, it's unclear what the
consequences of GCRYCTL_INITIALIZATION_FINISHED are, other than
GCRYCTL_INITIALIZATION_FINISHED_P returning a different value, and the
library appears to work without that call. So why should a user bother
to issue GCRYCTL_INITIALIZATION_FINISHED?