Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-7803

Encryption metadata (crypt_data) is written to InnoDB file space page 0 even when encryption is not enabled

        Details

          Description

          • When innodb_encrypt_tablespace == FALSE and fil_space_page_encrypted(space) == FALSE make sure that no encryption data is written to file space page 0 and redo-logs.
          • If we have existing database that is not encrypted make sure that encryption can be enabled and all existing file spaces are encrypted (Google encryption).

            Gliffy Diagrams

              Attachments

                Activity

                Hide
                Permalink
                jplindst Jan Lindström added a comment -

                commit b3438f24a17a28b2d396208a1bb072199cef5f39
                Author: Jan Lindström <jan.lindstrom@mariadb.com>
                Date: Thu Mar 19 14:09:49 2015 +0200

                MDEV-7803: Encryption metadata (crypt_data) is written to InnoDB file space page 0 e
                ven when encryption is not enabled

                Show
                jplindst Jan Lindström added a comment - commit b3438f24a17a28b2d396208a1bb072199cef5f39 Author: Jan Lindström <jan.lindstrom@mariadb.com> Date: Thu Mar 19 14:09:49 2015 +0200 MDEV-7803 : Encryption metadata (crypt_data) is written to InnoDB file space page 0 e ven when encryption is not enabled

                  People

                  • Assignee:
                    jplindst Jan Lindström
                    Reporter:
                    jplindst Jan Lindström
                  • Votes:
                    0 Vote for this issue
                    Watchers:
                    2 Start watching this issue

                    Dates

                    • Created:
                      Updated:
                      Resolved: