|
FOROS PROFESIONALES
WINDEV, WEBDEV y WINDEV Mobile |
| | | | | |
| Software protection serial code etc. |
| Iniciado por guest, 04,mar. 2009 14:17 - 6 respuestas |
| |
| | | |
|
| |
| Publicado el 04,marzo 2009 - 14:17 |
| I am looking for some sort of software protection sample for a PPC application. I could not find any so far. Any thoughs on that or sample code? |
| |
| |
| | | |
|
| | |
| |
| Publicado el 05,marzo 2009 - 01:10 |
I found this link http://www.pelock.com/ any ide if something like this could be integrated in to software dveloped by windev?
Thanks
Hans |
| |
| |
| | | |
|
| | |
| |
| Publicado el 05,marzo 2009 - 08:17 |
Hello Hans...
Protecting an app in mobile environment is not that different from protecting a regular windev app... And there is a course on protection (including source code) in my windev dvd... So if you are ready to code your own protection instead of buying an already done one, you have this source of information available (along with all the discussions on protections that we already had in this forum and in the old one)
Best regards |
| |
| |
| | | |
|
| | |
| |
| Publicado el 05,marzo 2009 - 08:18 |
Hi Hans,
PELOCK is 'wrapper'-type protection. Unfortunately, most wrappers do not work with WinDev software.
Any simple software type protection of programs is no good anyway. If the software is copied to another device and the 'key code' is used a second time you will not be able to know. In all cases where several pieces of the same equipment are used by the same customer (cash registers, mobile devices) the danger of multiple use of a single license is the highest one.
[color=#8B0000]There's only one way to protect software: in one way or another to bind it to a piece of hardware with a unique serial number in its firmware.[/color] The single relevant question is convenience of this type of software protection to the user and to the creator of the program.
As an example: Microsoft's protection of their Windows operating systems is bound to the hardware of the computer used. The plus: no extra hardware has to be distributed for software protection, the computer itself is the protection. The downside: You change one or two relevant pieces of the hardware and the OS will ask for licensing it once again.
As you can see easily, the main problem in binding software to existing hardware components (mainboard BIOS, hard disk, WinDev command ceOEMinfo() on WinCE / WinMobile devices etc) is changing / upgrading hardware by the customer. Customers could call and request a new unlock code by pretending that their old equipment went unusable. This happens to Microsoft as well and they do not prevent customers from installing that Vista or XP on a second computer - they simply cannot verify whether your old equipment just got a hardware upgrade or you installed the OS on a second computer.
So, since usage of dongles on mobile devices is a big no no, you have to put your protection as a stored procedure on the server! You can
1 - check whether the serial number (ceOEMinfo()) of any mobile device accessing the database is licensed for access. Means, you have to maintain a list of serial numbers on the server. If a device goes south, is destroyed, goes to the repair shop etc you have to add a new serial# and to remove the old one. You could use the Hyperfile C/S Control Center with remote access for that. One customer: no problem. 100 customers: a pain in the a..
2 - you don't care about how many different mobile devices are used with your software at all but you rather limit the number of devices with simultaneous access to the central database. Again, a stored procedure can check for the correct number of connected users and can refuse connection to devices exceeding the licensed number. You will have to distinguish between access of mobile devices and access of workstations of the LAN/WAN also.
Kind regards,
Guenter |
| |
| |
| | | |
|
| | |
| |
| Publicado el 05,marzo 2009 - 14:26 |
Hi Fabrice and Guenter,
as I am a beginner I thought it would be easier to implement a solid 3rd party solution instead of fighting my way trough a own self self made solution. I understand that a dongle may be a save way of doing it but that may not be suitable for PPC or some small piece of software thanks for your advice and info. I will have a closer look in to it.
Regards
Hans |
| |
| |
| | | |
|
| | |
| |
| Publicado el 14,marzo 2011 - 14:46 |
| |
| |
| | | |
|
| | |
| |
Miembro registrado
4 mensajes |
|
| Publicado el 02,febrero 2016 - 22:11 |
| |
| |
| | | |
|
| | | | |
| | |
| | |
| |
|
|
|