Pass in an explicit digest length to the Crypto constructor since it
was assuming only sessions with a MAC key would have a MAC. Passing
an explicit size allows us to test the full digest in HMAC tests as
well.
Details
Details
- Reviewers
cem jmg - Commits
- rS346616: Run the plain SHA digest tests from NIST.
- tested with cryptosoft0 and ccr0
- this depends on the updated version of the nist-kat port that installs the plain SHA test vectors
Diff Detail
Diff Detail
- Repository
- rS FreeBSD src repository - subversion
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
tests/sys/opencrypto/cryptotest.py | ||
---|---|---|
266 ↗ | (On Diff #56111) | Because we don't support these algorithms? |
tests/sys/opencrypto/cryptotest.py | ||
---|---|---|
266 ↗ | (On Diff #56111) | Yes, at least not AFAIK. If it's just truncated SHA512 I could perhaps ask for SHA512 from OCF and truncate it manually. |
tests/sys/opencrypto/cryptotest.py | ||
---|---|---|
266 ↗ | (On Diff #56111) | Nah, like SHA-384, it has different initial constants. Can't just truncate ordinary SHA-512. |