Support Forums - All Posts - XOOPS Web Application System

121

API from labs.coop v1.1 release -- Needing a hooking stratum

2014/12/11 11:33
wishcraft
Module Developer
Posts: 3711
Since: 2007/5/18

To the Core Dev,

How are you greg? how have you been, noted and true your bulked down in 2.6, something we need to add too it before release is like modules a /api path that can also be assigned to a sub directory...

it should path internal within or without API hooks possibly with a query instruction file based on the following I have developed outside XOOPS so they sit in flawlessly.

I have a couple more API's too finish off which I will be working on tonight and over the next week, see I am and decided with our moderator mamba being quite shinny and like a being of light, too only code at night after sunset on the continent which is after 8pm AEST but the couple of API's left to do are the following:--

jquery - a jquery strapping stratum (self updating)
identity - a sessioning identity giver
fonts - an API for font services

The APIS currently available from here to download now:--

agents - User agent detector
why - why querism
places - geolocality locations
spline - google places splining
time - time ticket provider
seed - random seed provider
translators - translators
whitelist - API whitelisting
whois - IPv4, IPv6 & TLD Whois
spots - geolocality spots of interest
screening - toxicology or random person selector
lookups - IPv4 & IPv6 lookups
icons - Icons API provider
life - Radio streaming media provider
hashing - hashinfo checksumer
css - CSS provider API

I will come up with a packing method for XOOPS for /api/ off the XOOPS_ROOT_PATH that will be similar to modules that will use similar system and when I have finished 'example' I will let you roll the code as I am still having the issues of having a module perfect and then uploading and suddenly something in the DEJ puts an error in it... so that is why there are a few releases normally it like a physical attack from makinghttps://xortify.com which should yes be bundled with 2.6 most certainly as it has reached the end of it current incarnation as the dev for XOOPS... maybe you can add some method with it for SPAM checking as well... It is a complementary package to GIJOE's protector..

--> good point I will put them on the SVN in Third party when I have a scheme for XoopsAPI on the SVN I will submit it in that category to Git and there... np

122

Signed 1.14 is ready for testing for first release!

2014/12/9 4:37
wishcraft
Module Developer
Posts: 3711
Since: 2007/5/18

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:--
www.hempembassy.net
www.xortify.com

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(16) unsigned  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(24) unsigned        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(19) unsigned  NOT NULL default '0',

  `expires`       int(13) unsigned         NOT NULL default '0',

  `expired`       int(13) unsigned         NOT NULL default '0',

  `saved`         int(13) unsigned         NOT NULL default '0',

  `issued`         int(13) unsigned         NOT NULL default '0',

  `used`       int(13) unsigned         NOT NULL default '0',

  `flagged`       int(13) unsigned         NOT NULL default '0',

  `group`        varchar(42)             NOT NULL default '',

  `uid`       int(13) unsigned         NOT NULL default '0',

  `zoneid`       mediumint(19) unsigned  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(19) unsigned  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(13) unsigned         NOT NULL default '0',

  `begun`           int(26,17) unsigned        NOT NULL default '0',

  `finish`           int(26,17) unsigned        NOT NULL default '0',

  `took`           int(26,17) unsigned        NOT NULL default '0',

  `group`            varchar(42)             NOT NULL default '',

  `uid`             int(13) unsigned        NOT NULL default '0',

  `began`           int(13) unsigned         NOT NULL default '0',

  `micro`             int(13) unsigned         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(19) unsigned  NOT NULL default '0',

  `zoneid`           mediumint(19) unsigned  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(33) unsigned  NOT NULL auto_increment,

  `group`            varchar(42)             NOT NULL default '',

  `when`             int(13) unsigned        NOT NULL default '0',

  `signid`          mediumint(12) unsigned  NOT NULL default '0',

  `eventid`            mediumint(19) unsigned  NOT NULL default '0',

  `zoneid`           mediumint(19) unsigned  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(19) unsigned  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,17) unsigned        NOT NULL default '0',

  `zoneid`           mediumint(19) unsigned  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(19) unsigned  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

123

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

2014/11/24 9:50
wishcraft
Module Developer
Posts: 3711
Since: 2007/5/18

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 thehttp://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...

124

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

2014/11/21 0:49
wishcraft
Module Developer
Posts: 3711
Since: 2007/5/18

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

125

syndipay.com -- About this Unique Syndisolution!

2014/11/20 17:28
wishcraft
Module Developer
Posts: 3711
Since: 2007/5/18

Syndipay.com is going to be a interglobalised invoicing & payment solutions for you and third parties; as well as your business clients or if your a single staff member and need to run invoices, this is the place to start and hop on!

Syndipay.com is a interglobal payment system, for a group of business which use the web for business and consultancy processes. It has been a growing business in online payments that utilises the very best of open business and open source to provide the delivery of invoice and payment topologies on the web.

If your using a Syndipay.com business you know they have passed all our quality of care investigations and have been identified as a highly ethical and fraud free business practises.

I have been working on this off and on to centralise billing in my web design business... I am using a gateway and already have all the merchant facilities organised..

126

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

2014/11/20 17:03
wishcraft
Module Developer
Posts: 3711
Since: 2007/5/18

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

127

Eight Months' break time for in-looue to come off holidays

2014/11/16 16:18
wishcraft
Module Developer
Posts: 3711
Since: 2007/5/18

Hi how are you all? I hope you are well and all is good, I have started up again after taking a number of months off on holidays from the project... In a week or two I will be release consectively in one hit the following new modules

Signed 1.xx ~ based onhttp://signed.labs.coop -- online legal signature system for identification and sealing an aggreement! {See: XOOPS SVN}
Radioo 1.xx ~ radio stations for your web clients {See:~ XOOPS SVN for Alpha}
xAlky 1.xx ~ IRC Style chat rooms based onhttp://chat.labs.coop {See:~ XOOPS SVN for Alpha}

128

Online Digital Signatures v1.11 (RC) ~ Signed 1.11

2014/10/4 23:25
wishcraft
Module Developer
Posts: 3711
Since: 2007/5/18

Digital Online Signatures for XOOPS 2.5

Yes I believe a return to self peer reviewed signing is possible with httpx://. Do you notice how people when you get a SSL Certificate say yes yes all balanced and check, but if they are giving you the signature, they don't even take your Identification. Well this is one step closer to httpx:// the part were you create your own personal or business entity seal for signing things online.

It covers all scopes of the serious lack of integrity and Dodecanese of online in-security.. For example you would not put your interstitials to sign a document as Initials in one box, then name and date, it has not a signal of viewable integrity, with this it has an API so you say at a website put in the details of class one or two of the signature and it would provide that site with your stored identification.

This is a version of signed.labs.coop for XOOPS 2.5 it is from the Final minor release I wrote and for signing legal clauses, aggrandisement, contracts anything online correctly and with all fundamental balances in check.

Discussion: Chronolabs Source-forge Forums
Bug & Issues Tickets: Report issues here about a Buggy Software Issues!
Download: xoops2.5_signed_1.11-RC.tar.gz - 1.8Mb
(*.zip ~ 2.1mb) (*.7z ~ 1.2mb) (*.rar ~ 1.9mb)

129

Xortify 4.99 (Final Minor Release) for XOOPS 2.5.7

2014/9/1 14:23
wishcraft
Module Developer
Posts: 3711
Since: 2007/5/18

Xortify 4.99 is in it ready and final minor revision release. I appologies if you have been attempting to use the honeypot over the last 4 months as I have been developing a Word press client for it called Wortify which is also in final. This is a revisit to the code and fixing of some minor bugs for signup such as changes to the templating system in XOOPS 2.5.x namely in 2.5.7.

This would have not meant you were able to sign-up to the cloud, which is sponsored by Arck Interactive as previous historical corridors!

The cloud portal has more information on it see:https://xortify.com - The Portal/Cloud has been cleaned up a bit as well with bolder fonts as well as IP Sec standardisation for URL's etc. There is also an option on their if you want to send someone or a group of emails a mailer about it should it be of interest?

Changelog is:

[size=xx-small]========================================
2014/09/01 23:57:19 Version 4.99
========================================
- Changed /admin/index.php - fixed templates being loaded! (wishcraft)
- Changed /admin/menus.php - fixed image paths for control panel! (wishcraft)
- Changed /class/curl(*.?).php - added CURLOPT_VERBOSE, CURLOPT_SSL_VERIFYHOST & CURLOPT_SSL_VERIFYPEER (Wishcraft)
- Changed /class/rest_curl(*.?).php - added CURLOPT_VERBOSE, CURLOPT_SSL_VERIFYHOST & CURLOPT_SSL_VERIFYPEER (Wishcraft)
- Changed /class/auth/curl(*.?).php - added CURLOPT_VERBOSE, CURLOPT_SSL_VERIFYHOST & CURLOPT_SSL_VERIFYPEER (Wishcraft)
- Changed /class/auth/rest_curl(*.?).php - added CURLOPT_VERBOSE, CURLOPT_SSL_VERIFYHOST & CURLOPT_SSL_VERIFYPEER (Wishcraft)
- Added /images/icons/32/home.png localised source (Wishcraft)
- Added /images/icons/32/about.png localised source (Wishcraft)[/size]

Places to communicate:

* Xortify Social Center –http://facebook.com/xortify/
* Xortify Support Tickets –https://sourceforge.net/p/xortify/tickets/ (Report Bugs)
* Xortify Wiki –https://sourceforge.net/p/xortify/wiki/Home/
* Xortify Discussion Forums -https://sourceforge.net/p/xortify/discussion/

Xortify Client Downloads:

* XOOPS 2.5.x (zip) –http://sourceforge.net/projects/xortify/files/XOOPS/xoops2.5_xortify_4.99.zip/download
* XOOPS 2.5.x (7z) –http://sourceforge.net/projects/xortify/files/XOOPS/xoops2.5_xortify_4.99.7z/download
* XOOPS 2.5.x (tar.gz) –http://sourceforge.net/projects/xortify/files/XOOPS/xoops2.5_xortify_4.99.tar.gz/download
* XOOPS 2.5.x (rar) –http://sourceforge.net/projects/xortify/files/XOOPS/xoops2.5_xortify_4.99.rar/download

130

#GPL/#GNU Licence Key’s should assign on Install (Finally at your home! Big Plus+++)

2014/7/19 13:18
wishcraft
Module Developer
Posts: 3711
Since: 2007/5/18

I firmly believe just like when you ‘purchase’ a closed source package and receive a licence key for your unique DJ Set with that title of software and your Record player Hard drive. Open source like GNU2, GNU3, GPL2, GPL3, NMC, etc. Should also assign and output on install definitely from what I experience with one with and one without in XOOPS 2.3, 2.4 then with one added in XOOPS 2.5 were it was just you and the whole world and your website!

Resized Image

Watch: https://www.youtube.com/watch?v=cszSzx7qZ78

Stats
Goal:	$100.00
Due Date:	May 31
Gross Amount:	$0.00
Net Balance:	$0.00
Left to go:	$100.00

Forum Index

API from labs.coop v1.1 release -- Needing a hooking stratum

Signed 1.14 is ready for testing for first release!

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

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

syndipay.com -- About this Unique Syndisolution!

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

Eight Months' break time for in-looue to come off holidays

Online Digital Signatures v1.11 (RC) ~ Signed 1.11

Xortify 4.99 (Final Minor Release) for XOOPS 2.5.7

#GPL/#GNU Licence Key’s should assign on Install (Finally at your home! Big Plus+++)

Login

Search

Recent Posts

Re: Rebuilding and Updating a 20 years old Xoops Website from 2.0.18? to 2.5.11

Rebuilding and Updating a 20 years old Xoops Website from 2.0.18? to 2.5.11

Re: NewBB v 5.1.0 b 6

Re: NewBB v 5.1.0 b 6

NewBB v 5.1.0 b 6

Re: XOOPS 2.5.11 search user is not working

Re: oledrion

Re: oledrion

Re: oledrion

Re: oledrion

Who's Online

Donat-O-Meter

Latest GitHub Commits

{{ record.sha.slice(0, 7) }} - {{ record.commit.message | truncate }}