WordPress.org

Plugin Directory

Changeset 645743


Ignore:
Timestamp:
12/29/12 07:22:39 (16 months ago)
Author:
fredericktownes
Message:

Fixed security issue that can occur if using database caching to disk. If using database caching to disk with a web server with directory listing or web accessible wp-content/w3tc/dbcache/* directories. This patch works for all hosting environments / types where PHP is properly configured, i.e. .htaccess modifications (or other web server configuration changes) are *not* necessary to ensure proper security.

Location:
w3-total-cache
Files:
410 added
1 edited

Legend:

Unmodified
Added
Removed
  • w3-total-cache/trunk/readme.txt

    r645436 r645743  
    44Requires at least: 2.8 
    55Tested up to: 3.5 
    6 Stable tag: 0.9.2.4 
     6Stable tag: 0.9.2.5 
    77 
    88Improve site performance and user experience via caching: browser, page, object, database, minify and content delivery network support. 
     
    462462 
    463463== Changelog == 
     464 
     465= 0.9.2.5 = 
     466* Fixed security issue that can occur if using database caching to disk. If using database caching to disk with a web server with directory listing or web accessible wp-content/w3tc/dbcache/* directories. This patch works for all hosting environments / types where PHP is properly configured, i.e. .htaccess modifications (or other web server configuration changes) are *not* necessary to ensure proper security. Empty the database cache after performing the update if you use database caching to disk. 
    464467 
    465468= 0.9.2.4 = 
     
    792795= 0.5 = 
    793796* Initial release 
     797 
     798== Upgrade Notice == 
     799 
     800= 0.9.2.5 = 
     801* Fixed security issue that can occur if using database caching to disk. If using database caching to disk with a web server with directory listing or web accessible wp-content/w3tc/dbcache/* directories. This patch works for all hosting environments / types where PHP is properly configured, i.e. .htaccess modifications (or other web server configuration changes) are *not* necessary to ensure proper security. Empty the database cache after performing the update if you use database caching to disk. 
Note: See TracChangeset for help on using the changeset viewer.