mirror of
git://git.gnupg.org/gnupg.git
synced 2025-07-02 22:46:30 +02:00
gpg,sm: Check compliance of the RNG.
* common/compliance.c (gnupg_rng_is_compliant): New. * g10/call-agent.c (start_agent) [W32]: Check rng compliance. * sm/call-agent.c (start_agent) [W32]: Ditto. * g10/encrypt.c (encrypt_simple, encrypt_crypt): Check that the RNG is compliant. * sm/encrypt.c (gpgsm_encrypt): Ditto. * g10/sign.c (do_sign): Ditto. * sm/sign.c (gpgsm_sign): Ditto. -- Under Windows we need to check that the Jitter RNG is active in de-vs mode. Under Linux this is not necessary because /dev/random can be scrutinized and is believed to provide enough entropy. Signed-off-by: Werner Koch <wk@gnupg.org>
This commit is contained in:
parent
bbbd0db34b
commit
a149afe338
8 changed files with 131 additions and 0 deletions
|
@ -66,6 +66,8 @@ int gnupg_digest_is_compliant (enum gnupg_compliance_mode compliance,
|
|||
int gnupg_digest_is_allowed (enum gnupg_compliance_mode compliance,
|
||||
int producer,
|
||||
digest_algo_t digest);
|
||||
int gnupg_rng_is_compliant (enum gnupg_compliance_mode compliance);
|
||||
|
||||
const char *gnupg_status_compliance_flag (enum gnupg_compliance_mode
|
||||
compliance);
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue