home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.os.os2.apps:5963 comp.security.misc:1204
- Path: sparky!uunet!gatech!prism!gt1610c
- From: gt1610c@prism.gatech.EDU (MCGAUGH,MICHAEL KENNETH)
- Newsgroups: comp.os.os2.apps,comp.security.misc
- Subject: Re: Self-Extracting Binaries dangerous? (Was: REXXShip: Self-Extracting UUEncode!)
- Message-ID: <67843@hydra.gatech.EDU>
- Date: 8 Sep 92 21:44:18 GMT
- References: <1992Sep6.175645.24543@midway.uchicago.edu> <DENS.92Sep8074930@sawwhet.owlnet.rice.edu> <1992Sep8.151847.10060@midway.uchicago.edu>
- Followup-To: comp.os.os2.apps
- Organization: Georgia Institute of Technology
- Lines: 25
-
- In article <1992Sep8.151847.10060@midway.uchicago.edu> sip1@midway.uchicago.edu writes:
- >
- >It would be terrific, but, unless I'm mistaken, I'm forced to use
- >QUEUE statements, which prevents true xx-compatibility. If anyone has
- >any ideas on this, I'll be glad to do it for the next release.
- >
-
- Doesn't REXX have a command for reading its own source code?
- If it does, why not use that and then keep the xx-compatibility.
- Since REXX isn't compiled, you can put any garbage you want in
- the source and it doesn't matter as long as the interpreter never
- sees the junk. Have the first line of REXX code jump to the end
- of the file, where the uncompress code is. Then have the uncompress
- code read the source code in between, which happens to be the
- xx-compatible encoded information.
-
- Hope this works.
-
- Ken.
-
- --
- M. Ken McGaugh
- Georgia Institute of Technology, Atlanta Georgia, 30332
- uucp: ...!{decvax,hplabs,ncar,purdue,rutgers}!gatech!prism!gt1610c
- Internet: gt1610c@prism.gatech.edu
-