home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.os.os2.apps:5924 comp.security.misc:1175
- Path: sparky!uunet!utcsri!dgp.toronto.edu!flaps
- Newsgroups: comp.os.os2.apps,comp.security.misc
- From: flaps@dgp.toronto.edu (Alan J Rosenthal)
- Subject: Re: Self-Extracting Binaries dangerous? (Was: REXXShip: Self-Extracting UUEncode!)
- Message-ID: <1992Sep6.202133.26032@jarvis.csri.toronto.edu>
- References: <1992Sep6.025645.5101@midway.uchicago.edu> <18cf8rINNmpl@agate.berkeley.edu> <dank.715798089@blacks>
- Date: 7 Sep 92 00:21:34 GMT
- Lines: 15
-
- dank@blacks.jpl.nasa.gov (Daniel R. Kegel) writes:
- >Is it just me, or do other people shudder at the thought of
- >self-extracting binary archives? They seem dangerous to me
- >because they involve running a raw program straight off the net
- >without any visibility as to what it's doing.
- >
- >It seems safer to give everybody a copy of, say, uudecode. Perhaps
- >IBM could include it in their next release as a security enhancement
- >for those folks who would otherwise blindly run things off the net.
-
- It depends. What are you going to do with that thing after you uudecode it?
- If you're just going to run it right away, that's as big an opportunity as
- running it straight off the net. But if you're not going to run it (e.g. it's
- a star trek parody), then you're right, it's foolish to run a self-extracting
- program.
-