You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Rob Hartill <ro...@imdb.com> on 1996/12/05 12:56:39 UTC

WWW Form Bug Report: "Problem with comment "eval" on "sh"" on OSF/1 (fwd)

----- Forwarded message from develop@vaxxine.com -----

Message-Id: <19...@taz.hyperreal.com>
From: develop@vaxxine.com
To: apache-bugs%apache.org@organic.com
Date: Wed Dec  4 22:13:09 1996
Subject: WWW Form Bug Report: "Problem with comment "eval" on "sh"" on OSF/1

Submitter: develop@vaxxine.com
Operating system: OSF/1, version: 2.0
Version of Apache Used: 
Extra Modules used: 
URL exhibiting problem: 

Symptoms:
--
This is in followup to a bug report submitted earlier concerning the use of "eval" on a comment in PrintPath.  I have included a short sample script which verifies the problem in OSF/1.  The shell groes to consume all available memory in the system.  Please forward it to any developers that may be interested.  
I sent a modified PrintPath by e-mail earlier
that merely eliminated the chance of "eval #".
Thank you for your help concerning this problem  - Apache's the tops. :)
--

Backtrace:
--
#! /bin/sh

# 'ty' can actually be set to anything - file,
# directory, junk value, etc., so it doesn't
# appear to be some kind of weird "I'll try
# and execute the directory" thing.

tx=#
ty=/tmp

eval $tx $ty
--

----- End of forwarded message from develop@vaxxine.com -----

-- 
Rob Hartill.       Internet Movie Database Ltd.    http://www.imdb.com/