Open Access Open Access  Restricted Access Subscription Access

Inhibition to Software Piracy Using Challenging Response Protocol


 

In todays IT World main approach of software developer is to prevent the software piracy. Lots of implementations are done to prevent software piracy. So, many ideas are suggested to stop it. In this paper we are presenting an approach, which based on SMS Gateway System. The server initiates the authentication process and identifies the genuine copy software on client machine. In brief we are implementing a general key distribution system, which provides the maximum inhibition to software piracy. In which server starts the process by sending the authentication challenge to client then client will response to the challenge and server will verify the response. After getting expected reply from client, server will send status message to client according to that client machine will decides what should be done next. After getting proper output from client side server send either success or failure status. At the end software installation process starts or software uninstallation process starts.


User
Notifications
Font Size

Abstract Views: 124

PDF Views: 0




  • Inhibition to Software Piracy Using Challenging Response Protocol

Abstract Views: 124  |  PDF Views: 0

Authors

Abstract


In todays IT World main approach of software developer is to prevent the software piracy. Lots of implementations are done to prevent software piracy. So, many ideas are suggested to stop it. In this paper we are presenting an approach, which based on SMS Gateway System. The server initiates the authentication process and identifies the genuine copy software on client machine. In brief we are implementing a general key distribution system, which provides the maximum inhibition to software piracy. In which server starts the process by sending the authentication challenge to client then client will response to the challenge and server will verify the response. After getting expected reply from client, server will send status message to client according to that client machine will decides what should be done next. After getting proper output from client side server send either success or failure status. At the end software installation process starts or software uninstallation process starts.