The Unsigned Nature of it all and Signed 2.2RC for XOOPS

A few month ago I injured myself while developing open source titles for the popular framework I have been on the project teams (modules at the moment) since around 2007; I was stuck on the couch for 9 months until the ache which was like a programmer RSI Electric Shock, came on so sudden and I was unable to walk from the agony. I decided when I was well again I would spend the time on the couch planning a legal binder for online signatures; which is now in Release Candidate 2.2.

Part of the reason this is for example if you get an SSL Certificate all they do is validate your email and they don’t card you, therefore being a illegitimate verified signature, even for the fancy green square which all you do is sign a paper and they don’t validate any business documents or your physical signature. I get my ssl from btw. Anyway, you see those websites which ask you to input your name your intials and the date but this is also not validating any identification.

So I came up with the application Signed for psuedo-legal and psuedo-scientifically correct online signatures where the identification is presented as part of the API packages; this is then where a small detail of the signature is kept with signing an online document for verification, as well if some identification get flagged there is a callback which unsigned everything to do with that signature and when the identification (Which are randomly watermarked which is the best method as there is always duplicate visual interpretation when it is not random watermarked) is fixed and authenticated it will then go on the callback api and resign everything to do with that store signature.

Signed well entity or organisation signatures there are too many for any one individual or company to store; when an individual signature package is around 10Mb with images, ocr the lot; so I have written this system to be written into outter packagaes as well as a lead on to things like httpx:// with peer-to-peer reviewing and clustering rather than the problem with https:// and running out of IPv4 addresses so the certificate is portable and can be mounted on multiple places in security hives.

You can see Signed 2.2RC running in these locations:-

ANd you can get the source code as well as early none XOOPS variegates of this software from the chronolabs project on sourceforge here: Chronolabs – Browse /Encryption/Digital Signatures at