but guys what will stop the users from decompiling the class files and still figure out your tricks and the keys staff? may be you can explain more on "obfusticate"
-----Original Message----- From: SAMINATHAN [mailto:[EMAIL PROTECTED]] Sent: Sunday, April 28, 2002 11:02 PM To: [EMAIL PROTECTED] Subject: Re: prevent cracking my class files This is what exactly we are looking for.Thanks a lot. Thanks and Regards Saminathan. ----- Original Message ----- From: "Keith Sterling" <[EMAIL PROTECTED]> To: "'SAMINATHAN'" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Monday, April 29, 2002 11:01 AM Subject: RE: prevent cracking my class files > > What you are looking for is full copy protection. We use Rainbow > Technologies http://www.rainbow.com/ License Manager > > This is a server that runs on the network and checks how many copies are > running. If each of you applications cannot talk to the server then they > won't start up. > > They key is generated by using taking a snap shot of the hardware the server > is running on, customers send this back to us during install, and we send > them back a full license key. We normally include a 30 day eval license so > that non UK customers are not hit with time zone problems trying to contact > us > > In addition we obfusticate all our code to stop reverse engineering > > Both work well and stop any form of copying > > ------------------------------------------------------------------------- > Keith Sterling > Jacobs Rimell > VP of Engineering > > Jacobs Rimell Ltd > 24 Chiswell St > London EC1Y 4TY > Tel : +44 207 786 4000 > Mob : +44 7771 597 630 > Fax : +44 207 786 4004 > http://www.jacobsrimell.com > ------------------------------------------------------------------------- > IMPORTANT NOTICE: > This email is confidential, may be legally privileged, and is for the > intended recipient only. If you are not the intended recipient, please > inform the sender and delete the email immediately. > WARNING: > It is impossible to guarantee the content of this message when it is > delivered across the internet, therefore the sender accepts no liability > for any claims arising from the information contained. > > > -----Original Message----- > From: SAMINATHAN [mailto:[EMAIL PROTECTED]] > Sent: 29 April 2002 05:59 > To: [EMAIL PROTECTED] > Subject: Re: prevent cracking my class files > > We also facing some kind of similar issue but in our case we want to > restrict of installation.If client buys for 5 user license we don't want to > allow more than 5 people accessing our server. > > bye > Saminathan. > > ----- Original Message ----- > From: "Ramesh" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Monday, April 29, 2002 10:17 AM > Subject: Re: prevent cracking my class files > > > > hi > > u want just disable re-engineering or to disable unauthorized > copying?? > > Using obfuscators available in market you can make re-engineering > difficult. > > To disable unauthorized copying a combination of techniques can be used. > One > > such technique is to generate a key for each distribution and write a > > separate > > class loader to load and check this generated key in the main class if it > is > > tampered exit the program. > > thanks > > ramesh > > > > -----Original Message----- > > From: A mailing list for Enterprise JavaBeans development > > [mailto:[EMAIL PROTECTED]]On Behalf Of Kesav, Ramesh > > Sent: Monday, April 29, 2002 9:49 AM > > To: [EMAIL PROTECTED] > > Subject: prevent cracking my class files > > > > > > > > Hi all, > > > > i have a product being developed for Chartered Accountants. It is a > swing > > application.Now i want to sell the product to various parties but i do not > > want them to crack my class files. > > I had 2 ideas > > 1) first i will convert these class files into executables but i heard > that > > javatoexe is not the appropriate one. > > 2) secondly i thought of writing this class files into a cd and somehow i > > need to put a cd key in it.how to do this. > > > > any other suggestions are mostly welcome. > > > > Regards > > > > Ramesh Kesavanarayanan > > [EMAIL PROTECTED] > > > > > =========================================================================== > > To unsubscribe, send email to [EMAIL PROTECTED] and include in the > body > > of the message "signoff EJB-INTEREST". For general help, send email to > > [EMAIL PROTECTED] and include in the body of the message "help". > > > > > =========================================================================== > > To unsubscribe, send email to [EMAIL PROTECTED] and include in the > body > > of the message "signoff EJB-INTEREST". For general help, send email to > > [EMAIL PROTECTED] and include in the body of the message "help". > > =========================================================================== > To unsubscribe, send email to [EMAIL PROTECTED] and include in the body > of the message "signoff EJB-INTEREST". For general help, send email to > [EMAIL PROTECTED] and include in the body of the message "help". =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help". =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
