mirror of
https://git.postgresql.org/git/postgresql.git
synced 2025-02-23 19:39:53 +08:00
f5576a21b0
Use the padding provided by OpenSSL instead of doing it ourselves. The internal implementation was once applicable to the non-OpenSSL code paths, but those have since been removed. The padding algorithm is still the same. The OpenSSL padding implementation is stricter than the previous internal one: Bad padding during decryption is now an error, and encryption without padding now requires the input size to be a multiple of the block size, otherwise it is also an error. Previously, these cases silently proceeded, in spite of the documentation saying otherwise. Add some test cases about this, too. (The test cases are in rijndael.sql, but they apply to all encryption algorithms.) Reviewed-by: Jacob Champion <pchampion@vmware.com> Reviewed-by: Nathan Bossart <nathandbossart@gmail.com> Discussion: https://www.postgresql.org/message-id/flat/ba94c26b-0c58-c97e-7a44-f44e08b4cca2%40enterprisedb.com
73 lines
2.2 KiB
SQL
73 lines
2.2 KiB
SQL
--
|
|
-- AES cipher (aka Rijndael-128, -192, or -256)
|
|
--
|
|
|
|
-- some standard Rijndael testvalues
|
|
SELECT encrypt(
|
|
'\x00112233445566778899aabbccddeeff',
|
|
'\x000102030405060708090a0b0c0d0e0f',
|
|
'aes-ecb/pad:none');
|
|
|
|
SELECT encrypt(
|
|
'\x00112233445566778899aabbccddeeff',
|
|
'\x000102030405060708090a0b0c0d0e0f1011121314151617',
|
|
'aes-ecb/pad:none');
|
|
|
|
SELECT encrypt(
|
|
'\x00112233445566778899aabbccddeeff',
|
|
'\x000102030405060708090a0b0c0d0e0f101112131415161718191a1b1c1d1e1f',
|
|
'aes-ecb/pad:none');
|
|
|
|
-- cbc
|
|
SELECT encrypt(
|
|
'\x00112233445566778899aabbccddeeff',
|
|
'\x000102030405060708090a0b0c0d0e0f101112131415161718191a1b1c1d1e1f',
|
|
'aes-cbc/pad:none');
|
|
|
|
-- without padding, input not multiple of block size
|
|
SELECT encrypt(
|
|
'\x00112233445566778899aabbccddeeff00',
|
|
'\x000102030405060708090a0b0c0d0e0f101112131415161718191a1b1c1d1e1f',
|
|
'aes-cbc/pad:none');
|
|
|
|
-- key padding
|
|
|
|
SELECT encrypt(
|
|
'\x0011223344',
|
|
'\x000102030405',
|
|
'aes-cbc');
|
|
|
|
SELECT encrypt(
|
|
'\x0011223344',
|
|
'\x000102030405060708090a0b0c0d0e0f10111213',
|
|
'aes-cbc');
|
|
|
|
SELECT encrypt(
|
|
'\x0011223344',
|
|
'\x000102030405060708090a0b0c0d0e0f101112131415161718191a1b',
|
|
'aes-cbc');
|
|
|
|
-- empty data
|
|
select encrypt('', 'foo', 'aes');
|
|
-- 10 bytes key
|
|
select encrypt('foo', '0123456789', 'aes');
|
|
-- 22 bytes key
|
|
select encrypt('foo', '0123456789012345678901', 'aes');
|
|
|
|
-- decrypt
|
|
select encode(decrypt(encrypt('foo', '0123456', 'aes'), '0123456', 'aes'), 'escape');
|
|
-- data not multiple of block size
|
|
select encode(decrypt(encrypt('foo', '0123456', 'aes') || '\x00'::bytea, '0123456', 'aes'), 'escape');
|
|
-- bad padding
|
|
-- (The input value is the result of encrypt_iv('abcdefghijklmnopqrstuvwxyz', '0123456', 'abcd', 'aes')
|
|
-- with the 16th byte changed (s/db/eb/) to corrupt the padding of the last block.)
|
|
select encode(decrypt_iv('\xa21a9c15231465964e3396d32095e67eb52bab05f556a581621dee1b85385789', '0123456', 'abcd', 'aes'), 'escape');
|
|
|
|
-- iv
|
|
select encrypt_iv('foo', '0123456', 'abcd', 'aes');
|
|
select encode(decrypt_iv('\x2c24cb7da91d6d5699801268b0f5adad', '0123456', 'abcd', 'aes'), 'escape');
|
|
|
|
-- long message
|
|
select encrypt('Lets try a longer message.', '0123456789', 'aes');
|
|
select encode(decrypt(encrypt('Lets try a longer message.', '0123456789', 'aes'), '0123456789', 'aes'), 'escape');
|