Look-See Security Scanner
[resolved] Look-See Security Scanner: MySQL error on table creation (4 posts)

  1. labarbiche
    Posted 3 years ago #


    I did install Look-See Security Scanner on a fresh wordpress 3.5.1 install, that I host myself.
    I use MySQL 5.5.29-0ubuntu0.12.04.2 with MySQL charset: UTF-8 Unicode (utf8) , and tables in InnoDB format.

    When I first ran Look-See Security Scanner, it asked my to install definition files, then again and again.

    The apache logs state:
    MySQL error: Specified key was too long; max key length is 767 for the table creation.

    As a workaround, in wp-content/plugins/look-see-security-scanner/index.php I removed in the SQL table creation the line
    UNIQUE KEY file2 (file,file_hash),
    as the resulting key file2 is too long for my MySQL configuration (InnoDB).

    See Prefix limitations on the MySQL documentation.

    I'm sure there's a better fix :)


  2. blobfolio
    Plugin Author

    Posted 3 years ago #

    Thanks for bringing this to my attention, labarbiche!

    I've run into this issue on another server using InnoDB as well. I'll be releasing an update with a new table structure this week that should work with that engine. I'll post back here once it's up.

  3. blobfolio
    Plugin Author

    Posted 3 years ago #


    The change was actually rather simple, so I've managed to push out an updated version this morning (13.04)! I tested it with both MyISAM and InnoDB storage engines, so you should be good to go.

    Thanks again for your feedback!

  4. labarbiche
    Posted 3 years ago #

    Thanks for the quick fix !
    Works like a charm now !
    Have a nice day

Topic Closed

This topic has been closed to new replies.

About this Plugin

  • Look-See Security Scanner
  • Frequently Asked Questions
  • Support Threads
  • Reviews

About this Topic


No tags yet.