Xortify is a network security drone that uses Web 2.0 techniques to link between your XOOPS installs and other via a Server Cloud. This will prevent security intrusions to your xoops with accurate deceptive notation of the intruder and prevent any farmed attacks. It is an accessory and required Protector to be installed an running to be part of the hookup. Otherwise it will run without protector just make sure you deselect protector as a provider.

It will display a template if you are banned and is an accessory to protector or any other firewall technology. The site itself is driven from http://www.xortify.com .. Cloud computing is web 2.0/3.0 stuff it used a SOAP or JSON, XML or Serialisation to exchange on the API backend to work, this will eventually be included in xoops as a support class.

A cloud computing process is one which staggers multiple networks sometime and mainly unknown to the webmaster into a network or cloud of data. In this example it is IP and Netaddy names to control access lists.

This will prevent predators from exposing your network to lag and other attacks from link farming, often this means many xoops are attacked in occasions which is all the time caught by protector, this way if an attack is in process across a large spectrum of links, your site will down itself to your sourced attack even if it is discovered on a completely unaffiliated site that is link farmed to yours or on a XOOPS User list.

Xortify is a cloud solution to protectors Bad IPs, if someone attempts to hack your site and becomes a bad IP it will then send the IP to the Ban Cloud on Xortify.com and its paired cloud Xortify.chronolabs.coop. It will also poll the server to make sure it has the latest ban list so your website will be aware of malusers before they attack through farming IP from services like Google or bing.

Xortify is finally bug free, there was a lasting reminder of how it can be quiet frustrating developing software, especially cloud solutions with so many variables to hone to make sure the system is working, you should enjoy this version and any future releases for XOOPS 2.7, but as it stands I can't find anymore situations, warnings, notices or WSOD with this copy.

Features
* Cloud Server List Propogation - Floating cloud
* Cache Maintenance Cleanup
* Better Ban List
* Better XOOPS 2.5 Module Class GUI
* Greater Ban Diagnostics
* CURL Resolution Timeout
* Fault Locking/Delay
* Performance Extras - fixed
* Cron Job State and Timing
* Pre PHP 5.2 Compatibility
* My IP Information Anti Ban Prevention
* Provider Plugins
* Admin Usage Log
* Protector Module Provider
* Project Honeypot Provider
* Stop Forum Spam Provider
* Spider Module Provide
* XML Polling Protocol
* Serialisation API Protocol
* JSON API Protocol
* SOAP API Protocol
* Anti Spamming with User Signupl
* Anti Harvesting
* Serialisation API Protocol

Installation

Download the lastest version from Chronolabs on Google code or off sourceforge. Unzip the archive you should have a folder called 'htdocs' in the unzipped location. Copy the contents of 'htdocs' folder to your CMS root path this is generally a folder called 'public_html' or 'www' on your FTP service of your website. Log into your CMS and goto the modules/applications installation section, this is generally in your system control area under modules. Click on the icon that represent installing the module. If all has behaved as need be then your module is installed. If your module requires a user licences, keys or a username then sign-up to the apprpriate sites and retreieve your keys or IDs (Links should be provided in the preferences) and paste the values into preferences. Now your right to go!

Upgrading

Download the lastest version from Chronolabs on Google code or off sourceforge. Unzip the archive you should have a folder called 'htdocs' in the unzipped location. Copy the contents of 'htdocs' folder to your CMS root path this is generally a folder called 'public_html' or 'www' on your FTP service of your website. Log into your CMS and goto the modules/applications installation section, this is generally in your system control area under modules. Click on the icon that represent upgrading the module. Your version number should no longer be in bold and would have changed!

Reporting a Bug

The google code section has an area for reporting bugs called issues. Any issue or bug you believe you are having that is not a result of your site services then please report it here. The URL for reporting bugs is as follows: http://code.google.com/p/chronolabs2/issues/entry

Please report the following:

a) Version of CMS
b) Version of PHP
c) Version of MySQL
d) Services Software ie. Apache, Zeus etc.
e) Version of Software
f) Error Messages
g) Steps to reproduce
e) Contact details for the team to get in touch should they need!

Simon, it is getting better, but there are still errors visible right after installation. I strongly suggest that you test your modules on PHP 5.4.x before you release them as "final" - you'll avoid a lot of complaints from the users.

This is in the Admin area:
Quote:

This is on the front:
Quote:

This is how it looks like:



Tested on XOOPS 2.5.6 on PHP 5.4.15

Item "E" in his report criteria tells the tale:

Quote:

Tested on Xoops 2.5.5 with PHP 5.3.8 and 5.3.24

Note: Why do you say install on xoops 2.5.5, and ignore the standard admin GUI?

OKey Try now mamba and the rest.. I have fixed those bugs... Sorry been unwell for awhile, thats why I haven't been very dilligent on the forums..

Thanks

Simon

Quote:

Core bug sound be right, should be checking if strlen(session_id())==0 befor calling session_start(), more examples of half done preloader code.

Simon,

Can you post the session bug to SVN? It'd be good to track it and I'm sure it'll get lost in a forum thread.