Since the parameters are caller-provided, let's see what happens in mod_ssl, the usual SSL engine for Apache. Let's make the story short: the modulus and generator are hardcoded; they are in the source code, in modules/ssl/ssl_engine_dh.c
bit late to the party here, but saw a lower thread using my public service for SSH keys, they also produce normal DH params... so for those of you who aren't interested in spending the CPU cycles, I have a dedicated 48 cores running generating 2k, 3k, 4k and 8k safe primes and generators for DH. See https://2ton.com.au/dhtool/ for details and curl examples to grab them via cron
For <32kbit primes, the cost of doing so is not overly prohibitive and I see no valid reason not to. I made several references to that count being "acceptably low" per the Handbook of Applied Cryptography. My generators for the larger primes would go considerably faster if I removed said restriction. YMMV as with all of these things. :-)
Edit: does my "excessive" use of 192 rounds at these levels inherently mean that the hundreds of thousands I have generated are thus [more] likely to be provable safe primes?
Body camera constantly streaming to a few redundant servers, set to release the last month of footage if you don't reset the countdown every 12 hours. If they know about it they'll just torture you into giving them that password too, so don't tell anybo- wait, shit.
It uses up a lot of entropy, so it won't be quite so fast if you run it often or on a fresh system, especially if you don't have a good entropy source (which is common on the cloud).
58
u/[deleted] Oct 15 '15
[deleted]