ionCube Logo
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 


 
Post new topic   Reply to topic    ionCube Forum Index -> ionCube PHP Encoder

Encorder issues for testing software

Author Message
mauger



Joined: 14 Jan 2005
Posts: 1
Location: Phoenix, AZ

PostPosted: Fri Jan 14, 2005 8:57 pm    Post subject: Encorder issues for testing software Reply with quote

We sell shopping cart software that is encoded with Ioncube for protection. When we deliver the download, we have to tie it to a domain name, server or IP address to protect the software.

The issue we run into frequently is when customers already have their website up and are not going to use our software. They don't want downtime on their site, so they want to set up our shopping cart on a test server and then move it over once it is complete. The obvious issue we have is that Ioncube won't allow this to occur because it is tied to the owners domain name.

Anyone have any solutions to this?

Mike
Back to top
View user's profile Send private message Visit poster's website
liaison
ionCube Support


Joined: 16 Dec 2004
Posts: 2788

PostPosted: Sun Jan 16, 2005 5:26 pm    Post subject: Reply with quote

Hi

Thanks for an interesting question. Firstly, this is really just a logistical issue, and not at all a restriction in ionCube. It simply comes down to how you use the Encoder and manage your product delivery. The Encoder is highly flexible, and you can encode scripts to run on as many domains and IP addresses as you like, and if you use Cerberus, also lock to MAC addresses. Therefore it's easily possible to lock your scripts to both their live system and also to a development machine.

Generally a test system will mirror a live system as closely as possible, at least it should, and so this would include the server name. Given this, you would be locking to a single domain name, but to more than one IP address. Using the command line option, and if their domain is www.foo.com with local IP 192.168.1.1, and live IP 60.70.80.90, then you might use:

--allowed-server www.foo.com@192.168.1.1,60.70.80.90

You might ask your customers before purchase whether they wish to use the software on a local machine too for testing purposes, and then acquire both IP's from them at time of purchase, ready for encoding.

Alternatively, you might provide a separately encoded copy for testing, with it's own server restriction, and appropriate comments that would appear in the encoded files. e.g.

--allowed-server www.foo.com@192.168.1.1 --add-comment "This version supplied to xxx strictly and exclusively for testing purposes"

so that the encoded files are branded as being for test purposes only.

If wishing to lock to more than a few IP's, you can also specify IP ranges, subnet masks, and partial IP addresses, to simplify things. You can also specify more than one server restriction, and so you might have

--allowed-server test.foo.com@192.168.1.1 --allowed-server www.foo.com@60.70.80.90

Hope this helps, and please feel free to post more on this topic if you have more queries or questions.

Nick
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic   Reply to topic    ionCube Forum Index -> ionCube PHP Encoder All times are GMT + 1 Hour
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum