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).

      Attachments

        Activity

          Ascending order - Click to sort in descending order
          jplindst Jan Lindström (Inactive) created issue -
          jplindst Jan Lindström (Inactive) made changes -
          Field Original Value New Value
          Status Open [ 1 ] In Progress [ 3 ]
          jplindst Jan Lindström (Inactive) made changes -
          Resolution Fixed [ 1 ]
          Status In Progress [ 3 ] Closed [ 6 ]
          ratzpo Rasmus Johansson (Inactive) made changes -
          Workflow MariaDB v2 [ 60160 ] MariaDB v3 [ 66717 ]
          serg Sergei Golubchik made changes -
          Workflow MariaDB v3 [ 66717 ] MariaDB v4 [ 148911 ]

          People

            jplindst Jan Lindström (Inactive)
            jplindst Jan Lindström (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.