1. 08 Jun, 2007 1 commit
    • cmiller@zippy.cornsilk.net's avatar
      Bug #28984: crasher on connect with out of range password length in \ · 4584ac2c
      cmiller@zippy.cornsilk.net authored
      	protocol
      
      One could send a malformed packet that caused the server to SEGV.  In 
      recent versions of the password protocol, the client tells the server 
      what length the ciphertext is (almost always 20).  If that length was
      large enough to overflow a signed char, then the number would jump to 
      very large after being casted to unsigned int.
      
      Instead, cast the *passwd char to uchar. 
      4584ac2c
  2. 07 May, 2007 1 commit
  3. 04 May, 2007 2 commits
  4. 30 Apr, 2007 1 commit
  5. 29 Apr, 2007 5 commits
  6. 28 Apr, 2007 2 commits
    • gshchepa/uchum@gshchepa.loc's avatar
      Fixed bug #13191. · 3adcb94e
      gshchepa/uchum@gshchepa.loc authored
      INSERT...ON DUPLICATE KEY UPDATE may cause error 1032: 
      "Can't find record in ..." if we are inserting into
      InnoDB table unique index of partial key with
      underlying UTF-8 string field.
      
      This error occurs because INSERT...ON DUPLICATE uses a wrong
      procedure to copy string fields of multi-byte character sets
      for index search.
      3adcb94e
    • gshchepa/uchum@gshchepa.loc's avatar
      Fixed bug #20710. · 3322b3c0
      gshchepa/uchum@gshchepa.loc authored
      This bug occurs when error message length exceeds allowed limit: my_error()
      function outputs "%s" sequences instead of long string arguments.
      
      Formats like %-.64s are very common in errmsg.txt files, however my_error()
      function simply ignores precision of those formats.
      3322b3c0
  7. 26 Apr, 2007 2 commits
  8. 24 Apr, 2007 2 commits
  9. 23 Apr, 2007 2 commits
  10. 20 Apr, 2007 1 commit
  11. 19 Apr, 2007 1 commit
  12. 18 Apr, 2007 1 commit
  13. 17 Apr, 2007 3 commits
  14. 14 Apr, 2007 1 commit
  15. 12 Apr, 2007 2 commits
  16. 11 Apr, 2007 4 commits
  17. 10 Apr, 2007 9 commits