Question

I am just installing the current version of TWiki under WindowsNT.

When saving an edited text I receive an error:

Insecure directory in $ENV{PATH}while running with -T switch at ../lib/TWiki/Store.pm line 955.

As far as I can see, $tmp is untainted just a few lines before. Any hints or workarounds (except removing -T)?

• TWiki version: 20010901
• Web server: Apache
• Server OS: WindowsNT

-- TWikiGuest - 20 Sep 2001

I'm running into the same problem only at ../lib/TWiki/Search.pm line 266 I am running Apache2/Win2k so I did try the workaround below of removing Everyone from permissions in the cygwin and Twiki directories but it results in internal server errors trying to access the twiki afterwords.

-- TWikiGuest - 21 Nov 2002

Answer

.

I found a similar problem on a Windows 2000 installation running Apache2. I removed the Group "Everyone" from the Permissions on the Windows Folders for "twiki" and "cygwin" and it solved the problem.

-- TWikiGuest - 22 Nov 2002

Hi - thanks for the update. See WindowsInstallCookbook for another way to avoid this. This is due to TaintChecking in Perl - presumably you are using ActivePerl.

-- RichardDonkin - 22 Nov 2002

I had exactly the same problem on a Windows 2000 / Apache installation. The WindowsInstallCookbook instructions did not solve this, and removing the group "Everyone" also resulted in server errors, as mentioned above. However, re-adding the group "Everyone" to the permissions on Windows folder "cygwin/bin" and applying the following security permissions solved the issue:

Allow: [Read & Execute, List Folder Contents, Read] Deny: [Write]

Hope this can be of some help.

-- BirgirFinnsson - 26 Nov 2002

Denying write to Everyone will make twiki work, but you won't be able to upgrade cygwin anymore as deny always takes precedence over allow .

A more correct fix is to

1. bring up security properties on the top cygwin directory (c:\cygwin),
2. uncheck 'inherit permissions', slap the 'copy existing' button when prompted
3. for the 'Everyone' group, uncheck Write access and Full Control
4. Add the groups CREATOR OWNER, SYSTEM and give them Full Control
5. Add the users Administrator, Your_Name and give them Full Control

-- MattWilkie - 29 Jun 2003