Features:

• Revolving File Key Store


• IDentification Storage and Capture


• Full Right to view Suffix and Prefix names


• Individual Signatures


• Organisational Signatures


• Transposition File Store - No Database


• Discoverable API


• Multi-lingugal (Translation Required)


• Unsigning/Resigning API

Warning: DUE To the divination method of the XCP Checksum with locks; if you generate with the standard formula in here your other certificate types like LABSCOOP-DS 1.03 like SSA etc. In your certificate forumate they can resign even the oldest by divinating the lock with this application framework!

Require: Translators; and country signature types need to be added to the trunk if translators could get crackin!!

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 signee 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.
Demonstration.

This includes an API that allows for signature bases to be unsigned if someone's identification fails check standards; through call-backs and API which is part of the system!

Due to the nature of this utility I will be opening it to demostration in a couple of days with the username provided but you will be able to see it at

URL: https://signed.ringwould.com.au
Installation

Download: ~~~::[ *.7z ! *.rar ! *.tar.gz ! *.tar.bz2 ! *.zip ! *.iso ! *.exe ! *.war ! *.ear ]::~~~

XOOPS SVN: https://sourceforge.net/p/xoops/svn/HEAD/tree/XoopsModules/signed/



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: https://sourceforge.net/p/chronolabs/tickets/?source=navbar
Quote:

Thank you for this module!
One thing I would like to know:
I agree to test the module and do my bug report but from the start, when going on your demonstration site and the debug mode is activated, you see many errors appear.
Why don't you go on your demonstration site see these mistakes and correct them, before proposing us your Module here?

Sure no worries, it has been a write up to versions unheard of before!!! 2.2 RC is the first release candidate we have asked for general testing...

See this URL: http://cipher.labs.coop/portfolio/signed-identification-validations-and-signer-for-xoops/

If people could start doing translations of the processes, this is to remain primarily a file store as the data is multiversal and the file base will be able to save all character escape sequences as well as all the file stores are text file base store so it eill transposer...

Yes we have heard of people with signed generating other certificate sequences just with the I-Ching XCP Checksum laid as so as the code is now just in the length it is and it dilettantes the lock for the certificate... yes yes that all true dsh!

I also completed the suffix and prefix to names... like dishonourable cause you might been that or need that for a hive your a part of in httpx:// xll+ssh://