File:  [MW Coherent from dump] / coherent / a / usr / man / COHERENT / permissions
Revision 1.1.1.1 (vendor branch): download - view: text, annotated - select for diffs
Wed May 29 04:56:34 2019 UTC (7 years ago) by root
Branches: MarkWilliams, MAIN
CVS tags: relic, HEAD
coherent



Permissions                File Format                Permissions




Format of UUCP permissions file

/uussrr/lliibb/uuuuccpp/PPeerrmmiissssiioonnss

The  file  PPeerrmmiissssiioonnss   describes  the  remote  sites  that  can
communicate  via UUCP  with your COHERENT  system, and  lists the
programs that  each site  can execute  on your system.   Before a
remote site can  communicate with your COHERENT system, that site
must have an entry in PPeerrmmiissssiioonnss.

When the command uuuucciiccoo attempts to execute a file transfer to or
from a remote  site, it checks to see that  there is an entry for
the  site in  PPeerrmmiissssiioonnss. If  your  PPeerrmmiissssiioonnss entries  are not
written correctly, you risk a breach of system security.

Each entry in PPeerrmmiissssiioonnss takes one of two forms:

-> LLOOGGNNAAMMEE   entries  detail  the   permissions  granted   to  an
   individual user when he calls your system from a remote site.

-> MMAACCHHIINNEE entries  detail the  permissions for the  remote sites
   that you call.

You can  combine the two types  of entries into one  entry if the
permissions are the same in both entries.

An entry in PPeerrmmiissssiioonnss consists  of pairs of entries of the form
_O_P_T_I_O_N=_v_a_l_u_e,   each  separated  by   one  or   more  white-space
characters.  The  _O_P_T_I_O_N side  must be in  upper-case characters,
and the _v_a_l_u_e side in  lower-case characters.  At the end of each
line (except  the last), you  must include a  backslash character
(`\')  to continue  the current  line onto  the next  one.  Blank
lines between entries are ignored.

For the RREEAADD, NNOORREEAADD, WWRRIITTEE, and NNOOWWRRIITTEE fields, described below,
the value  specified is a sequence of one  or more directories on
your  computer, separated  only by colons  (i.e., no  white space
allowed).

An entry in PPeerrmmiissssiioonnss can have up to ten fields:

1. MMAACCHHIINNEE
     This  field  names  the  remote  system  that  you  wish  to
     communicate  with.   It  is  limited  to  seven  characters.
     (Future releases of COHERENT will increase this limit.)

2. LLOOGGNNAAMMEE
     This field  specifies the login name  that the remote system
     will use when it calls your system.  Please note that if the
     remote site  attempts to log  into your system  with a login
     name other than the one specified by this field, uuuucciiccoo will
     terminate the  call for security  reasons.  There must  be a
     valid entry  in file /eettcc/ppaasssswwdd  for the name  specified in
     this field.


COHERENT Lexicon                                           Page 1




Permissions                File Format                Permissions




3. RREEAADD
     This  entry names  the directories on  your system  that the
     UUCP commands can access.   You must give the full path name
     of the directory.  The default is /uussrr/ssppooooll/uuuuccppppuubblliicc.

4. NNOORREEAADD
     When a  directory is entered  in the RREEAADD field,  all of its
     sub-directories become  available for reading.   If you wish
     to make any  of its sub-directories unreadable by the remote
     site, name it here.  You must give the full path name of the
     directory.  The default is NULL.

5. WWRRIITTEE
     Here,  name the  directories on your  system into  which the
     command uuuucciiccoo  can deposit files.   You must give  the full
     path    name   of   the    directory.    The    default   is
     /uussrr/ssppooooll/uuuuccppppuubblliicc.

6. NNOOWWRRIITTEE
     When a  directory is entered in the  WWRRIITTEE field, the remote
     system can  write into all  of its sub-directories.   If you
     wish to  make any of its  sub-directories unwriteable by the
     remote site,  enter it  here.  You  must give the  full path
     name of the directory.  The default is NULL.

7. CCOOMMMMAANNDDSS
     Here, name  the commands that the  remote system can execute
     on your  computer.  The  two most  basic commands to  put in
     this entry  are rrmmaaiill  and uuuuccpp.  This lets the  remote site
     send  electronic mail  to you  and to  use uucp  to transfer
     files.   You may  add other  commands,  but the  shorter the
     list,  the  greater  your  level  of system  security.   The
     default is rrmmaaiill.

8. RREEQQUUEESSTT
     This entry  asks if the remote site  can request to transfer
     files from  your system.  Respond yyeess if  security is not an
     issue.  If  the value  is nnoo,  only your system  can request
     that files be  transfered to the remote system.  The default
     is nnoo.

9. SSEENNDDFFIILLEESS
     This entry  asks if your system  can initiate file transfers
     to the remote site.  Your  response can be yyeess, nnoo, or ccaallll.
     The default is ccaallll, which allows files to be sent only when
     your system  calls the remote  site.  A value  of yyeess allows
     your  system   to  transfer  files  to   the  remote  system
     regardless of  which system originated  the conversation.  A
     value of nnoo prohibits any file transfers from your system to
     the remote system.

10. MMYYNNAAMMEE
     This  field  contains  the  site  name  that you  have  been
     assigned by the system administrator of the remote site.  It


COHERENT Lexicon                                           Page 2




Permissions                File Format                Permissions



     must contain  no more than  seven characters.  If  MMYYNNAAMMEE is
     defined, its value is used as your site name rather than the
     value in  /eettcc/uuuuccppnnaammee. This is useful  in situations where
     your site name is already used by an existing account on the
     remote site  you wish to call, or when  the remote site does
     not support ``anonymous'' UUCP access.

When writing your  Permissions file, keep these considerations in
mind:

-> White space is not allowed before or after the `=' sign.

-> Each line  corresponds to one  entry. You may  continue to the
   next line by ending the line with a backslash charcter (`\').

-> If a  field has more than  one value, use a  colon to separate
   them.

***** Example *****

The following  example gives an entry in PPeerrmmiissssiioonnss  to set up a
connection with the Mark Williams Company's UUCP BBS:


       MACHINE=mwcbbs MYNAME=bbsuser \
       REQUEST=yes SENDFILES=yes \
       COMMANDS=rmail:uucp \
       READ=/usr/spool/uucppublic:/tmp \
       WRITE=/usr/spool/uucppublic:/tmp


***** See Also *****

ffiillee ffoorrmmaattss, UUUUCCPP























COHERENT Lexicon                                           Page 3



unix.superglobalmegacorp.com

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.