RE: Anyone Interested in an A5 DB Security Add-in
Yes, I am very interested. But first let's make sure we are talking the same language here.
What I, and I believe many other Alpha Five developers, will want is a way to protect their intellectual property rights as represented in a Alpha Five application that they have developed. Therefore, I want these two things:
1. my Alpha Five source to be protected against unauthorised disclosure and modification and/or re-use; and
2. my Alpha Five application protected against unauthorised duplication and re-use.
And I want these two things done without excessive intrusion into my customers fair use of my application. So, for example, I consider product activation (a la Microsoft's model as implemented in Win XP and Office XP) to be overly intrusive from my customers' viewpoint and, from my viewpoint as the developer, administratively excessively cumbersome, so I don't want this.
How do I see application protection working then? I think protection based on a product registration id (unique to each copy of my application) combined with a customer supplied phrase (personal name, company name, email address or the like) to generate a secure non-reproducible registration key (which might be a hex code 30 digits in length for example) would probably work OK. It needs to be supported by a process to enable developers to record the registration details of their customers. So an Alpha Five product registration database application will be required here. (A business opportunity for someone?)
There will also need to be a way of presenting a "trial version" registration id so that all features of the application may be used for a set period, say up to 15, 30, 60 or 90 days and then selected features disabled until a valid registration key is supplied following purchase.
I'll stop here. Hopefully, someone from Alpha Software will read this and provide some more details on how they are proposing to implement application security and registration so we can be sure we are all talking the same language.
Yes, I am very interested. But first let's make sure we are talking the same language here.
What I, and I believe many other Alpha Five developers, will want is a way to protect their intellectual property rights as represented in a Alpha Five application that they have developed. Therefore, I want these two things:
1. my Alpha Five source to be protected against unauthorised disclosure and modification and/or re-use; and
2. my Alpha Five application protected against unauthorised duplication and re-use.
And I want these two things done without excessive intrusion into my customers fair use of my application. So, for example, I consider product activation (a la Microsoft's model as implemented in Win XP and Office XP) to be overly intrusive from my customers' viewpoint and, from my viewpoint as the developer, administratively excessively cumbersome, so I don't want this.
How do I see application protection working then? I think protection based on a product registration id (unique to each copy of my application) combined with a customer supplied phrase (personal name, company name, email address or the like) to generate a secure non-reproducible registration key (which might be a hex code 30 digits in length for example) would probably work OK. It needs to be supported by a process to enable developers to record the registration details of their customers. So an Alpha Five product registration database application will be required here. (A business opportunity for someone?)
There will also need to be a way of presenting a "trial version" registration id so that all features of the application may be used for a set period, say up to 15, 30, 60 or 90 days and then selected features disabled until a valid registration key is supplied following purchase.
I'll stop here. Hopefully, someone from Alpha Software will read this and provide some more details on how they are proposing to implement application security and registration so we can be sure we are all talking the same language.
Comment