home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.pascal
- Path: sparky!uunet!cs.utexas.edu!torn!news.ccs.queensu.ca!dmurdoch
- From: dmurdoch@QueensU.CA (Duncan Murdoch)
- Subject: Re: code Scrambler?
- Message-ID: <Bs28AC.H8B@knot.ccs.queensu.ca>
- Sender: news@knot.ccs.queensu.ca (Netnews control)
- Organization: Queen's University, Kingston, Canada
- References: <31537@adm.brl.mil>
- Date: Mon, 27 Jul 1992 18:20:36 GMT
- Lines: 29
-
- In article <31537@adm.brl.mil> J_SCHULL@acc.haverford.edu (Jonathan Schull) writes:
- >
- >I'm developing a proprietary .TPU tool. I can't distribute the
- >source code, and want to make it difficult for hackers to be able
- >to reconstruct it by examining the .TPU file. Are there
- >utilities out there for scrambling variable names, before
- >compiling final source code, so that there are no recognizable
- >variable names available used as landmarks in the TPU?
- >
- >Other approaches to suggest?
-
- There aren't any names in a .TPU file that aren't necessary, if you
- compile it with the $D-,L- options. The only names you'll get are the
- names of interfaced symbols and the names of units which the .TPU uses.
- I don't think you'd want to scramble either of those.
-
- BTW, if you don't make source code available for your unit, there will
- be a large body of users (including me) who won't use it. The nature of
- the .TPU design is such that it's necessarily version-specific; if I
- don't have the source code for all third-party units, I'm stuck in a
- particular TP version. This doesn't mean you should give away source
- code, but please make it optionally available.
-
- One thing that would be useful for people in your position would be a
- source scrambler, that stripped comments and white space, and changed
- local names, but I've never seen one.
-
- Duncan Murdoch
- dmurdoch@mast.queensu.ca
-