tree 1ac0053fa691017c13aaa44df1c21b259262dd6b
parent 4db437a4ed16da2803d4032d03aa8608e41f9b35
author Andrew Zaborowski <andrew.zaborowski@intel.com> 1507542419 +0200
committer Denis Kenzior <denkenz@gmail.com> 1507577577 -0500

unit: Add PBKDF2 tests from iwd

Test l_pkcs5_pbkdf2 using test data from iwd with the exception of the
test case that contained a \0 inside the password string.  ell
implementation treat the password as a C string so it can't have a \0 in
the middle, while the iwd version would take a length parameter.  We don't
have a use case for non-C-string passwords but RFC8018 doesn't exactly
prohibit them or define what is considered a password.

"Throughout this document, a password is considered to be an octet
string of arbitrary length whose interpretation as a text string is
unspecified.  In the interest of interoperability, however, it is
recommended that applications follow some common text encoding rules.
ASCII and UTF-8 [RFC3629] are two possibilities.  (ASCII is a subset
of UTF-8.)

Although the selection of passwords is outside the scope of this
document, guidelines have been published [NISTSP63] that may well be
taken into account."