An error occurred fetching the project authors.
  1. 26 Nov, 2007 1 commit
    • thek@adventure.(none)'s avatar
      Bug#16470 crash on grant if old grant tables · 34565021
      thek@adventure.(none) authored
      Loading 4.1 into 5.0 or 5.1 failed silently because procs_priv table missing.
      This caused the server to crash on any attempt to store new grants because
      of uninitialized structures.
      
      This patch breaks up the grant loading function into two phases to allow
      for procs_priv table to fail with an warning instead of crashing the server.
      34565021
  2. 20 Sep, 2007 1 commit
  3. 26 Jun, 2007 1 commit
  4. 01 Jun, 2007 2 commits
  5. 11 May, 2007 2 commits
    • evgen@moonbone.local's avatar
      grant.result, grant.test: · 6c8f5476
      evgen@moonbone.local authored
        Corrected test case for the bug#27878.
      6c8f5476
    • evgen@moonbone.local's avatar
      Bug#27878: Unchecked privileges on a view referring to a table from another · 34f47812
      evgen@moonbone.local authored
      database.
      
      If a user has a right to update anything in the current database then the 
      access was granted and further checks of access rights for underlying tables
      wasn't done correctly. The check is done before a view is opened and thus no
      check of access rights for underlying tables can be carried out.
      This allows a user to update through a view a table from another database for
      which he hasn't enough rights.
      
      Now the mysql_update() and the mysql_test_update() functions are forces
      re-checking of access rights after a view is opened.
      34f47812
  6. 24 Apr, 2007 1 commit
  7. 17 Apr, 2007 1 commit
  8. 13 Apr, 2007 1 commit
  9. 03 Apr, 2007 2 commits
  10. 23 Mar, 2007 1 commit
  11. 24 Jan, 2007 1 commit
  12. 04 Dec, 2006 1 commit
    • andrey@example.com's avatar
      Fix for bug#22369: Alter table rename combined · e6a47277
      andrey@example.com authored
      with other alterations causes lost tables
      
      Using RENAME clause combined with other clauses of ALTER TABLE led to
      data loss (the data was there but not accessible). This could happen if the
      changes do not change the table much. Adding and droppping of fields and
      indices was safe. Renaming a column with MODIFY or CHANGE was unsafe operation,
      if the actual column didn't change (changing from int to int, which is a noop)
        
      Depending on the storage engine (SE) the behavior is different:
      1)MyISAM/MEMORY - the ALTER TABLE statement completes
        without any error but next SELECT against the new table fails.
      2)InnoDB (and every other transactional table) - The ALTER TABLE statement
        fails. There are the the following files in the db dir -
        `new_table_name.frm` and a temporary table's frm. If the SE is file
        based, then the data and index files will be present but with the old
        names. What happens is that for InnoDB the table is not renamed in the
        internal DDIC.
      
      Fixed by adding additional call to mysql_rename_table() method, which should
      not include FRM file rename, because it has been already done during file
      names juggling.
      e6a47277
  13. 21 Nov, 2006 1 commit
  14. 20 Nov, 2006 1 commit
    • monty@mysql.com/nosik.monty.fi's avatar
      Remove compiler warnings · e8258798
      monty@mysql.com/nosik.monty.fi authored
      (Mostly in DBUG_PRINT() and unused arguments)
      Fixed bug in query cache when used with traceing (--with-debug)
      Fixed memory leak in mysqldump
      Removed warnings from mysqltest scripts (replaced -- with #)
      e8258798
  15. 30 Aug, 2006 1 commit
  16. 29 Aug, 2006 2 commits
  17. 24 Aug, 2006 1 commit
  18. 23 Aug, 2006 1 commit
  19. 11 Aug, 2006 1 commit
  20. 03 Aug, 2006 2 commits
    • tnurnberg@mysql.com/salvation.intern.azundris.com's avatar
      Bug#20214: Incorrect error when user calls SHOW CREATE VIEW on non privileged view · 35c523a6
      "A SELECT privilege on a view is required for SHOW CREATE VIEW and it will stay
      that way because of compatibility reasons." (see #20136)
      
      a test case to illustrate how the ACLs work in this case (and ensure they will continue
      to do so in the future)
      35c523a6
    • svoj@may.pils.ru's avatar
      BUG#7391 - Cross-database multi-table UPDATE uses active database · 67db270c
      svoj@may.pils.ru authored
                 privileges
      
      This problem is 4.1 specific. It doesn't affect 4.0 and was fixed
      in 5.x before.
      
      Having any mysql user who is allowed to issue multi table update
      statement and any column/table grants, allows this user to update
      any table on a server (mysql grant tables are not exception).
      
      check_grant() accepts number of tables (in table list) to be checked
      in 5-th param. While checking grants for multi table update, number
      of tables must be 1. It must never be 0 (actually we have
      DBUG_ASSERT(number > 0) in 5.x in grant_check() function).
      67db270c
  21. 24 Jul, 2006 1 commit
  22. 06 Jun, 2006 1 commit
    • monty@mysql.com's avatar
      Re-apply missing changeset, orignally pushed by elliot · e50412ef
      monty@mysql.com authored
      Add define YASSL_PREFIX when compiling yassl
      
      Import patch from yaSSL
      - avoid allocating memory for each call to 'EVP_md5' and 
        'EVP_des_ede3_cbc' which were not released until server was stopped
      - Those functions are used from the SQL function 'des_encrypt' and
        'des_decrypt'.
      
      Add new define YASSL_PREFIX beforee including ssl.h to activate inclusion of prefix_*.h files
      
      Bug#20022 mysql-test-run can't be run with secure connections turned on for all testcases
      - Part 1, fixes rpl- and federated-tests where connection is made to 127.0.0.1
      
      - Include prefix files that renames all public functions in yaSSLs
        OpenSSL API to ya<function_name>. They will otherwise conflict
        with OpenSSL functions if loaded by an application that uses OpenSSL
        as well as libmysqlclient with yaSSL support.
      
      Bug#18235: assertion/crash when windows mysqld is ended with ctrl-c
        
      Two threads both try a shutdown sequence which creates a race to the
      de-init/free of certain resources.
        
      This exists in similar form in the client as 17926: "mysql.exe crashes
      when ctrl-c is pressed in windows."
      
      Update after merge to 5.0
      
      BUG#18669: Session COM_STATISTICS breaks mysqladmin status.
      Changed COM_STATISTICS to display the global status, instead of thead status, for slow queries and table opens.
      
      - In function 'handle_grant_struct' when searching the memory structures for an 
        entry to modify, convert all entries here host.hostname is NULL to "" and compare that 
        with the host passed in argument "user_from".
      - A user created with hostname "" is stored in "mysql.user" table as host="" but when loaded into 
        memory it'll be stored as host.hostname NULL. Specifiying "" as hostname means
        that "any host" can connect. Thus is's correct to turn on allow_all_hosts
        when such a user is found. 
      - Review and fix other places where host.hostname may be NULL.
      
      BUG#19394 OPT_INNODB_THREAD_CONCURRENCY duplicated
      Removed duplication (not a user-visible change)
      e50412ef
  23. 29 May, 2006 1 commit
  24. 26 May, 2006 1 commit
    • gkodinov@mysql.com's avatar
      BUG#18681: View privileges are broken · a21a2b5b
      gkodinov@mysql.com authored
      The check for view security was lacking several points :
      1. Check with the right set of permissions : for each table ref that
      participates in a view there were the right credentials to use in it's
      security_ctx member, but these weren't used for checking the credentials.
      This makes hard enforcing the SQL SECURITY DEFINER|INVOKER property
      consistently.
      2. Because of the above the security checking for views was just ruled out
      in explicit ways in several places.
      3. The security was checked only for the columns of the tables that are
      brought into the query from a view. So if there is no column reference
      outside of the view definition it was not detecting the lack of access to
      the tables in the view in SQL SECURITY INVOKER mode.
      
      The fix below tries to fix the above 3 points.
      a21a2b5b
  25. 23 May, 2006 1 commit
    • msvensson@neptunus.(none)'s avatar
      Bug#16297 In memory grant tables not flushed when users's hostname is "" · 7b2e709f
      msvensson@neptunus.(none) authored
       - In function 'handle_grant_struct' when searching the memory structures for an 
         entry to modify, convert all entries here host.hostname is NULL to "" and compare that 
         with the host passed in argument "user_from".
       - A user created with hostname "" is stored in "mysql.user" table as host="" but when loaded into 
         memory it'll be stored as host.hostname NULL. Specifiying "" as hostname means
         that "any host" can connect. Thus is's correct to turn on allow_all_hosts
         when such a user is found. 
       - Review and fix other places where host.hostname may be NULL.
      7b2e709f
  26. 06 Mar, 2006 1 commit
  27. 09 Jan, 2006 2 commits
  28. 14 Nov, 2005 1 commit
    • bar@mysql.com's avatar
      Bug#14406 GRANTS ON objects with non-ascii names borked after FLUSH PRIVILEGES · 8894bd8d
      bar@mysql.com authored
      ps_grant.result:
        Fixing result order.
      grant.result:
        Adding test case,
        fixing result order.
      grant.test:
        Adding test case.
      sql_acl.cc:
        Fixed that my_charset_latin1 was incorrectly used instead of system_charset_info.
        This problem was previously fixed by Ingo in 5.0.
        This patch is basically a backport of the same changes into 4.1.
      8894bd8d
  29. 04 Aug, 2005 1 commit
    • bar@mysql.com's avatar
      grant.result, grant.test: · 1b40adcb
      bar@mysql.com authored
        fixing tests accordingly
      item.cc:
        Bug #10892 user variables not auto cast for comparisons
        When mixing strings with different character sets,
        and coercibility is the same, we allow conversion
        if one character set is superset for other character set.
      1b40adcb
  30. 28 Jul, 2005 1 commit
  31. 05 Jul, 2005 2 commits
  32. 20 Jun, 2005 1 commit
  33. 29 Mar, 2005 1 commit