◄ Wiki / Crypto
test vectors
Official known input-and-expected-output pairs used to prove a crypto implementation is correct.
Cryptographic standards publish 'known-answer' test vectors: given this exact input and key, the output must be exactly this. Running your implementation against them and matching byte-for-byte confirms you got the algorithm right, since crypto has no room for 'close enough'. Pinning primitives to published vectors guards against subtle bugs.
See also
- table-free AESAn AES encryption implementation that avoids memory lookup tables so its timing can't leak the secret key.
- to-be-signed (TBS) bytesThe exact bytes of a certificate that a digital signature actually covers.
- TLS 1.3The current, streamlined version of the TLS encryption protocol.
Referenced by
table-free AES · timing leak / side channel · to-be-signed (TBS) bytes