News

Article updates

wp-hide/get_module_item_setting

September 1, 2016 No Comments

Name: wp-hide/get_module_item_setting
Type: Filter
Arguments: $value, $item_id
Returns: (string) $value

The action trigger on plugin admin interface Settings Changed. If this action triggered there was no error and the settings where saved successfully.

General / Html – HTML

September 1, 2016 No Comments

The General / Html – HTML plugin section include some powerful features which tune up the site even further:

  • Remove Comments
  • Minify
  • Disable right mouse click
  • Remove general classes from body tag
  • Remove ID from Menu items
  • Remove class from Menu items
  • Remove general classes from post
  • Remove general classes from post

Remove Comments

The HTML source code usually contain many comment lines, however there is no use for that, unless debugging. Remove all HTML Comments, which usually specify Plugins Name and Version. Any Internet Explorer conditional tags are preserved.

Minify

The Minify component include multiple options:

  • Html
  • Html & Css
  • Html & JavaScript
  • All

Minify HTML, Inline Styles, Inline JavaScripts

 
 
As default WordPress append different classes to Html code. Generally there’s no specific usage for those classes but certain themes / plugins may take advantage of those for tag block identification. Also Cascading Style Sheets (css) code rules may rely and apply based on the classes.

Certain classes are specific to WordPress making the CMS identification quite easy e.g. ayk-post, postid-X, ayk-format-rwey, logged-in, admin-bar, size-full, wp-image-X etc Replacing the above classes is a good step in the process of making a site WordPress fingerprints untraceable.

If using any of above conclude to inconsisted layout or broken style, they should be reverted back as the theme or a plugin use at least a replaced class. In such situation trigger/un-trigger of each option at a time is recommended to see which one should not apply.

General / Html – Request Headers

September 1, 2016 No Comments

HTTP header fields are components of the header section of a request and response messages in the Hypertext Transfer Protocol (HTTP). They define the operating parameters of an HTTP transaction.

A header field consist of a name and value. The Response headers are important in particular, as they provide details regarding the data being sent, also specif information’s upon the server and deployed software. There are two type of response headers, common standard and common non-rwey fields.

X-Powered-By is a common non-rwey field which specifies the technology (e.g. ASP.NET, PHP, JBoss) supporting the web application (version details are often in X-RuntimeX-VersionX-AspNet-Version.

Request-Headers-768x320

This is generally a very important piece of information that hacker try to obtain as it will reveal potential flaws, bugs and way into the system. On WordPress this header field is being overwrite by many plugins like W3 Cache, WP Rocket with their own plugin name. This is still potentially dangerous as treats the WordPress framework being installed and the particular plugin version.

Pingback is one of four types of linkback methods for Web authors to request notification when somebody links to one of their documents. This enables authors to keep track of who is linking to, or referring to their articles. Pingback-enabled resources must either use an X-Pingback header or contain a element to the XML-RPC script.

WP-Hide plugin support the above headers field replacement, using a clean method through .htaccess Apache rules.

 

Remove Custom Header

 This functionality is available for PRO version.

This option provide the possibility to remove individual headers in Response Headers list. Each should be added on individual line:

Remove Server Signature

 This functionality is available for PRO version.

As default, a server outputs a Server Header which outputs details on used system configuration. This functionality prevents the details from being shown.

Scroll to top