libsodium/test/default/sodium_utils.exp

0
0
-1
0
0
0
0
0
010000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000
010100000000000000000000000000000000000000000000
020000000000000000000000000000000000000000000000
0001ff000000000000000000000000000000000000000000
0
0
000000000000fffefefefefefefefefefefefefefefefefe
00000000000000000000fffefefefefefefefefefefefefe
00000000000000000000000000000000000000000000fffe
fcfffffffffffbfdfefefefefefefefefefefefefefefefe
fcfffffffffffffffffffbfdfefefefefefefefefefefefe
fcfffffffffffffffffffffffffffffffffffffffffffbfd
fcfffffffffffffffffffffffffffffffffffffffffffbfd
fcfffffffffffffffffffffffffffffffffffffffffffbfd
fcfffffffffffffffffffffffffffffffffffffffffffbfd
fcfffffffffffffffffffffffffffffffffffffffffffbfd
Add tests for sodium_*() functions. 2013-04-26 01:37:15 -04:00			`0`
			`0`
Have sodium_memcmp(a,b,s) return -1 if a != b, document return value. 2013-10-30 09:47:13 -04:00			`-1`
Add tests for sodium_*() functions. 2013-04-26 01:37:15 -04:00			`0`
			`0`
Relax most __attribute__ ((nonnull)) to allow 0-length inputs to be NULL. Justifications: - crypto_(auth\|hash\|generichash\|onetimeauth\|shorthash): it's legal to hash or HMAC a 0-length message - crypto_box: it's legal to encrypt a 0-length message - crypto_sign*: it's legal to sign a 0-length message - utils: comparing two 0-length byte arrays is legal memzero on a 0-length byte array is a no-op converting an empty hex string to binary results in an empty binary string converting an empty binary string to hex results in an empty hex string converting an empty b64 string to binary results in an empty binary string converting an empty binary string to b64 results in an empty b64 string sodium_add / sodium_sub on zero-length arrays is a no-op For the functions declared in utils.h, I moved the logic into private functions that have the __attribute__ ((nonnull)) check, but they are only called when the corresponding length argument is non-0. I didn't do this for the hash/box/sign functions since it would have been a lot more work and quite a large refactor. Only memset() may have issues with a zero length. Fix tests, use guard page instead of NULL because of Wasm 2019-02-02 16:47:31 -05:00			`0`
			`0`
			`0`
Add sodium_increment() 2015-06-22 07:53:35 -04:00			`010000000000000000000000000000000000000000000000`
			`000000000000000000000000000000000000000000000000`
			`010100000000000000000000000000000000000000000000`
			`020000000000000000000000000000000000000000000000`
			`0001ff000000000000000000000000000000000000000000`
Relax most __attribute__ ((nonnull)) to allow 0-length inputs to be NULL. Justifications: - crypto_(auth\|hash\|generichash\|onetimeauth\|shorthash): it's legal to hash or HMAC a 0-length message - crypto_box: it's legal to encrypt a 0-length message - crypto_sign*: it's legal to sign a 0-length message - utils: comparing two 0-length byte arrays is legal memzero on a 0-length byte array is a no-op converting an empty hex string to binary results in an empty binary string converting an empty binary string to hex results in an empty hex string converting an empty b64 string to binary results in an empty binary string converting an empty binary string to b64 results in an empty b64 string sodium_add / sodium_sub on zero-length arrays is a no-op For the functions declared in utils.h, I moved the logic into private functions that have the __attribute__ ((nonnull)) check, but they are only called when the corresponding length argument is non-0. I didn't do this for the hash/box/sign functions since it would have been a lot more work and quite a large refactor. Only memset() may have issues with a zero length. Fix tests, use guard page instead of NULL because of Wasm 2019-02-02 16:47:31 -05:00			`0`
			`0`
More checks for sodium_add() (overlaps) and sodium_increment() 2015-12-06 13:06:27 -05:00			`000000000000fffefefefefefefefefefefefefefefefefe`
			`00000000000000000000fffefefefefefefefefefefefefe`
			`00000000000000000000000000000000000000000000fffe`
			`fcfffffffffffbfdfefefefefefefefefefefefefefefefe`
			`fcfffffffffffffffffffbfdfefefefefefefefefefefefe`
			`fcfffffffffffffffffffffffffffffffffffffffffffbfd`
Relax most __attribute__ ((nonnull)) to allow 0-length inputs to be NULL. Justifications: - crypto_(auth\|hash\|generichash\|onetimeauth\|shorthash): it's legal to hash or HMAC a 0-length message - crypto_box: it's legal to encrypt a 0-length message - crypto_sign*: it's legal to sign a 0-length message - utils: comparing two 0-length byte arrays is legal memzero on a 0-length byte array is a no-op converting an empty hex string to binary results in an empty binary string converting an empty binary string to hex results in an empty hex string converting an empty b64 string to binary results in an empty binary string converting an empty binary string to b64 results in an empty b64 string sodium_add / sodium_sub on zero-length arrays is a no-op For the functions declared in utils.h, I moved the logic into private functions that have the __attribute__ ((nonnull)) check, but they are only called when the corresponding length argument is non-0. I didn't do this for the hash/box/sign functions since it would have been a lot more work and quite a large refactor. Only memset() may have issues with a zero length. Fix tests, use guard page instead of NULL because of Wasm 2019-02-02 16:47:31 -05:00			`fcfffffffffffffffffffffffffffffffffffffffffffbfd`
			`fcfffffffffffffffffffffffffffffffffffffffffffbfd`
			`fcfffffffffffffffffffffffffffffffffffffffffffbfd`
			`fcfffffffffffffffffffffffffffffffffffffffffffbfd`