We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi, gpg's binary has a optional switch --debug-quick-random which will use non-blocking random sources and is nice to use for tests/CI.
--debug-quick-random
How do I toggle with switch with GPGME? I searched the source here for several keywords such as "random" and "quick" and did not find it.
A brief cross reference to the GPG source at https://github.com/gpg/gnupg/blob/98c52aeb31f4bf2604727aacad982fb51c04063f/g10/gpg.c#L2908 shows me that for a low level API call I'd need to call a function like gcry_control or do something with a constant named GCRYCTL_ENABLE_QUICK_RANDOM but I did not find anything like these defined in any rb files here.
gcry_control
GCRYCTL_ENABLE_QUICK_RANDOM
Thanks!
The text was updated successfully, but these errors were encountered:
This would also simplify my specs greatly as well
Sorry, something went wrong.
This request may soon be moot: https://lwn.net/Articles/884875/
No branches or pull requests
Hi, gpg's binary has a optional switch
--debug-quick-random
which will use non-blocking random sources and is nice to use for tests/CI.How do I toggle with switch with GPGME? I searched the source here for several keywords such as "random" and "quick" and did not find it.
A brief cross reference to the GPG source at https://github.com/gpg/gnupg/blob/98c52aeb31f4bf2604727aacad982fb51c04063f/g10/gpg.c#L2908 shows me that for a low level API call I'd need to call a function like
gcry_control
or do something with a constant namedGCRYCTL_ENABLE_QUICK_RANDOM
but I did not find anything like these defined in any rb files here.Thanks!
The text was updated successfully, but these errors were encountered: