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

Several server options / settings still not visible from SQL level

    XMLWordPrintable

Details

    Description

      E.g. the actual used values of allow-suspicious-udfs and skip-grant-tables can't be seen in SHOW GLOBAL VARIABLES output, and are not listed in INFORMATION_SCHEMA.SYSTEM_VARIABLES either.

      As both of these settings have security implications it should be possible to see their current value from the SQL level though, for audit / secure configuration check purposes.

      Especially with the now added GLOBAL_VALUE_ORIGIN and GLOBAL_VALUE_PATH information in I_S SYSTEM_VARIABLES, every setting that can be done via command line or my.cnf should actually be visible in SYSTEM_VARIABLES ...?

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-24815 Add 'allow-suspicious-udfs' and 'skip-grant-tables' to system variables

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed
          split to

          Task - A task that needs to be done. MDEV-30188 Ensure all binlog* variables are visible as system variables

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Task - A task that needs to be done. MDEV-30189 Add and alias remaining mariadbd replication command line options as system variables

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Open

          Activity

            People

              Unassigned Unassigned
              danblack Daniel Black
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:

                Git Integration

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