There's been a TODO in validateCertificatePath() that notes a long-time bottleneck in the execution of the library:
// TODO: updateHex() takes approximately two seconds per execution, can we improve this?
I was playing around tonight and think I've discovered a fix for this using the new signature verification logic added in #299. Preliminary testing showed a 60% reduction in unit test execution time; I need to test this out in a server (probably use the FIDO Conformance testing server in the example project) and see if similar gains can be observed in something resembling actual use.
Perhaps this will also solve the performance issues noted in #308 when using @simplewebauthn/server in lambdas.
MasterKale
commented
1 year ago
There's been a TODO in
validateCertificatePath()that notes a long-time bottleneck in the execution of the library:I was playing around tonight and think I've discovered a fix for this using the new signature verification logic added in #299. Preliminary testing showed a 60% reduction in unit test execution time; I need to test this out in a server (probably use the FIDO Conformance testing server in the example project) and see if similar gains can be observed in something resembling actual use.
Perhaps this will also solve the performance issues noted in #308 when using @simplewebauthn/server in lambdas.