1
wishcraft
Digitally Signed for XOOPS 2.5 ~~ A Legal Solution by Chronolabs Cooperative - http://labs.coop

Resized Image
Digitally Signed for XOOPS 2.5
A Legal Solution by Chronolabs Cooperative - http://labs.coop


Module: Self Signed
Version 1.12
Bug Tracking: https://sourceforge.net/p/chronolabs/tickets/?source=navbar
Discussion: https://sourceforge.net/p/chronolabs/discussion/?source=navbar

Synopsis:~


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://signed.labs.coop 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 3x3 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:~

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 http://xoops.signed.code.labs.coop as well as seeming the api at http://xoops.signed.code.labs.coop/modules/signed/api/

Quote:
Username: letmein
Password: roundhouse
URL: http://xoops.signed.code.labs.coop


Downloads:~

It has been committed to the XOOPS SVN as 1.12 Final Major the downloads are the following URLS:--

*.7z :: http://sourceforge.net/projects/chronolabs/files/Encryption/Digital%20Signatures/xoops2.5-signed-1.12.7z/download -- 571.2 kB
*.zip : http://sourceforge.net/projects/chronolabs/files/Encryption/Digital%20Signatures/xoops2.5-signed-1.12.zip/download -- 1.0 MB
*.tar :: http://sourceforge.net/projects/chronolabs/files/Encryption/Digital%20Signatures/xoops2.5-signed-1.12.tar.gz/download -- 849.1 kB

2
wishcraft
Re: Digitally Signed for XOOPS 2.5 ~~ A Legal Solution by Chronolabs Cooperative - http://labs.coop

If your looking for the XOOPS_ROOT_PATH .htaccess it is as follows as an example, remember to turn it on in the script as well as with apache2:

RewriteRule ^signer/(.*?)$ modules/signed/$1
     RewriteRule 
^signing/(.*?)$ modules/signed/api/$1

3
Dante7237
Re: Digitally Signed for XOOPS 2.5 ~~ A Legal Solution by Chronolabs Cooperative - http://labs.coop
  • 2014/11/21 3:30

  • Dante7237

  • Friend of XOOPS

  • Posts: 294

  • Since: 2008/5/28


I'm sorry dude, but I've tried to use your mods and am only going to say that I would rather self install DarkComet on my root directory with open access than trust any of your code.


4
wishcraft
Re: Digitally Signed for XOOPS 2.5 ~~ A Legal Solution by Chronolabs Cooperative - http://labs.coop

Alot of those module where mainly written in 2.4 of XOOPS and the structure of XOOPS 2.5 has changed between 2.5.1 and 2.5.7 -- if you use the discussion on or raise tickets on the http://sourceforge.net/projects/chronolabs the bugs if and when they exist will get fixed...

It is part of the communities responsibility to report this sort of thing, I do not being the only programmer in chronolabs currently have time to review them or and need peer-review from my clients you people at XOOPS...

5
wishcraft
Signed 1.14 is ready for testing for first release!

Self Signed 1.14 -- is a psuedo-scientific and psuedo-legal correct method of signing documents online... I have extensively tested this and in 3 minor version this seem to be the right one for this release in series 1.1.

You can download it from:~ Digital Signatures

You can see this module operating on:--


I have started planning version 2.xx which will include all the file resources being encrypted in the RAW File stores.. The database which is designed to be minimal as the signature data is stored in flat files will probably not expand much out of the following:~


CREATE TABLE `signed_signatures` (
  `
signid`      mediumint(16unsigned  NOT NULL auto_increment,
  `
state`       enum('active''inactive''progress''expired'NOT NULL default 'progress',
  `
type`          varchar(128)            NOT NULL default '',
  `
serial`        varchar(42)             NOT NULL default '',
  `
bytes`         int(24unsigned        NOT NULL default '0',
  `
entity`      varchar(255)            NOT NULL default '',
  `
name`          varchar(255)            NOT NULL default '',
  `
file`          varchar(255)            NOT NULL default '',
  `
path`          varchar(255)            NOT NULL default '',
  `
method`       enum('json''serial''xml'NOT NULL default 'json',
  `
saltid`       mediumint(19unsigned  NOT NULL default '0',
  `
expires`       int(13unsigned         NOT NULL default '0',
  `
expired`       int(13unsigned         NOT NULL default '0',
  `
saved`         int(13unsigned         NOT NULL default '0',
  `
issued`         int(13unsigned         NOT NULL default '0',
  `
used`       int(13unsigned         NOT NULL default '0',
  `
flagged`       int(13unsigned         NOT NULL default '0',
  `
group`        varchar(42)             NOT NULL default '',
  `
uid`       int(13unsigned         NOT NULL default '0',
  `
zoneid`       mediumint(19unsigned  NOT NULL default '0',
  
PRIMARY KEY  (`signid`),
  
KEY `hash` (`state`, `type`(19), `entity`(9), `name`(9), `group`(13), `signid`),
  
KEY `meters` (`expires`, `expired`, `saved`, `issued`, `used`, `flagged`, `uid`, `method`, `saltid`, `zoneid`, `signid`),
ENGINE=INNODB;

CREATE TABLE `signed_events` (
  `
eventid`            mediumint(19unsigned  NOT NULL auto_increment,
  `
system`          varchar(128)            NOT NULL default '',
  `
type`              varchar(128)            NOT NULL default '',
  `
comment`            text,
  `
key`            varchar(42)             NOT NULL default '',
  `
uid`           int(13unsigned         NOT NULL default '0',
  `
begun`           int(26,17unsigned        NOT NULL default '0',
  `
finish`           int(26,17unsigned        NOT NULL default '0',
  `
took`           int(26,17unsigned        NOT NULL default '0',
  `
group`            varchar(42)             NOT NULL default '',
  `
uid`             int(13unsigned        NOT NULL default '0',
  `
began`           int(13unsigned         NOT NULL default '0',
  `
micro`             int(13unsigned         NOT NULL default '0',
  `
log_storage`       enum('json''serial''xml'NOT NULL default 'json',
  `
log_path`          varchar(255)            NOT NULL default '',
  `
log_file`          varchar(255)            NOT NULL default '',
  `
log_saltid`       mediumint(19unsigned  NOT NULL default '0',
  `
zoneid`           mediumint(19unsigned  NOT NULL default '0',
  
PRIMARY KEY  (`eventid`),
  
KEY `hash` (`key`(13), `group`(13), `type`(11), `system`(9), `eventid`),
  
KEY `meters` (`uid`, `begun`, `finish`, `took`, `zoneid`, `eventid`),
ENGINE=INNODB;

CREATE TABLE `signed_event_links` (
  `
linkid`            mediumint(33unsigned  NOT NULL auto_increment,
  `
group`            varchar(42)             NOT NULL default '',
  `
when`             int(13unsigned        NOT NULL default '0',
  `
signid`          mediumint(12unsigned  NOT NULL default '0',
  `
eventid`            mediumint(19unsigned  NOT NULL default '0',
  `
zoneid`           mediumint(19unsigned  NOT NULL default '0',
  
PRIMARY KEY  (`linkid`),
  
KEY `hash` (`when`, `key`(13), `group`(13), `signid`(11), `eventid`, `linkid`),
ENGINE=INNODB;

## Table for secondary copy of file salts for security
CREATE TABLE `signed_salts` (
  `
saltid`            mediumint(19unsigned  NOT NULL auto_increment,
  `
type`              varchar(128)            NOT NULL default '',
  `
algorithm`       varchar(128)            NOT NULL default 'AES',
  `
filename`          varchar(255)            NOT NULL default '',
  `
path`              varchar(255)            NOT NULL default '',
  `
method`           enum('json''serial''xml'NOT NULL default 'json',
  `
salt`           tinytext,
  `
refeshed`           int(26,17unsigned        NOT NULL default '0',
  `
zoneid`           mediumint(19unsigned  NOT NULL default '0',
  
PRIMARY KEY  (`saltid`),
  
KEY `hash` (`type`(13), `algorithm`(13), `filename`(11), `path`(9), `saltid`),
  
KEY `meters` (`method`, `refeshed`, `zoneid`, `saltid`),
ENGINE=INNODB;

## Table for Date Zoning and Chronologicist!
CREATE TABLE `signed_zones` (
  `
zoneid`            mediumint(19unsigned  NOT NULL auto_increment,
  `
zone`              varchar(128)            NOT NULL default 'Australia/Sydney',
  `
metrix`           int(18)                NOT NULL default '0',
  
PRIMARY KEY  (`zoneid`),
  
KEY `xonier` (`zone`(13), `metrix`(13), `zoneid`),
ENGINE=INNODB;


I will be using my storage.php class and modifying the IO class so it crypts and decrypts on the fly, this will when you upgrade it encrypt all your datastores and backup the keys in the database..

The class I am talking about is this one:~ io.php + RadiooCrypt.php both of these are part of another new module for people to have streaming playlists and radios on there portal, this is called Radioo the module, next one when this one is finished, then the chat rooms xAlky.

Thanks

Simon/Alesha

Login

Who's Online

396 user(s) are online (271 user(s) are browsing Support Forums)


Members: 0


Guests: 396


more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: Nov 30
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits