On Thu, Dec 30, 2010 at 11:02 AM, Theo de Raadt <dera...@cvs.openbsd.org> wrote: >> On Wed, Dec 29, 2010 at 6:08 PM, Ingo Schwarze <schwa...@usta.de> wrote: >> > I consider this a bug in security(8). >> > >> > The following is the best i could come up with so far; make sure >> > to wear your sed-peril-proof sunglasses before reading the patch. >> > >> > This still mangles the file name, but at least you have a chance >> > to find it on your disk. Anybody has a better plan? >> >> sed it back? assume blank is generally space, replace it with >> __omgspace__, then after sorting, replace that with a single space? >> It will still screw up for tabs and newlines, but I think spaces are a >> lot more common. > > It is starting to sound like slip/ppp escape protocol. > > A language which is more 8-bit capable should be used.
this is a half-thought-out idea, but can the script use file inodes so it doesn't have to futz with the file name? --patrick
