Enable soft crypto device support when testing soft crypto devices

[markj]

Summary

The cryptocheck utility only enables software crypto when testing with the soft crypto device.

Since ossl(4) is gated behind the same kern.cryptodevallowsoft sysctl, cryptocheck should also enable soft crypto support when using the ossl crypto device. If this is not done, a cryptic series of generic "Invalid argument" messages are printed when testing with the ossl(4) device.

Test Plan

cryptocheck -a aes-gcm -d ossl0 -z

echo $?
0

[markj]

I think this is ok, but aesni and armv8crypto need the same treatment. And, if one is running as a non-root user, we won't toggle the sysctl and will end up with same errors anyway.

[tpearson_raptorengineering.com]

Added aesni and armv8crypto alongside ossl

[markj]

I just went ahead and uploaded an extended diff, I hope that's ok: https://reviews.freebsd.org/D52490

tools/tools/crypto/cryptocheck.c

382

4 is not the right length to use for the other strings.

[tpearson_raptorengineering.com]

In D52400#1198743, @markj wrote:

I just went ahead and uploaded an extended diff, I hope that's ok: https://reviews.freebsd.org/D52490

No problem, I consider most of this a trivial change. Was just a landmine I stepped on while trying to get the test framework up and running with near zero documentation.

[markj]

Closing this since a similar change landed in commit e63bf6aa523eb9a865b7ce34d01e75a13818b367