Signed – Final Major (ver. 2.2RC)
Time and time again I come by these websites that require an online authentication like identification of you as an individual or business this is also true of SSL Signing. The only thing is they only seem to verify email addresses, never ask you for any identification and rarely have any versification system. Self Signed is based on the protomodel – http://sourceforge.net/projects/chronolabs/files/Encryption/Digital%20Signatures/signed.labs.coop%20%7E%20v1.1.10%20%7E%20final%20minor.tar.gz/download but for XOOPS 2.5. This comes with an API that allows for a class one only or class one and class two self identification on the API then provides to them in the format they require (JSON, Serialisation or XML) your full signature. This could be from your 3×3 code with an email address or a date it contains, it also comes with a root certificate much like an SSL certificate.
The receptacle of the Signature data, has method and a call back to be notified when the signature if it does expire or someone else has checked the attached identification that the soignee has scanned in and loaded into your environment and flag it for renew or incorrectly uploaded which temporarily if not on a time delay ends the ability for that signature to be valid.
I see this as a clear path too something like httpx:// a self signed with peer-reviewing communication method that is completely open and true law based pseudo-sciences no like the like current SSL which only seems to check and email address and has a master key as well, self signing is the way of the future and explicative to the environment of open renderment of open source and the communities with software and network layer dependencies in our object orientated world and people.
Due to the nature of this utility I will be opening it to demonstration in a couple of days with the user-name provided but you will be able to see it at
Download the latest 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!
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!
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: https://sourceforge.net/p/chronolabs/tickets/?source=navbar
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!