Tags:
bugs1Add my vote for this tag extract_idea1Add my vote for this tag create new tag
, view all tags
I could not get Twiki to run and got
"error 500: Internal Server Error: 
The server encountered an unexpected condition 
which prevented it from fulfilling the request."

1and1.com support pointed out that

#!/usr/bin/perl -wT 
need to be replaced by
#!/usr/bin/perl

in all Perl modules in /twiki/bin, each time on the first line.

Making this change allows Twiki to run on this hoster, maybe the same problem exists on other hosters.

If this change would work for all hosters, then mayby this change can be added to the main product. Otherwise we will need to document this carefully as part of the installation notes.

-- BartLouwagie - 18 Nov 2004

Bart, did 1and1.com support say why taint checking (the T part of -wT) should be disabled? You really should have taint checking enabled in Apache server scripts, and it surprises me to hear of a hosting company recommending that you switch these checks off. The -w is just enabling warnings, which slows TWiki down a little but otherwise has no effect you would notice.

-- CrawfordCurrie - 18 Nov 2004

Sent this e-mail to 1and1.com support:

There is a concern that -T, Taint checking should be on in Perl scripts, see their comment on http://twiki.org/cgi-bin/view/Codev/AllPerlmodules where they ask: (copied the above feedback)

I looked it up on this perldoc.com page:

  • Perl automatically enables a set of special security checks, called taint mode, when it detects its program running with differing real and effective user or group IDs. The setuid bit in Unix permissions is mode 04000, the setgid bit mode 02000; either or both may be set. You can also enable taint mode explicitly by using the -T command line flag. This flag is strongly suggested for server programs and any program run on behalf of someone else, such as a CGI script. Once taint mode is on, it's on for the remainder of your script.
  • "-T forces 'taint' checks to be turned on so you can test them. Ordinarily these checks are done only when running setuid or setgid. It's a good idea to turn them on explicitly for programs that run on behalf of someone else whom you might not necessarily trust, such as CGI programs or any internet servers you might write in Perl. See http://www.perldoc.com/perl5.8.0/pod/perlsec.html for details. For security reasons, this option must be seen by Perl quite early; usually this means it must appear early on the command line or in the #! line for systems which support that construct."

I will keep you posted on their reply.

-- BartLouwagie - 18 Nov 2004

also, what are the permissions for the bin/ directory and the bin files?

-- WillNorris - 18 Nov 2004

As in installation with other hosters, I put the bin/ folder and files at 755 permission. I believe that is the recommended setting?

-- BartLouwagie - 20 Nov 2004

BasicForm
TopicClassification TWikiDeployment
TopicSummary #!/usr/bin/perl -wT in perl modules prevents installation at hoster
InterestedParties

RelatedTopics

Edit | Attach | Watch | Print version | History: r5 < r4 < r3 < r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r5 - 2004-11-20 - BartLouwagie
 
  • Learn about TWiki  
  • Download TWiki
This site is powered by the TWiki collaboration platform Powered by Perl Hosted by OICcam.com Ideas, requests, problems regarding TWiki? Send feedback. Ask community in the support forum.
Copyright © 1999-2017 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.