![]() ![]()
If you have already set up a PuTTY saved session, then instead of supplying a host name, you can give the saved session name. In order to connect with a different protocol, you can give the command line options -ssh, -ssh-connection, -telnet, -rlogin, or -raw. Interactive connections like this are not the main point of Plink. So if you run any full-screen applications, for example, you can expect to see strange characters appearing in your window. The output sent by the server will be written straight to your command prompt window, which will most likely not interpret terminal control codes in the way the server expects it to. You should then be able to log in as normal and run a session. To make a simple interactive connection to a remote server, just type plink and then the host name: Once this works, you are ready to use Plink. Test whether a connection-sharing upstream exists Open tunnel in place of session (SSH-2 only)Ĭontrol what happens when a log file already exists ![]() N don't start a shell/command (SSH-2 only) s remote command is an SSH subsystem (SSH-2 only) no-antispoof omit anti-spoofing prompt after authentication sanitise-stderr, -sanitise-stdout, -no-sanitise-stderr, -no-sanitise-stdoutĭo/don't strip control chars from standard output/error Manually specify a host key (may be repeated) noshare disable use of connection sharing i key private key file for user authenticationĭisconnect if SSH authentication succeeds trivially 1 -2 force use of particular SSH protocol version #NEW WINDOWS TERMINAL GREP PASSWORD#pwfile file login with password read from specified file The following options only apply to SSH connections: #NEW WINDOWS TERMINAL GREP SERIAL#Specify the serial configuration (serial only) load sessname Load settings from saved sessionįorce use of the bare ssh-connection protocol pgpfp print PGP key fingerprints and exit ("host" can also be a PuTTY saved session name) #NEW WINDOWS TERMINAL GREP HOW TO#This tells you the version of Plink you're using, and gives you a brief summary of how to use Plink: Once you've got a console window to type into, you can just type plink on its own to bring up a usage message. This section describes the basics of how to use Plink for interactive logins and for automated processes. On Windows 95, 98, and ME, you will need to edit your AUTOEXEC.BAT to include a set command like the one above. To set your PATH more permanently on Windows NT, 2000, and XP, use the Environment tab of the System Control Panel. ![]() This will only work for the lifetime of that particular console window. Set PATH=C:\path\to\putty\directory %PATH% To add the directory containing Plink to your PATH environment variable, type into the console window: In order to use Plink, the file plink.exe will need either to be on your PATH or in your current directory. It should be available from the Programs section of your Start Menu. In Windows 95, 98, and ME, this is called an ‘MS-DOS Prompt’, and in Windows NT, 2000, and XP, it is called a ‘Command Prompt’. This means that you cannot just double-click on its icon to run it and instead you have to bring up a console window. Plink is probably not what you want if you want to run an interactive session in a console window. It is mostly used for automated operations, such as making CVS access a repository on a remote server. Plink is a command-line connection tool similar to UNIX ssh.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |