This is Info file uucp.info, produced by Makeinfo-1.55 from the input file /usr/src/gnu/libexec/uucp/doc/uucp.texi. This file documents Taylor UUCP, version 1.05. Copyright (C) 1992, 1993, 1994 Ian Lance Taylor Permission is granted to make and distribute verbatim copies of this manual provided the copyright notice and this permission notice are preserved on all copies. Permission is granted to copy and distribute modified versions of this manual under the conditions for verbatim copying, provided also that the section entitled "Copying" are included exactly as in the original, and provided that the entire resulting derived work is distributed under the terms of a permission notice identical to this one. Permission is granted to copy and distribute translations of this manual into another language, under the above conditions for modified versions, except that the section entitled "Copying" may be included in a translation approved by the author instead of in the original English.  File: uucp.info, Node: Security, Prev: dial File, Up: Configuration Files Security ======== This discussion of UUCP security applies only to Unix. It is a bit cursory; suggestions for improvement are solicited. UUCP is traditionally not very secure. Taylor UUCP addresses some security issues, but is still far from being a secure system. If security is very important to you, then you should not permit any external access to your computer, including UUCP. Any opening to the outside world is a potential security risk. By default Taylor UUCP provides few mechanisms to secure local users of the system from each other. You can allow increased security by putting the owner of the UUCP programs (normally `uucp') into a separate group; the use of this is explained in the following paragraphs, which refer to this separate group as `uucp-group'. When the `uucp' program is invoked to copy a file to a remote system, it will by default copy the file into the UUCP spool directory. When the `uux' program is used, the `-C' switch must be used to copy the file into the UUCP spool directory. In any case, once the file has been copied into the spool directory, other local users will not be able to access it. When a file is requested from a remote system, UUCP will only permit it to be placed in a directory which is writable by the requesting user. The directory must also be writable by UUCP. A local user can create a directory with a group of `uucp-group' and set the mode to permit group write access. This will allow the file be requested without permitting it to be viewed by any other user. There is no provision for security for `uucp' requests (as opposed to `uux' requests) made by a user on a remote system. A file sent over by a remote request may only be placed in a directory which is world writable, and the file will be world readable and writable. This will permit any local user to destroy or replace the contents of the file. A file requested by a remote system must be world readable, and the directory it is in must be world readable. Any local user will be able to examine, although not necessarily modify, the file before it is sent. There are some security holes and race conditions that apply to the above discussion which I will not elaborate on. They are not hidden from anybody who reads the source code, but they are somewhat technical and difficult (though scarcely impossible) to exploit. Suffice it to say that even under the best of conditions UUCP is not completely secure. For many sites, security from remote sites is a more important consideration. Fortunately, Taylor UUCP does provide some support in this area. The greatest security is provided by always dialing out to the other site. This prevents anybody from pretending to be the other site. Of course, only one side of the connection can do this. If remote dialins must be permitted, then it is best if the dialin line is used only for UUCP. If this is the case, then you should create a call-in password file (*note Configuration File Names::.) and let `uucico' do its own login prompting. For example, to let remote sites log in on a port named `entry' in the port file (*note port File::.) you might invoke `uucico -p entry'. This would cause `uucico' to enter an endless loop of login prompts and daemon executions. The advantage of this approach is that even if remote users break into the system by guessing or learning the password, they will only be able to do whatever `uucico' permits them to do. They will not be able to start a shell on your system. If remote users can dial in and log on to your system, then you have a security hazard more serious than that posed by UUCP. But then, you probably knew that already. Once your system has connected with the remote UUCP, there is a fair amount of control you can exercise. You can use the `remote-send' and `remote-receive' commands to control the directories the remote UUCP can access. You can use the `request' command to prevent the remote UUCP from making any requests of your system at all; however, if you do this it will not even be able to send you mail or news. If you do permit remote requests, you should be careful to restrict what commands may be executed at the remote system's request. The default is `rmail' and `rnews', which will suffice for most systems. If different remote systems call in and they must be granted different privileges (perhaps some systems are within the same organization and some are not) then the `called-login' command should be used for each system to require that they different login names. Otherwise it would be simple for a remote system to use the `myname' command and pretend to be a different system. The `sequence' command can be used to detect when one system pretended to be another, but since the sequence numbers must be reset manually after a failed handshake this can sometimes be more trouble than it's worth.  File: uucp.info, Node: Protocols, Next: Hacking, Prev: Configuration Files, Up: Top UUCP protocol internals *********************** A detailed description of how the various UUCP protocols work is posted monthly to the newsgroups `comp.mail.uucp', `news.answers' and `comp.answers'. There is no need to read this information in order to use Taylor UUCP. It is intended for people who are interested in how the UUCP code works.  File: uucp.info, Node: Hacking, Next: Acknowledgements, Prev: Protocols, Up: Top Hacking Taylor UUCP ******************* This chapter provides the briefest of guides to the Taylor UUCP source code itself. * Menu: * System Dependence:: System Dependence * Naming Conventions:: Naming Conventions * Patches:: Patches  File: uucp.info, Node: System Dependence, Next: Naming Conventions, Prev: Hacking, Up: Hacking System Dependence ================= The code is carefully segregated into a system independent portion and a system dependent portion. The system dependent code is in the `unix' subdirectory, and also in the files `tcp.c', `tli.c' and `sysh.unx' (also known as `sysdep.h'). With the right configuration parameters, the system independent code calls only ANSI C functions. Some of the less common ANSI C functions are also provided in the `lib' directory. The replacement function `strtol' in `lib/strtol.c' assumes that the characters `A' to `F' and `a' to `f' appear in strictly sequential order. The function `igradecmp' in `uuconf/grdcmp.c' assumes that the upper and lower case letters appear in order. Both assumptions are true for ASCII and EBCDIC, but neither is guaranteed by ANSI C. Disregarding these caveats, I believe that the system independent portion of the code is strictly conforming. That's not too exciting, since all the work is done in the system dependent code. I think that this code can conform to POSIX 1003.1, given the right compilation parameters. I'm a bit less certain about this, though. The code is in use on a 16 bit segmented system with no function prototypes, so I'm certain that all casts to long and pointers are done when necessary.  File: uucp.info, Node: Naming Conventions, Next: Patches, Prev: System Dependence, Up: Hacking Naming Conventions ================== I use a modified Hungarian naming convention for my variables and functions. As with all naming conventions, the code is rather opaque if you are not familiar with it, but becomes clear and easy to use with time. The first character indicates the type of the variable (or function return value). Sometimes additional characters are used. I use the following type prefixes: `a' array; the next character is the type of an element `b' byte or character `c' count of something `e' stdio FILE * `f' boolean `i' generic integer `l' double `o' file descriptor (as returned by open, creat, etc.) `p' generic pointer `q' pointer to structure `s' structure `u' void (function return values only) `z' character string A generic pointer (`p') is sometimes a `void *', sometimes a function pointer in which case the prefix is pf, and sometimes a pointer to another type, in which case the next character is the type to which it points (pf is overloaded). An array of strings (`char *[]') would be named `az' (array of string). If this array were passed to a function, the function parameter would be named `paz' (pointer to array of string). Note that the variable name prefixes do not necessarily indicate the type of the variable. For example, a variable prefixed with i may be int, long or short. Similarly, a variable prefixed with b may be a char or an int; for example, the return value of getchar would be caught in an int variable prefixed with b. For a non-local variable (extern or file static), the first character after the type prefix is capitalized. Most static variables and functions use another letter after the type prefix to indicate which module they come from. This is to help distinguish different names in the debugger. For example, all static functions in `protg.c', the `g' protocol source code, use a module prefix of `g'. This isn't too useful, as a number of modules use a module prefix of `s'.  File: uucp.info, Node: Patches, Prev: Naming Conventions, Up: Hacking Patches ======= I am always grateful for any patches sent in. Much of the flexibility and portability of the code is due to other people. Please do not hesitate to send me any changes you have found necessary or useful. When sending a patch, please send the output of the Unix `diff' program invoked with the `-c' option (if you have the GNU version of `diff', use the `-p' option). Always invoke `diff' with the original file first and the modified file second. If your `diff' does not support `-c' (or you don't have `diff'), send a complete copy of the modified file (if you have just changed a single function, you can just send the new version of the function). In particular, please do not send `diff' output without the `-c' option, as it is useless. If you have made a number of changes, it is very convenient for me if you send each change as a separate mail message. Sometimes I will think that one change is useful but another one is not. If they are in different messages it is much easier for me to apply one but not the other. I rarely apply the patches directly. Instead I work my way through the hunks and apply each one separately. This ensures that the naming remains consistent, and that I understand all the code. If you can not follow all these rules, then don't. But if you do, it makes it more likely that I will incorporate your changes. I am not paid for my UUCP work, and my available time is unfortunately very restricted. The package is important to me, and I do what I can, but I can not do all that I would like, much less all that everybody else would like. Finally, please do not be offended if I do not reply to messages for some time, even a few weeks. I am often behind on my mail, and if I think your message deserves a considered reply I will often put it aside until I have time to deal with it.  File: uucp.info, Node: Acknowledgements, Next: Index (concepts), Prev: Hacking, Up: Top Acknowledgements **************** This is a list of people who gave help or suggestions while I was working on the Taylor UUCP project. Appearance on this list does not constitute endorsement of the program, particularly since some of the comments were criticisms. I've probably left some people off, and I apologize for any oversight; it does not mean your contribution was unappreciated. First of all, I would like to thank the people at Infinity Development Systems (formerly AIRS, which lives on in the domain name, at least for now) for permitting me to use their computers and `uunet' access. I would also like to thank Richard Stallman `' for founding the Free Software Foundation and John Gilmore `' for writing the initial version of gnuucp which was a direct inspiration for this somewhat larger project. Chip Salzenberg `' has contributed many patches. Franc,ois Pinard `' tirelessly tested the code and suggested many improvements. He also put together the initial version of this document. Doug Evans contributed the zmodem protocol. Marc Boucher `' contributed the code supporting the pipe port type. Finally, Verbus M. Counts `' and Centel Federal Systems, Inc. deserve special thanks, since they actually paid me money to port this code to System III. In alphabetical order: "Earle F. Ake - SAIC" `' `mra@searchtech.com' (Michael Almond) `cambler@zeus.calpoly.edu' (Christopher J. Ambler) Brian W. Antoine `' `jantypas@soft21.s21.com' (John Antypas) `james@bigtex.cactus.org' (James Van Artsdalen) `nba@sysware.DK' (Niels Baggesen) `uunet!hotmomma!sdb' (Scott Ballantyne) Zacharias Beckman `' `mike@mbsun.ann-arbor.mi.us' (Mike Bernson) `bob@usixth.sublink.org' (Roberto Biancardi) `statsci!scott@coco.ms.washington.edu' (Scott Blachowicz) `bag%wood2.cs.kiev.ua@relay.ussr.eu.net' (Andrey G Blochintsev) `spider@Orb.Nashua.NH.US' (Spider Boardman) Gregory Bond `' Marc Boucher `' `dean@coplex.com' (Dean Brooks) `jbrow@radical.com' (Jim Brownfield) `dave@dlb.com' (Dave Buck) `gordon@sneaky.lonestar.org' (Gordon Burditt) `dburr@sbphy.physics.ucsb.edu' (Donald Burr) `mib@gnu.ai.mit.edu' (Michael I Bushnell) Brian Campbell `' Andrew A. Chernov `' `mafc!frank@bach.helios.de' (Frank Conrad) Ed Carp `' `mpc@mbs.linet.org' (Mark Clements) `verbus@westmark.westmark.com' (Verbus M. Counts) `cbmvax!snark.thyrsus.com!cowan' (John Cowan) Bob Cunningham `' `kdburg@incoahe.hanse.de' (Klaus Dahlenburg) Damon `' `hubert@arakis.fdn.org' (Hubert Delahaye) `markd@bushwire.apana.org.au' (Mark Delany) Allen Delaney `' `denny@dakota.alisa.com' (Bob Denny) `ssd@nevets.oau.org' (Steven S. Dick) `gert@greenie.gold.sub.org' (Gert Doering) `gemini@geminix.in-berlin.de' (Uwe Doering) Hans-Dieter Doll `' Mark W. Eichin `' Andrew Evans `' `dje@cygnus.com' (Doug Evans) Marc Evans `' Dan Everhart `' `kksys!kegworks!lfahnoe@cs.umn.edu' (Larry Fahnoe) `fenner@jazz.psu.edu' (Bill Fenner) `jaf@inference.com' (Jose A. Fernandez) "David J. Fiander" `' Thomas Fischer `' `louis@marco.de' (Ju"rgen Fluk) `erik@eab.retix.com' (Erik Forsberg) `andy@scp.caltech.edu' (Andy Fyfe) Lele Gaifax `' `Peter.Galbavy@micromuse.co.uk' `hunter@phoenix.pub.uu.oz.au' (James Gardiner [hunter]) Terry Gardner `' `ol@infopro.spb.su' (Oleg Girko) `jimmy@tokyo07.info.com' (Jim Gottlieb) Benoit Grange `' `elg@elgamy.jpunix.com' (Eric Lee Green) `ryan@cs.umb.edu' (Daniel R. Guilderson) `greg@gagme.chi.il.us' (Gregory Gulik) Richard H. Gumpertz `' Michael Haberler `' Daniel Hagerty `' `jh@moon.nbn.com' (John Harkin) `guy@auspex.auspex.com' (Guy Harris) Petri Helenius `' `gabe@edi.com' (B. Gabriel Helou) Bob Hemedinger `' Andrew Herbert `' Peter Honeyman `' `jhood@smoke.marlboro.vt.us' (John Hood) Bill Irwin `' `pmcgw!personal-media.co.jp!ishikawa' (Chiaki Ishikawa) `bei@dogface.austin.tx.us' (Bob Izenberg) `djamiga!djjames@fsd.com' (D.J.James) Rob Janssen `' `harvee!esj' (Eric S Johansson) Kevin Johnson `' Alan Judge `' `chris@cj_net.in-berlin.de' (Christof Junge) `tron@Veritas.COM' (Ronald S. Karr) Brendan Kehoe `' `warlock@csuchico.edu' (John Kennedy) `kersing@nlmug.nl.mugnet.org' (Jac Kersing) Gabor Kiss `' `gero@gkminix.han.de' (Gero Kuhlmann) `rob@pact.nl' (Rob Kurver) `kent@sparky.IMD.Sterling.COM' (Kent Landfield) `lebaron@inrs-telecom.uquebec.ca' (Gregory LeBaron) `karl@sugar.NeoSoft.Com' (Karl Lehenbauer) `alex@hal.rhein-main.de' (Alexander Lehmann) `merlyn@digibd.com' (Merlyn LeRoy) `clewis@ferret.ocunix.on.ca' (Chris Lewis) `gdonl@ssi1.com' (Don Lewis) `libove@libove.det.dec.com' (Jay Vassos-Libove) `bruce%blilly@Broadcast.Sony.COM' (Bruce Lilly) Ted Lindgreen `' `andrew@cubetech.com' (Andrew Loewenstern) "Arne Ludwig" `' Matthew Lyle `' `djm@eng.umd.edu' (David J. MacKenzie) John R MacMillan `' Giles D Malet `' `mem@mv.MV.COM' (Mark E. Mallett) `pepe@dit.upm.es' (Jose A. Manas) `peter@xpoint.ruessel.sub.org' (Peter Mandrella) `martelli@cadlab.sublink.org' (Alex Martelli) W Christopher Martin `' Yanek Martinson `' `jm@aristote.univ-paris8.fr' (Jean Mehat) `me@halfab.freiburg.sub.org' (Udo Meyer) `les@chinet.chi.il.us' (Leslie Mikesell) `mmitchel@digi.lonestar.org' (Mitch Mitchell) Emmanuel Mogenet `' `rmohr@infoac.rmi.de' (Rupert Mohr) Jason Molenda `' `ianm@icsbelf.co.uk' (Ian Moran) `brian@ilinx.wimsey.bc.ca' (Brian J. Murrell) `service@infohh.rmi.de' (Dirk Musstopf) `lyndon@cs.athabascau.ca' (Lyndon Nerenberg) `rolf@saans.north.de' (Rolf Nerstheimer) `tom@smart.bo.open.de' (Thomas Neumann) `mnichols@pacesetter.com' Richard E. Nickle `' `stephan@sunlab.ka.sub.org' (Stephan Niemz) `nolan@helios.unl.edu' (Michael Nolan) david nugent `' Jim O'Connor `' Petri Ojala `' `oneill@cs.ulowell.edu' (Brian 'Doc' O'Neill) `abekas!dragoman!mikep@decwrl.dec.com' (Mike Park) Tim Peiffer `peiffer@cs.umn.edu' `don@blkhole.resun.com' (Don Phillips) "Mark Pizzolato 415-369-9366" `' John Plate `' `dplatt@ntg.com' (Dave Platt) `eldorado@tharr.UUCP' (Mark Powell) Mark Powell `' `pozar@kumr.lns.com' (Tim Pozar) `putsch@uicc.com' (Jeff Putsch) `ar@nvmr.robin.de' (Andreas Raab) Jarmo Raiha `' Scott Reynolds `' `mcr@Sandelman.OCUnix.On.Ca' (Michael Richardson) Kenji Rikitake `' `arnold@cc.gatech.edu' (Arnold Robbins) `steve@Nyongwa.cam.org' (Steve M. Robbins) Serge Robyns `' Lawrence E. Rosenman `' Jeff Ross `' Aleksey P. Rudnev `' "Heiko W.Rupp" `' `wolfgang@wsrcc.com' (Wolfgang S. Rupprecht) `tbr@tfic.bc.ca' (Tom Rushworth) `jsacco@ssl.com' (Joseph E. Sacco) `rsalz@bbn.com' (Rich Salz) `sojurn!mike@hobbes.cert.sei.cmu.edu' (Mike Sangrey) Nickolay Saukh `' `heiko@lotte.sax.de' (Heiko Schlittermann) Eric Schnoebelen `' `russell@alpha3.ersys.edmonton.ab.ca' (Russell Schulz) `scott@geom.umn.edu' Igor V. Semenyuk `' Christopher Sawtell `' `schuler@bds.sub.org' (Bernd Schuler) `uunet!gold.sub.org!root' (Christian Seyb) `s4mjs!mjs@nirvo.nirvonics.com' (M. J. Shannon Jr.) `peter@ficc.ferranti.com' (Peter da Silva) `vince@victrola.sea.wa.us' (Vince Skahan) `frumious!pat' (Patrick Smith) `roscom!monty@bu.edu' (Monty Solomon) `sommerfeld@orchard.medford.ma.us' (Bill Sommerfeld) Julian Stacey `' Harlan Stenn `' Ralf Stephan `' `johannes@titan.westfalen.de' (Johannes Stille) `chs@antic.apu.fi' (Hannu Strang) `ralf@reswi.ruhr.de' (Ralf E. Stranzenbach) `sullivan@Mathcom.com' (S. Sullivan) Shigeya Suzuki `' `swiers@plains.NoDak.edu' Oleg Tabarovsky `' John Theus `' `rd@aii.com' (Bob Thrush) ppKarsten Thygesen `' Graham Toal `' `rmtodd@servalan.servalan.com' (Richard Todd) Martin Tomes `' Len Tower `' Mark Towfiq `' `mju@mudos.ann-arbor.mi.us' (Marc Unangst) Tomi Vainio `' Andrew Vignaux `' `vogel@omega.ssw.de' (Andreas Vogel) `jos@bull.nl' (Jos Vos) `jv@nl.net' (Johan Vromans) David Vrona `' `Marcel.Waldvogel@nice.usergroup.ethz.ch' (Marcel Waldvogel) `steve@nshore.org' (Stephen J. Walick) `syd@dsinc.dsi.com' (Syd Weinstein) `gerben@rna.indiv.nluug.nl' (Gerben Wierda) `jbw@cs.bu.edu' (Joe Wells) `frnkmth!twwells.com!bill' (T. William Wells) Peter Wemm `' `mauxci!eci386!woods@apple.com' (Greg A. Woods) Michael Yu.Yaroslavtsev `' Alexei K. Yushin `' `jon@console.ais.org' (Jon Zeeff) Matthias Zepf `' Eric Ziegast `'  File: uucp.info, Node: Index (concepts), Next: Index (configuration file), Prev: Acknowledgements, Up: Top Concept Index ************* * Menu: * /usr/spool/uucp: Miscellaneous (config). * /usr/spool/uucppublic: Miscellaneous (config). * anonymous UUCP: config File Examples. * call configuration file: Configuration File Names. * call in login name: Configuration File Names. * call in password: Configuration File Names. * call out file: Configuration File Names. * call out login name: Configuration File Names. * call out password: Configuration File Names. * changing spool directory: config File Examples. * chat scripts: Chat Scripts. * config file: config File. * config file examples: config File Examples. * configuration file (call): Configuration File Names. * configuration file (config): config File. * configuration file (dial): dial File. * configuration file (dialcode): Configuration File Names. * configuration file (passwd): Configuration File Names. * configuration file (port): port File. * configuration file (sys): sys File. * debugging file: Log File Names. * dial file: dial File. * dialcode configuration file: Configuration File Names. * dialcode file: Configuration File Names. * dialer configuration file: dial File. * gateway: Gateway Example. * leaf site: Leaf Example. * lock directory: Miscellaneous (config). * log file: Log File Names. * main configuration file: config File. * passwd configuration file: Configuration File Names. * passwd file: Configuration File Names. * port configuration file: port File. * port file: port File. * public directory: Miscellaneous (config). * spool directory: Miscellaneous (config). * spool directory (changing): config File Examples. * statistics file: Log File Names. * sys file: sys File. * sys file example (gateway): Gateway Example. * sys file example (leaf): Leaf Example. * system configuration file: sys File. * system name: Miscellaneous (config). * time strings: Time Strings. * unknown systems: Miscellaneous (config). * UUCP system name: Miscellaneous (config). * uucppublic: Miscellaneous (config).  File: uucp.info, Node: Index (configuration file), Prev: Index (concepts), Up: Top Configuration File Index ************************ * Menu: * abort: dial File. * abort-chat: dial File. * abort-chat-fail: dial File. * abort-chat-program: dial File. * abort-chat-seven-bit: dial File. * abort-chat-timeout: dial File. * address: Placing the Call. * alias: Naming the System. * alternate: Naming the System. * baud in port file: port File. * baud in sys file: Placing the Call. * baud-range: port File. * call-local-size: File Transfer Control. * call-login: Logging In. * call-password: Logging In. * call-remote-size: File Transfer Control. * call-timegrade: When to Call. * call-transfer: File Transfer Control. * callback: Accepting a Call. * called-chat: Accepting a Call. * called-chat-fail: Accepting a Call. * called-chat-program: Accepting a Call. * called-chat-seven-bit: Accepting a Call. * called-chat-timeout: Accepting a Call. * called-local-size: File Transfer Control. * called-login: Accepting a Call. * called-remote-size: File Transfer Control. * called-transfer: File Transfer Control. * callfile: Configuration File Names. * carrier in dial file: dial File. * carrier in port file: port File. * carrier-wait: dial File. * chat: Chat Scripts. * chat in dial file: dial File. * chat in sys file: Logging In. * chat-fail: Chat Scripts. * chat-fail in dial file: dial File. * chat-fail in sys file: Logging In. * chat-program: Chat Scripts. * chat-program in dial file: dial File. * chat-program in sys file: Logging In. * chat-seven-bit: Chat Scripts. * chat-seven-bit in dial file: dial File. * chat-seven-bit in sys file: Logging In. * chat-timeout: Chat Scripts. * chat-timeout in dial file: dial File. * chat-timeout in sys file: Logging In. * command: port File. * command-path: Miscellaneous (sys). * commands: Miscellaneous (sys). * complete: dial File. * complete-chat: dial File. * complete-chat-fail: dial File. * complete-chat-program: dial File. * complete-chat-seven-bit: dial File. * complete-chat-timeout: dial File. * debug in config file: Debugging Levels. * debug in sys file: Miscellaneous (sys). * debugfile: Log File Names. * default-alternates: Naming the System. * device: port File. * dial-device: port File. * dialcodefile: Configuration File Names. * dialer in dial file: dial File. * dialer in port file: port File. * dialer-sequence: port File. * dialfile: Configuration File Names. * dialtone: dial File. * dtr-toggle: dial File. * forward: File Transfer Control. * forward-from: File Transfer Control. * forward-to: File Transfer Control. * free-space: Miscellaneous (sys). * half-duplex in dial file: dial File. * half-duplex in port file: port File. * hardflow: port File. * hdb-files: Miscellaneous (config). * hostname: Miscellaneous (config). * local-receive: File Transfer Control. * local-send: File Transfer Control. * lockdir: Miscellaneous (config). * lockname: port File. * logfile: Log File Names. * max-remote-debug: Miscellaneous (sys). * max-retries: When to Call. * max-uuxqts: Miscellaneous (config). * myname: Naming the System. * nodename: Miscellaneous (config). * passwdfile: Configuration File Names. * pause: dial File. * phone: Placing the Call. * port in port file: port File. * port in sys file: Placing the Call. * portfile: Configuration File Names. * protocol in port file: port File. * protocol in sys file: Protocol Selection. * protocol-parameter in dial file: dial File. * protocol-parameter in port file: port File. * protocol-parameter in sys file: Protocol Selection. * pubdir in config file: Miscellaneous (config). * pubdir in sys file: Miscellaneous (sys). * push: port File. * receive-request: File Transfer Control. * reliable in dial file: dial File. * reliable in port file: port File. * remote-receive: File Transfer Control. * remote-send: File Transfer Control. * request: File Transfer Control. * run-uuxqt: Miscellaneous (config). * send-request: File Transfer Control. * sequence: Miscellaneous (sys). * server-address: port File. * service: port File. * seven-bit in dial file: dial File. * seven-bit in port file: port File. * speed in port file: port File. * speed in sys file: Placing the Call. * speed-range: port File. * spool: Miscellaneous (config). * statfile: Log File Names. * stream: port File. * sysfile: Configuration File Names. * system: Naming the System. * time: When to Call. * timegrade: When to Call. * timetable: Miscellaneous (config). * transfer: File Transfer Control. * type: port File. * unknown: Miscellaneous (config). * uuname: Miscellaneous (config). * v2-files: Miscellaneous (config).