39a938f7 |
1 | \define{versionidplink} \versionid $Id$ |
bace5431 |
2 | |
e5b0d077 |
3 | \C{plink} Using the command-line connection tool Plink |
4 | |
717c214c |
5 | \i{Plink} (PuTTY Link) is a command-line connection tool similar to |
2f8d6d43 |
6 | UNIX \c{ssh}. It is mostly used for automated operations, such as |
7 | making CVS access a repository on a remote server. |
8 | |
9 | Plink is probably not what you want if you want to run an |
10 | interactive session in a console window. |
bace5431 |
11 | |
12 | \H{plink-starting} Starting Plink |
13 | |
2f8d6d43 |
14 | Plink is a command line application. This means that you cannot just |
15 | double-click on its icon to run it and instead you have to bring up |
16 | a \i{console window}. In Windows 95, 98, and ME, this is called an |
17 | \q{MS-DOS Prompt}, and in Windows NT and 2000 it is called a |
18 | \q{Command Prompt}. It should be available from the Programs section |
bace5431 |
19 | of your Start Menu. |
20 | |
2f8d6d43 |
21 | In order to use Plink, the file \c{plink.exe} will need either to be |
22 | on your \i{\c{PATH}} or in your current directory. To add the |
23 | directory containing Plink to your \c{PATH} environment variable, |
24 | type into the console window: |
bace5431 |
25 | |
8452efbc |
26 | \c set PATH=C:\path\to\putty\directory;%PATH% |
bace5431 |
27 | |
28 | This will only work for the lifetime of that particular console |
2f8d6d43 |
29 | window. To set your \c{PATH} more permanently on Windows NT, use the |
bace5431 |
30 | Environment tab of the System Control Panel. On Windows 95, 98, and |
31 | ME, you will need to edit your \c{AUTOEXEC.BAT} to include a \c{set} |
32 | command like the one above. |
33 | |
2f8d6d43 |
34 | \H{plink-usage} Using Plink |
35 | |
36 | This section describes the basics of how to use Plink for |
37 | interactive logins and for automated processes. |
bace5431 |
38 | |
39 | Once you've got a console window to type into, you can just type |
40 | \c{plink} on its own to bring up a usage message. This tells you the |
41 | version of Plink you're using, and gives you a brief summary of how to |
42 | use Plink: |
43 | |
44 | \c Z:\sysosd>plink |
45 | \c PuTTY Link: command-line connection utility |
c9a13be6 |
46 | \c Release 0.XX |
bace5431 |
47 | \c Usage: plink [options] [user@]host [command] |
e2a197cf |
48 | \c ("host" can also be a PuTTY saved session name) |
bace5431 |
49 | \c Options: |
2285d016 |
50 | \c -V print version information and exit |
51 | \c -pgpfp print PGP key fingerprints and exit |
bace5431 |
52 | \c -v show verbose messages |
e2a197cf |
53 | \c -load sessname Load settings from saved session |
54 | \c -ssh -telnet -rlogin -raw |
afd4d0d2 |
55 | \c force use of a particular protocol |
bace5431 |
56 | \c -P port connect to specified port |
e2a197cf |
57 | \c -l user connect with specified username |
e2a197cf |
58 | \c -batch disable all interactive prompts |
59 | \c The following options only apply to SSH connections: |
bace5431 |
60 | \c -pw passw login with specified password |
dbe6c525 |
61 | \c -D [listen-IP:]listen-port |
62 | \c Dynamic SOCKS-based port forwarding |
63 | \c -L [listen-IP:]listen-port:host:port |
64 | \c Forward local port to remote address |
65 | \c -R [listen-IP:]listen-port:host:port |
66 | \c Forward remote port to local address |
e2a197cf |
67 | \c -X -x enable / disable X11 forwarding |
68 | \c -A -a enable / disable agent forwarding |
69 | \c -t -T enable / disable pty allocation |
70 | \c -1 -2 force use of particular protocol version |
05581745 |
71 | \c -4 -6 force use of IPv4 or IPv6 |
e2a197cf |
72 | \c -C enable compression |
73 | \c -i key private key file for authentication |
54018d95 |
74 | \c -m file read remote command(s) from file |
4d1cdf5d |
75 | \c -s remote command is an SSH subsystem (SSH-2 only) |
b72c366d |
76 | \c -N don't start a shell/command (SSH-2 only) |
bace5431 |
77 | |
2f8d6d43 |
78 | Once this works, you are ready to use Plink. |
79 | |
80 | \S{plink-usage-interactive} Using Plink for interactive logins |
81 | |
82 | To make a simple interactive connection to a remote server, just |
83 | type \c{plink} and then the host name: |
84 | |
85 | \c Z:\sysosd>plink login.example.com |
86 | \c |
87 | \c Debian GNU/Linux 2.2 flunky.example.com |
88 | \c flunky login: |
89 | |
90 | You should then be able to log in as normal and run a session. The |
91 | output sent by the server will be written straight to your command |
92 | prompt window, which will most likely not interpret terminal control |
93 | codes in the way the server expects it to. So if you run any |
94 | full-screen applications, for example, you can expect to see strange |
95 | characters appearing in your window. Interactive connections like |
96 | this are not the main point of Plink. |
97 | |
98 | In order to connect with a different protocol, you can give the |
99 | command line options \c{-ssh}, \c{-telnet}, \c{-rlogin} or \c{-raw}. |
100 | To make an SSH connection, for example: |
101 | |
102 | \c Z:\sysosd>plink -ssh login.example.com |
103 | \c login as: |
104 | |
105 | If you have already set up a PuTTY saved session, then instead of |
106 | supplying a host name, you can give the saved session name. This |
107 | allows you to use public-key authentication, specify a user name, |
108 | and use most of the other features of PuTTY: |
109 | |
110 | \c Z:\sysosd>plink my-ssh-session |
111 | \c Sent username "fred" |
112 | \c Authenticating with public key "fred@winbox" |
113 | \c Last login: Thu Dec 6 19:25:33 2001 from :0.0 |
114 | \c fred@flunky:~$ |
115 | |
116 | \S{plink-usage-batch} Using Plink for automated connections |
117 | |
118 | More typically Plink is used with the SSH protocol, to enable you to |
119 | talk directly to a program running on the server. To do this you |
120 | have to ensure Plink is \e{using} the SSH protocol. You can do this |
121 | in several ways: |
122 | |
123 | \b Use the \c{-ssh} option as described in |
124 | \k{plink-usage-interactive}. |
125 | |
126 | \b Set up a PuTTY saved session that describes the server you are |
127 | connecting to, and that also specifies the protocol as SSH. |
128 | |
129 | \b Set the Windows environment variable \c{PLINK_PROTOCOL} to the |
130 | word \c{ssh}. |
131 | |
132 | Usually Plink is not invoked directly by a user, but run |
133 | automatically by another process. Therefore you typically do not |
134 | want Plink to prompt you for a user name or a password. |
135 | |
ae62952c |
136 | Next, you are likely to need to avoid the various interactive |
137 | prompts Plink can produce. You might be prompted to verify the host |
138 | key of the server you're connecting to, to enter a user name, or to |
139 | enter a password. |
140 | |
141 | To avoid being prompted for the server host key when using Plink for |
142 | an automated connection, you should first make a \e{manual} |
143 | connection (using either of PuTTY or Plink) to the same server, |
144 | verify the host key (see \k{gs-hostkey} for more information), and |
145 | select Yes to add the host key to the Registry. After that, Plink |
146 | commands connecting to that server should not give a host key prompt |
147 | unless the host key changes. |
148 | |
2f8d6d43 |
149 | To avoid being prompted for a user name, you can: |
150 | |
151 | \b Use the \c{-l} option to specify a user name on the command line. |
152 | For example, \c{plink login.example.com -l fred}. |
153 | |
154 | \b Set up a PuTTY saved session that describes the server you are |
155 | connecting to, and that also specifies the username to log in as |
156 | (see \k{config-username}). |
157 | |
158 | To avoid being prompted for a password, you should almost certainly |
159 | set up public-key authentication. (See \k{pubkey} for a general |
160 | introduction to public-key authentication.) Again, you can do this |
161 | in two ways: |
162 | |
163 | \b Set up a PuTTY saved session that describes the server you are |
164 | connecting to, and that also specifies a private key file (see |
165 | \k{config-ssh-privkey}). For this to work without prompting, your |
166 | private key will need to have no passphrase. |
167 | |
168 | \b Store the private key in Pageant. See \k{pageant} for further |
169 | information. |
170 | |
171 | Once you have done all this, you should be able to run a remote |
172 | command on the SSH server machine and have it execute automatically |
173 | with no prompting: |
174 | |
175 | \c Z:\sysosd>plink login.example.com -l fred echo hello, world |
176 | \c hello, world |
177 | \c |
178 | \c Z:\sysosd> |
179 | |
180 | Or, if you have set up a saved session with all the connection |
181 | details: |
182 | |
183 | \c Z:\sysosd>plink mysession echo hello, world |
184 | \c hello, world |
185 | \c |
186 | \c Z:\sysosd> |
187 | |
188 | Then you can set up other programs to run this Plink command and |
189 | talk to it as if it were a process on the server machine. |
bace5431 |
190 | |
e117a742 |
191 | \S{plink-options} Plink command line options |
ff2ae367 |
192 | |
e117a742 |
193 | Plink accepts all the general command line options supported by the |
194 | PuTTY tools. See \k{using-general-opts} for a description of these |
195 | options. |
bace5431 |
196 | |
4d1cdf5d |
197 | Plink also supports some of its own options. The following sections |
198 | describe Plink's specific command-line options. |
199 | |
200 | \S2{plink-option-batch} \c{-batch}: disable all interactive prompts |
201 | |
202 | If you use the \c{-batch} option, Plink will never give an |
ff2ae367 |
203 | interactive prompt while establishing the connection. If the |
204 | server's host key is invalid, for example (see \k{gs-hostkey}), then |
205 | the connection will simply be abandoned instead of asking you what |
206 | to do next. |
207 | |
208 | This may help Plink's behaviour when it is used in automated |
209 | scripts: using \c{-batch}, if something goes wrong at connection |
210 | time, the batch job will fail rather than hang. |
211 | |
4d1cdf5d |
212 | \S2{plink-option-s} \c{-s}: remote command is SSH subsystem |
213 | |
214 | If you specify the \c{-s} option, Plink passes the specified command |
215 | as the name of an SSH \q{subsystem} rather than an ordinary command |
216 | line. |
217 | |
218 | (This option is only meaningful with the SSH-2 protocol.) |
219 | |
eaebbdf8 |
220 | \H{plink-batch} Using Plink in \i{batch files} and \i{scripts} |
bace5431 |
221 | |
2f8d6d43 |
222 | Once you have set up Plink to be able to log in to a remote server |
223 | without any interactive prompting (see \k{plink-usage-batch}), you |
224 | can use it for lots of scripting and batch purposes. For example, to |
225 | start a backup on a remote machine, you might use a command like: |
226 | |
227 | \c plink root@myserver /etc/backups/do-backup.sh |
228 | |
229 | Or perhaps you want to fetch all system log lines relating to a |
230 | particular web area: |
231 | |
35cffede |
232 | \c plink mysession grep /~fred/ /var/log/httpd/access.log > fredlog |
2f8d6d43 |
233 | |
234 | Any non-interactive command you could usefully run on the server |
235 | command line, you can run in a batch file using Plink in this way. |
236 | |
eaebbdf8 |
237 | \H{plink-cvs} Using Plink with \i{CVS} |
238 | |
7638530e |
239 | To use Plink with CVS, you need to set the environment variable |
240 | \c{CVS_RSH} to point to Plink: |
eaebbdf8 |
241 | |
242 | \c set CVS_RSH=\path\to\plink.exe |
7638530e |
243 | |
244 | You also need to arrange to be able to connect to a remote host |
2f8d6d43 |
245 | without any interactive prompts, as described in |
246 | \k{plink-usage-batch}. |
7638530e |
247 | |
2f8d6d43 |
248 | You should then be able to run CVS as follows: |
7638530e |
249 | |
250 | \c cvs -d :ext:user@sessionname:/path/to/repository co module |
251 | |
2f8d6d43 |
252 | If you specified a username in your saved session, you don't even |
253 | need to specify the \q{user} part of this, and you can just say: |
7638530e |
254 | |
255 | \c cvs -d :ext:sessionname:/path/to/repository co module |
256 | |
7638530e |
257 | \H{plink-wincvs} Using Plink with \i{WinCVS} |
258 | |
259 | Plink can also be used with WinCVS. Firstly, arrange for Plink to be |
2f8d6d43 |
260 | able to connect to a remote host non-interactively, as described in |
261 | \k{plink-usage-batch}. |
eaebbdf8 |
262 | |
2f8d6d43 |
263 | Then, in WinCVS, bring up the \q{Preferences} dialogue box from the |
d60c975d |
264 | \e{Admin} menu, and switch to the \q{Ports} tab. Tick the box there |
2f8d6d43 |
265 | labelled \q{Check for an alternate \cw{rsh} name} and in the text |
266 | entry field to the right enter the full path to \c{plink.exe}. |
267 | Select \q{OK} on the \q{Preferences} dialogue box. |
eaebbdf8 |
268 | |
d60c975d |
269 | Next, select \q{Command Line} from the WinCVS \q{Admin} menu, and type |
7638530e |
270 | a CVS command as in \k{plink-cvs}, for example: |
271 | |
272 | \c cvs -d :ext:user@hostname:/path/to/repository co module |
eaebbdf8 |
273 | |
a88d77d6 |
274 | or (if you're using a saved session): |
275 | |
276 | \c cvs -d :ext:user@sessionname:/path/to/repository co module |
277 | |
d60c975d |
278 | Select the folder you want to check out to with the \q{Change Folder} |
279 | button, and click \q{OK} to check out your module. Once you've got |
7638530e |
280 | modules checked out, WinCVS will happily invoke plink from the GUI for |
281 | CVS operations. |
bace5431 |
282 | |
2f8d6d43 |
283 | \# \H{plink-whatelse} Using Plink with... ? |