• Resolved Aaron

    (@aaron13100)


    There’s a bit of a security risk with the backups folder.

    The message “Kangaroos cannot jump here” is always displayed when it’s accessed directly, which is fine. However, the message itself tells the world that the plugin is installed on the website. Also, the .htaccess file does not limit access to the backup files ending in .wpress. With no other security plugins a user is free to guess (or brute force search) names of the backup files and then download the files.

    When I try to overwrite the .htaccess file it’s automatically overwritten by the plugin, so I’m unable to tighten security.

    I think it would be better to return a plain 404 so that there is no hint that the plugin is installed. Also I think public access to the backup files should be prevented using the .htaccess file. For example with the following or something similar.

    `# Deny access to files with extensions .ini, .psd, .log, .sh
    <FilesMatch “\.(ini|psd|log|sh|zip|wpress|bz2|gzip|php|config|html)$”>
    Order allow,deny
    Deny from all

    </FilesMatch>

    thanks

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Yani

    (@yaniiliev)

    Guessing the backup filename is not a trivial task and it will take a really long time to brute-force it.
    If you are not comfortable with keeping your backups on the server where the site resides, you should try using our cloud storage extensions.
    You can delete backups from the plugin backups menu.

    Thread Starter Aaron

    (@aaron13100)

    Using a cloud storage extension and deleting the backup afterwards are workarounds that don’t solve the problem. They’re not fixes.

    Fixing the problem is as easy as adding

    ‘Deny from all’,

    to /all-in-one-wp-migration/lib/vendor/servmask/filesystem/class-ai1wm-file-htaccess.php line 53.

    Plugin Author Yani

    (@yaniiliev)

    How would you download the migration file if you Deny from all?

    Thread Starter Aaron

    (@aaron13100)

    Good point.

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘htaccess and Kangaroos cannot jump here’ is closed to new replies.