| Customer Browsers |
 |
|
Browser scripts are encrypted to be site specfic for popular
current version browsers:
| |

|
Internet Explorer® |

|
Netscape® |
|
| |

|
FireFox |

|
Opera® |
|
|
| The customer sees the browser lock using the same SSL 128 bit online
encryption as Ebay® and Amazon® |
|
 |
|
| Vendor Computer |
 |
|
Win2000/XP/Vista with
Access 2000/2002/2003/2007
Supplied: Putty., PSFTP, PLINK, DETAR
Suggested: WinSCP for minor updates of the text data files on the server. |
 |
|
| Vendor Server |
 |
|
Redhat Linux
7.3/8.0 with Bash Shell, VDS hosting, or UNIX/Linux equivalent;
Perl 5.6/5.8, SSH, SFTP;
Apache 1.3/2.0 with SSI-Server Side Includes (NoExecs) and Mod Perl. |
|
|
| Gateways |
 |
NetBilling: Includes
automatic membership signup for recurrent billing |
|
PayPal®: OPENSSL
for Linux/Unix for button encryption if used |
|
TrustCommerce®: recurrent billing option included;
requires tclink-perl-3.4.1.tar.gz |
|
Secure Version: For collection of credit card #'s on
your ISP server. A 2048 bit
public-private key, OEAP padding, and a well known algorithm
subject of US patent #4,405,829 by Rivest,
Shamir, and Adleman which expired Sept 20, 2000.
Requires CPAN; INLINE::C, INLINE::CPP (includes Parse-RecDescent,Text-Balanced). This is
advanced encryption. Export
controls or local restrictions may apply for some jurisdictions. Windows Security Audit and user logging must be enabled
on the vendor client. If HardHat Hosting is not used, requires Perl 5.6 may require
re-compilation of libcryptopp.a with gcc2.96 (i.e RedHat 7.3). |
|
|
| Store Size |
 |
|
Small Store
for up to suggested 500 products maximum. The order summary page uses a single data file
making it lightning fast. |
|
|
|
Large Store for greater than 500 products. The order summary pages
use a timer frame to assemble the order summary data from the selected categories data
files overcoming the constraint of a large single data file on a slow network. |
|
|
| Security |
|
 |
 |
The database uses internally
encrypted case sensitive users passwords to guard customer information. The Admin user
manages User accounts to optionally enforce user password expiry ...
As well, the Admin user can Preview, Print and Delete the User Access Log. |
 |
The database records include last
update time for cross reference with the User Access Log. |
 |
Once payment has been received, the
credit card number is deleted from the database and order record upon confirmation. |
 |
Order calculations
done on the client browser are verified by the current values in the data base on the
"Edit Order Form" |
 |
Upload of the Store
and download of the orders are handled by the client data base using Putty, a secure SSH2
client, so the vendor's server account and password are not compromised. |
 |
The entire order process can be
made securely (https) using less server and network resources than page loading shopping
carts on non-secure (http) connections. |
 |
Site coupon codes are encrypted to
be non-readable. |
 |
Browser JavaScripts are encrypted
to be domain specific preventing site spoofing. |
|
|
|
|