[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: bin/41764: ksh has suffered serious regressions in the past few years
The following reply was made to PR bin/41764; it has been noted by GNATS.
From: Robert Elz <kre%munnari.OZ.AU@localhost>
Subject: Re: bin/41764: ksh has suffered serious regressions in the past few
Date: Fri, 24 Jul 2009 04:44:14 +0700
Date: Thu, 23 Jul 2009 20:15:04 +0000 (UTC)
From: "Greg A. Woods" <woods%planix.com@localhost>
| The code as it was existed in NetBSD's 1.6.x and 2.0.x, and 2.1, and I
| don't recall anyone complaining of any actual crashes involving it.
It may be almost (or completely) impossible to get a string ending with a
backslash into ksh (or that part of it anyway) - just perhaps, if you have
a potentially affected binary, you could try something like
eval echo $x
and see what happens, that'sjust about the only way I can imagine it getting
This kind of thing isn't something an average user would likely encounter...
Main Index |
Thread Index |