1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
|
<TITLE>CGIWrap - Installation Instructions</TITLE>
<CENTER><H2>CGIWrap - Installation Instructions</H2></CENTER>
<HR><P>
<H3>Basic Installation</H3>
<DL>
<P><DT>Look at the <A HREF="notes.html">notes</A> to see if
there are any hints for your platform.
<P><DT>Type "./Configure" and answer the questions.
<P><DT>Type "make"
<P><DT>Copy cgiwrap executable to your servers cgi-bin directory
<P><DT>Make cgiwrap owned by root, executable by all, and setuid.
(<B>Note:</B> This step must be performed while logged in as "<TT>root</TT>"</B>)
<P>
<DD>chown root cgiwrap
<DD>chmod 4755 cgiwrap
<P><DT>Hardlink or symlink nph-cgiwrap, nph-cgiwrapd, cgiwrapd to
cgiwrap in the cgi-bin directory.
<P>
<DD>ln [-s] cgiwrap cgiwrapd
<DD>ln [-s] cgiwrap nph-cgiwrap
<DD>ln [-s] cgiwrap nph-cgiwrapd
<P><DT>You can, if you wish, install it with less permissive permissions. (Eg.
4750) But if you do this, make sure that the group of cgiwrap is the same
as the group that the server runs as.
</DL>
<P><HR>
<H3>Password Protected Installation</H3>
<P>
The following are pecial additional instructions for installing a copy of
cgiwrap that allows users to create access controlled scripts. For this to
work, you will need to have a single common password file that will be
used by all authenticated scripts.
<DL>
<P><DT>Re run configure, specify "public_html/auth-cgi-bin" instead of
"public_html/cgi-bin" for the cgi directory.
<P><DT>Type make.
<P><DT>Create a new server cgi-bin directory called "auth-cgi-bin", and
install this new copy of cgiwrap into that directory the same way you installed
it into the cgi-bin directory. (4 copies, and set permissions). You will
now be able to use the url: http://server/auth-cgi-bin/cgiwrap...
<P><DT>To enable access control, place a .htaccess or equivalent file in
the auth-cgi-bin directory where cgiwrap is located, that requires
authentication to get at any file in that directory, but will allow any
valid user to get through.
<P><DT>Now, your users can simply check: 1. That their script was
executed by them (eg. check the real uid of the script to make sure someone else
wasn't running it by hand) 2. That the REMOTE_USER environment variable
contains a user name that they want to allow to access the script.
</DL>
<P><HR>
<H3>Supplementary Configuration</H3>
<P>
If you enabled the access file checking, you need to make sure and create
the necessary files.
<P>
If you enabled the user directory rewriting feature, you need to create
the configuration file that you specified in the Configure run.
|
