Jan Lindström
3578419b77
MDEV-7797: file_key_management_plugin uses static IV for a key
...
Currently crypt data is written to file space always. Use
that to obtain random IV for every object (file).
Beatify code to confort InnoDB coding styles.
Conflicts:
storage/innobase/fil/fil0crypt.cc
storage/xtradb/fil/fil0crypt.cc
2015-03-20 13:09:07 +02:00
Jan Lindström
b3438f24a1
MDEV-7803: Encryption metadata (crypt_data) is written to InnoDB file space page 0 even when encryption is not enabled
2015-03-19 14:09:49 +02:00
Jan Lindström
bab0bdbb5c
Introduce two debug crash points while writing crypt data to test
...
redo operations.
2015-03-19 07:13:07 +02:00
Jan Lindström
c4b268add0
InnoDB cleanup. Remove empty statements i.e. extra ; characters.
2015-03-16 09:14:13 +02:00
Jan Lindström
7047bef1ef
Use standard InnoDB error mechanism on compression and encryption
...
error messages.
2015-03-02 10:55:48 +02:00
Jan Lindström
e2e809860e
Pass down the information should we encrypt the page at os0file.cc
...
when page compression and google encryption is used.
2015-02-10 10:21:18 +01:00
Sergei Golubchik
21430e4378
encryption keys service
2015-02-10 10:21:18 +01:00
Sergei Golubchik
cf8bf0b68e
encryption key management plugin api
2015-02-10 10:21:17 +01:00
Monty
d7d589dc01
Push for testing of encryption
2015-02-10 10:21:17 +01:00
