Viewing 2 replies - 1 through 2 (of 2 total)
  • Task finished with these commits:

    1193688Added. Self-contained library to handle the hardening process
    1193691Fixed. Harden content directory with correct access rules
    1193701Fixed. Harden uploads directory with correct access rules
    1193713Fixed. Harden includes directory with correct access rules
    1194952Removed. Message for nonsupported Apache 2.4 hardening

    These changes also improved the blocking of files with the PHP extension in different cases as suggested by here [1]. Previously, the hardening that was being applied by the plugin in the content, includes, and uploads directories was only blocking the lower case extension.

    /wp-content/file.php - HTTP/1.1 403 Forbidden
    /wp-content/file.phP - HTTP/1.1 403 Forbidden
    /wp-content/file.pHp - HTTP/1.1 403 Forbidden
    /wp-content/file.pHP - HTTP/1.1 403 Forbidden
    /wp-content/file.Php - HTTP/1.1 403 Forbidden
    /wp-content/file.PHp - HTTP/1.1 403 Forbidden
    /wp-content/file.PHP - HTTP/1.1 403 Forbidden
    

    [1] https://wordpress.org/support/topic/bypass-php-file-execution-restriction

    Thread Starter Viktor Szépe

    (@szepeviktor)

    You’re typing faster then I can think.

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

The topic ‘How to detect Apache/2.4’ is closed to new replies.