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

Parsec sends garbage when using an empty password

    XMLWordPrintable

Details

    • Bug
    • Status: Stalled (View Workflow)
    • Blocker
    • Resolution: Unresolved
    • None
    • 11.6
    • None
    • None

    Description

      About parsec authentication, when user has an empty password, user doesn't have an authentication_string set (visible in mysql.user).
      Exchanges when creating a connection results then sends unexpected data when asking for ext-salt.

      example when using an empty password, packet is for example :

      +--------------------------------------------------+
      |  0  1  2  3  4  5  6  7   8  9  a  b  c  d  e  f |
      +--------------------------------------------------+------------------+
      | 14 00 00 04 00 04 00 05  00 06 00 07 00 08 00 0B | ................ |
      | 00 0E 00 0F 00 10 00 13                          | ........         |
      +--------------------------------------------------+------------------+
      

      in place of something that begins with 'P0' like :

      +--------------------------------------------------+
      |  0  1  2  3  4  5  6  7   8  9  a  b  c  d  e  f |
      +--------------------------------------------------+------------------+
      | 14 00 00 04 50 00 01 A5  ED 67 34 40 70 2A E3 8A | ....P....g4@p*.. |
      | 00 A2 BB 63 6B 9C D3 13                          | ...ck...         |
      +--------------------------------------------------+------------------+
      

      Attachments

        Issue Links

          Activity

            People

              nikitamalyavin Nikita Malyavin
              diego dupin Diego Dupin
              Votes:
              0 Vote for this issue
              Watchers:
              5 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.