Posted by David Fifield on Nov 01
It appears that this problem is now fixed. The software now generates a
CA certificate with an unpredictable private key when run for the first
time. The fix is in the released version 3.2.1.
I’ve updated the advisory page.
David Fifield