home *** CD-ROM | disk | FTP | other *** search
/ NetNews Usenet Archive 1993 #1 / NN_1993_1.iso / spool / comp / lang / pascal / 8073 < prev    next >
Encoding:
Text File  |  1993-01-12  |  1.7 KB  |  37 lines

  1. Newsgroups: comp.lang.pascal
  2. Path: sparky!uunet!haven.umd.edu!purdue!yuma!hallch
  3. From: hallch@CS.ColoState.EDU (christopher hall)
  4. Subject: Re: CRC values in Turbo PASCAL
  5. Sender: news@yuma.ACNS.ColoState.EDU (News Account)
  6. Message-ID: <Jan12.140522.30619@yuma.ACNS.ColoState.EDU>
  7. Date: Tue, 12 Jan 1993 14:05:22 GMT
  8. References: <1993Jan6.202931.6292@cs.unca.edu> <1993Jan8.120512.15614dave@tygra.Michigan.COM> <93011.140320JDG111@psuvm.psu.edu>
  9. Nntp-Posting-Host: beethoven.cs.colostate.edu
  10. Organization: Colorado State University, Computer Science Department
  11. Lines: 24
  12.  
  13. In article <93011.140320JDG111@psuvm.psu.edu> JDG111@psuvm.psu.edu writes:
  14. >> Does anyone know how to calculate CRC values in pascal?
  15. >l know.  Of course, this method certainly isn't bulletproof, but it helps prote
  16. >ct your code from hacking or cracking.  
  17.  
  18. Actually no it doesn't.  All I would have to do if I were the person doing this
  19. is to change what I wanted to change in your executable, follow the CRC check
  20. with a debugger, and watch what value your check produces.  Then it should be
  21. a simple matter to encrypt that new number and place it over the old CRC value.
  22.  
  23. Let me know what you think.
  24.  
  25.                             Regards,
  26.                             Chris Hall
  27.  
  28.  
  29. /--------------------------------------------------------------------------\
  30. |    The world cannot end today because it is tomorrow in Australia...     |
  31. |                                                                          |
  32. |       |________          Chris Hall                                      |
  33. | ||OOO||________>         hallch@handel.colostate.edu                     |
  34. |       |                                                                  |
  35. \__________________________________________________________________________/
  36.  
  37.