From: Eric Armstrong Date: 2006-07-21T06:33:51+09:00 Subject: Re: "insecure world writable" fix ? Sean Harre wrote: > Hello All, > > I have come up with a fix/workaround which turns off the "insecure world > writable" warning message. > > In my code, I pass a string (exec_str) to exec: > > exec_str = "./foo.pl test" > exec(exec_str) > > Depending on my PATH, this can point out any number of world-writable > directories on my network. > > If I change the above so I'm just adding a CR to the end of exec_str, I > now do not see the warning message any longer: > > exec_str = "./foo.pl test\n" > exec(exec_str) > > Anyone have an idea why this works? > *Heck* of a workaround. Thanks. I look forward to explanations as to why it works. I've been using this: exec_str = "eval ''; ..." The initial eval also stops the insecure writable message. There's no way to modify the environment, either. Access ENV. causes the message to appear before I even try to execute anything in a subshell. That message is one heckofa mystery, to be sure.