You can have ftam skip the password
request and automatically set up a connection to a remote host.
To automate your ftam connections, you create an FTAM "startup"
file (called .ftamrc ) in your home directory.
This file contains login information for specific remote hosts.
Once login information is available in .ftamrc, ftam does
not prompt you for passwords during connection establishment. This
feature can be useful if you routinely use ftam with particular
remote hosts, or use programs that need to perform ftam operations
unattended.
The following example illustrates using automatic remote login.
Note that an entry in .ftamrc has this basic form:
machine host_name login user_name [password user_pass] [account
account_name] |
A startup file can contain multiple entries like this.
Each one identifies a remote host, and a valid user name on that
host. A startup file provides FTAM with customized default information
for your convenience.
When you start an ftam session, it scans the startup file
looking for the host name you specified. The information in the
first entry that matches becomes the default information for the
login sequence.
You can accept the default by pressing [Enter]; ftam then
uses the password from that entry to log in to the remote. Also,
you can specify a different user name at the Username prompt. If
the startup file has an entry for that user on the specified host,
ftam uses the password from that entry to access the remote.
 |
| |
|
 | CAUTION: A startup file that contains password information
is a potential security hazard
. This may be an unacceptable risk in some situations. In such cases,
startup files should not contain password information. |
|
| |
|
Example |
|
Sue has the following entries in her .ftamrc file:
machine denver login don password shadowy
machine denver login sue password mystery
machine atlanta login kelly |
In this example, Sue connects to each host with ftam to show
the effect of these entries.
$ ftam
ftam> open denver
Username (denver:don): [Return]
Connected to denver as user don
ftam> close
Released connection to denver
ftam> open denver
Username (denver:don): sue
Connected to denver as user sue
ftam> close
Released connection to denver
ftam> open atlanta
Username (atlanta:kelly): [Return]
Password (atlanta:kelly):
Connected to atlanta as user kelly.
ftam> |
Sue had two entries in her .ftamrc file, listing different
login names and passwords for denver. The first (for don) is the
default whenever Sue connects to denver. Because both entries for
the host denver contain passwords, she is never prompted for a password
when she connects as either sue or don. However, when she connects
to atlanta, the startup file entry for kelly does not contain a
password. Therefore, if the user kelly has a password, Sue must
provide that password at the prompt.
Printable version
