![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to permissions CVS log ![[TXT]](/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/cvsweb/icons/dir.gif){kind=icon}
Up to [MW Coherent from dump] / coherent / a / usr / man / COHERENT|
Return to permissions CVS log | Up to [MW Coherent from dump] / coherent / a / usr / man / COHERENT |
1.1 root 1:
2:
3: Permissions File Format Permissions
4:
5:
6:
7:
8: Format of UUCP permissions file
9:
10: /uussrr/lliibb/uuuuccpp/PPeerrmmiissssiioonnss
11:
12: The file PPeerrmmiissssiioonnss describes the remote sites that can
13: communicate via UUCP with your COHERENT system, and lists the
14: programs that each site can execute on your system. Before a
15: remote site can communicate with your COHERENT system, that site
16: must have an entry in PPeerrmmiissssiioonnss.
17:
18: When the command uuuucciiccoo attempts to execute a file transfer to or
19: from a remote site, it checks to see that there is an entry for
20: the site in PPeerrmmiissssiioonnss. If your PPeerrmmiissssiioonnss entries are not
21: written correctly, you risk a breach of system security.
22:
23: Each entry in PPeerrmmiissssiioonnss takes one of two forms:
24:
25: -> LLOOGGNNAAMMEE entries detail the permissions granted to an
26: individual user when he calls your system from a remote site.
27:
28: -> MMAACCHHIINNEE entries detail the permissions for the remote sites
29: that you call.
30:
31: You can combine the two types of entries into one entry if the
32: permissions are the same in both entries.
33:
34: An entry in PPeerrmmiissssiioonnss consists of pairs of entries of the form
35: _O_P_T_I_O_N=_v_a_l_u_e, each separated by one or more white-space
36: characters. The _O_P_T_I_O_N side must be in upper-case characters,
37: and the _v_a_l_u_e side in lower-case characters. At the end of each
38: line (except the last), you must include a backslash character
39: (`\') to continue the current line onto the next one. Blank
40: lines between entries are ignored.
41:
42: For the RREEAADD, NNOORREEAADD, WWRRIITTEE, and NNOOWWRRIITTEE fields, described below,
43: the value specified is a sequence of one or more directories on
44: your computer, separated only by colons (i.e., no white space
45: allowed).
46:
47: An entry in PPeerrmmiissssiioonnss can have up to ten fields:
48:
49: 1. MMAACCHHIINNEE
50: This field names the remote system that you wish to
51: communicate with. It is limited to seven characters.
52: (Future releases of COHERENT will increase this limit.)
53:
54: 2. LLOOGGNNAAMMEE
55: This field specifies the login name that the remote system
56: will use when it calls your system. Please note that if the
57: remote site attempts to log into your system with a login
58: name other than the one specified by this field, uuuucciiccoo will
59: terminate the call for security reasons. There must be a
60: valid entry in file /eettcc/ppaasssswwdd for the name specified in
61: this field.
62:
63:
64: COHERENT Lexicon Page 1
65:
66:
67:
68:
69: Permissions File Format Permissions
70:
71:
72:
73:
74: 3. RREEAADD
75: This entry names the directories on your system that the
76: UUCP commands can access. You must give the full path name
77: of the directory. The default is /uussrr/ssppooooll/uuuuccppppuubblliicc.
78:
79: 4. NNOORREEAADD
80: When a directory is entered in the RREEAADD field, all of its
81: sub-directories become available for reading. If you wish
82: to make any of its sub-directories unreadable by the remote
83: site, name it here. You must give the full path name of the
84: directory. The default is NULL.
85:
86: 5. WWRRIITTEE
87: Here, name the directories on your system into which the
88: command uuuucciiccoo can deposit files. You must give the full
89: path name of the directory. The default is
90: /uussrr/ssppooooll/uuuuccppppuubblliicc.
91:
92: 6. NNOOWWRRIITTEE
93: When a directory is entered in the WWRRIITTEE field, the remote
94: system can write into all of its sub-directories. If you
95: wish to make any of its sub-directories unwriteable by the
96: remote site, enter it here. You must give the full path
97: name of the directory. The default is NULL.
98:
99: 7. CCOOMMMMAANNDDSS
100: Here, name the commands that the remote system can execute
101: on your computer. The two most basic commands to put in
102: this entry are rrmmaaiill and uuuuccpp. This lets the remote site
103: send electronic mail to you and to use uucp to transfer
104: files. You may add other commands, but the shorter the
105: list, the greater your level of system security. The
106: default is rrmmaaiill.
107:
108: 8. RREEQQUUEESSTT
109: This entry asks if the remote site can request to transfer
110: files from your system. Respond yyeess if security is not an
111: issue. If the value is nnoo, only your system can request
112: that files be transfered to the remote system. The default
113: is nnoo.
114:
115: 9. SSEENNDDFFIILLEESS
116: This entry asks if your system can initiate file transfers
117: to the remote site. Your response can be yyeess, nnoo, or ccaallll.
118: The default is ccaallll, which allows files to be sent only when
119: your system calls the remote site. A value of yyeess allows
120: your system to transfer files to the remote system
121: regardless of which system originated the conversation. A
122: value of nnoo prohibits any file transfers from your system to
123: the remote system.
124:
125: 10. MMYYNNAAMMEE
126: This field contains the site name that you have been
127: assigned by the system administrator of the remote site. It
128:
129:
130: COHERENT Lexicon Page 2
131:
132:
133:
134:
135: Permissions File Format Permissions
136:
137:
138:
139: must contain no more than seven characters. If MMYYNNAAMMEE is
140: defined, its value is used as your site name rather than the
141: value in /eettcc/uuuuccppnnaammee. This is useful in situations where
142: your site name is already used by an existing account on the
143: remote site you wish to call, or when the remote site does
144: not support ``anonymous'' UUCP access.
145:
146: When writing your Permissions file, keep these considerations in
147: mind:
148:
149: -> White space is not allowed before or after the `=' sign.
150:
151: -> Each line corresponds to one entry. You may continue to the
152: next line by ending the line with a backslash charcter (`\').
153:
154: -> If a field has more than one value, use a colon to separate
155: them.
156:
157: ***** Example *****
158:
159: The following example gives an entry in PPeerrmmiissssiioonnss to set up a
160: connection with the Mark Williams Company's UUCP BBS:
161:
162:
163: MACHINE=mwcbbs MYNAME=bbsuser \
164: REQUEST=yes SENDFILES=yes \
165: COMMANDS=rmail:uucp \
166: READ=/usr/spool/uucppublic:/tmp \
167: WRITE=/usr/spool/uucppublic:/tmp
168:
169:
170: ***** See Also *****
171:
172: ffiillee ffoorrmmaattss, UUUUCCPP
173:
174:
175:
176:
177:
178:
179:
180:
181:
182:
183:
184:
185:
186:
187:
188:
189:
190:
191:
192:
193:
194:
195:
196: COHERENT Lexicon Page 3
197:
198:
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.