 Topic  |
|
 Posted - Dec 31 2003 : 04:27:42
|
| How can your solutions be incorporated into my shopping cart which delivers pages on the fly? And which one? Please explain the differences. |
|
Posted - Dec 31 2003 : 04:32:21
|
Copysafe is very versatile. We currently provide it in two formats. One is a program that encrypts images, adds them to web pages which are then uploaded to any type of web server/site. The other is a server side solution that enables site visitors to upload images to a site which are encrypted and added to pages on the server. The site visitor (member) can log into their admin and add header/footer, extra copy, etc to individual pages or set standard headers for all of them.
Copysafe will also run on CD when using something like our
ArtistScope CD product which creates a mini web server that runs from an exe file.
Copysafe encrypted images are the more secure way to go, but another method in which a small Copysafe applet is added to the page header (using inserts) or added to the head of a frameset creates the same effect for browser control. When a Copysafe page is loaded into a web browser, the controls are effective in all open browser windows.
It is using this latter method that Copysafe can be added to any shopping cart/catalogue system whether it is written in Perl, Php or Asp. Because these products usually use inserts for headers and footers it is very simple to add Copysafe to all or selected pages. In fact I have just replied to one enquiry where the client wanted to allow saving/printing for a limited number of visits and also set the level of security according to the user's rights. This can also be done easily as Copysafe standard features allow/disallow print/save/capture according to the js file used in the insert... all he has to do is add his own scripts to his pages to check a database for hits/rights.
Copysafe would not be as secure if it was easily redistributable and thus have it's sources and methods known to every hacker in the world (such as with Msoft server products which can be purchased throughout Asia on CD for the price of a cup of coffee). Even the
plug-in itself is encrypted so that there is little clue visible as to how it all works. Its real security lies in what we call "domain lock" where the security applet will not function unless it
recognizes the site as being registered (images are encrypted according to a code based on the domain name of the site).
Ever since finding a freely
distributed key generator within weeks of our first release in 1998 we have been very conscious of the security of our products. Our Copysafe PBV solution for example is mostly written in Asp but the package is secure because it depends on an exe written in C which is domain locked... possibly an option for your top end products, but for now lets look at Copysafe as an add-on.
To add Copysafe to your shopping cart system for example, all we need to do is provide a couple of templates (one with a premade applet to match the site) which are added to your header and footer inserts, plus several js files. The js files control which level of security is used on a page.
You can check out some online demos of each of the methods described above at
demos or you can download a demo on
ArtistScope CD from
ArtisCD.zip
Both sets of demos show examples of the encrypted image method and the one using a Copysafe Insert (added to a page and also in a frameset).
Let me know what you think. |
 |
|
|
Topic |
|
|
|
Protecting shopping carts