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

file_key_management_plugin uses static IV for a key

    Details

      Description

      We should use random IV that is not reused and has no assiciation to key. This naturally requires that used IV is stored to file space (similar way as in example_key_management_plugin version).

        Gliffy Diagrams

          Attachments

            Activity

            Hide
            jplindst Jan Lindström added a comment -

            commit 3578419b778876fc1e7ec2a6994b9273b5d2b166
            Author: Jan Lindström <jan.lindstrom@mariadb.com>
            Date: Fri Mar 20 12:38:53 2015 +0200

            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

            Show
            jplindst Jan Lindström added a comment - commit 3578419b778876fc1e7ec2a6994b9273b5d2b166 Author: Jan Lindström <jan.lindstrom@mariadb.com> Date: Fri Mar 20 12:38:53 2015 +0200 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

              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: