We benchmarked DKLS/SoftSpoken signing with the default BoringSSL path and with -tags nobignum. BoringSSL does not show a clear end-to-end win, while it adds CGO/build complexity.
What was the intended benefit of introducing BoringSSL here? Was it mainly added for workloads such as the CGGMP21 library, or is it also expected to improve DKLS signing flows?
Also, is the nobignum path considered audited/supported for production use?
We benchmarked DKLS/SoftSpoken signing with the default BoringSSL path and with
-tags nobignum. BoringSSL does not show a clear end-to-end win, while it adds CGO/build complexity.What was the intended benefit of introducing BoringSSL here? Was it mainly added for workloads such as the CGGMP21 library, or is it also expected to improve DKLS signing flows?
Also, is the
nobignumpath considered audited/supported for production use?