Previous | Contents | Next

In this tutorial we'll show you how to transfer files from your local computer to your hosting account and vice versa through SSH (Secure Shell) using PuTTY. PuTTY is an application with which Windows users can connect to their hosting accounts through SSH and execute commands, transfer files, etc.

Learn how to move and copy your files via SSH. Once inside the application you will see two sections - left and right. You can easily copy/move files from the left side directory to the right side using a semi-visual approach. You can even use your mouse to select files and function keys to execute commands. Download File From Putty. File Transfer from Checkpoint FW to windows box using PuTTY (via serial/usb). You could put a USB into the firewall and copy the log or SCP it off the box. Plink.exe for ssh commands. Plink is able to ssh into a host and run a set of commands using the following syntax: > plink.exe -ssh -t -pw @ -m. Serial Communication using Putty Step – 10 Double click on downloaded ‘Putty.exe’, you will see a window like this: Step – 11 Select ‘serial’, insert com port and baud rate value and click on ‘Serial’ (Left pan), you will see a window look like this: Step – 12 Enter all the setting according your device and then click on open, Step -13 After clicking on ‘open’, you will see a window like this, now you are ready to communicate with your device. Other questions about 'How to transfer file in putty serial'. — Files transfer is similar to the actual file transfer available in Windows. — CCFile is blocked by the XP inside firewall. Press the Windows + R key. — Connect your iPhone 5 to computer through USB. — If you format you will lose all your data and that you don't want. In case that.

PSFTP, the PuTTY SFTP client, is a tool for transferring files securely between computers using an SSH connection.

PSFTP differs from PSCP in the following ways:

• PSCP should work on virtually every SSH server. PSFTP uses the new SFTP protocol, which is a feature of SSH 2 only. (PSCP will also use this protocol if it can, but there is an SSH 1 equivalent it can fall back to if it cannot.)
• PSFTP allows you to run an interactive file transfer session, much like the Windows ftp program. You can list the contents of directories, browse around the file system, issue multiple get and put commands, and eventually log out. By contrast, PSCP is designed to do a single file transfer operation and immediately terminate.

Section 6.1: Starting PSFTP

The usual way to start PSFTP is from a command prompt, much like PSCP. To do this, it will need either to be on your PATH or in your current directory. To add the directory containing PSFTP to your PATH environment variable, type into the console window:

Unlike PSCP, however, PSFTP has no complex command-line syntax; you just specify a host name and perhaps a user name:

or perhaps

Alternatively, if you just type psftp on its own (or double-click the PSFTP icon in the Windows GUI), you will see the PSFTP prompt, and a message telling you PSFTP has not connected to any server:

At this point you can type open server.example.com or open fred@server.example.com to start a session.

The following sections describe PSFTP's command-line options.

6.1.1 -l: specify a user name

The -l option is an alternative way to specify the user name to log in as, on the command line. Instead of typing psftp user@host, you can also type psftp host -l user.

This option does not work in the open command once PSFTP has started.

6.1.2 -P: specify a port number

If the host you specify is a saved session, PSFTP uses any port number specified in that saved session. If not, PSFTP uses the default SSH port, 22. The -P option allows you specify the port number to connect to for PSFTP's SSH connection.

6.1.3 -v: show verbose messages

The -v option to PSFTP makes it print verbose information about the establishing of the SSH connection. The information displayed is equivalent to what is shown in the PuTTY Event Log (section 3.1.3.1).

This information may be useful for debugging problems with PSFTP.

6.1.4 -pw: specify a password

If a password is required to connect to the host, PSFTP will interactively prompt you for it. However, this may not always be appropriate. If you are running PSFTP as part of some automated job, it will not be possible to enter a password by hand. The -pw option to PSFTP lets you specify the password to use on the command line.

Since specifying passwords in scripts is a bad idea for security reasons, you might want instead to consider using public-key authentication; see section 6.3.

6.1.5 -b: specify a file containing batch commands

In normal operation, PSFTP is an interactive program which displays a command line and accepts commands from the keyboard.

If you need to do automated tasks with PSFTP, you would probably prefer to specify a set of commands in advance and have them executed automatically. The -b option allows you to do this. You use it with a file name containing batch commands. For example, you might create a file called myscript.scr containing lines like this:

and then you could run the script by typing

When you run a batch script in this way, PSFTP will abort the script if any command fails to complete successfully. To change this behaviour, you can use the -be option (section 6.1.7).

6.1.6 -bc: display batch commands as they are run

The -bc option alters what PSFTP displays while processing a batch script. With the -bc option, PSFTP will display prompts and commands just as if the commands had been typed at the keyboard. So instead of seeing this:

you might see this:

6.1.7 -be: continue batch processing on errors

When running a batch file, this option causes PSFTP to continue processing even if a command fails to complete successfully.

You might want this to happen if you wanted to delete a file and didn't care if it was already not present, for example.

6.1.8 -batch: avoid interactive prompts

If you use the -batch option, PSFTP will never give an interactive prompt while establishing the connection. If the server's host key is invalid, for example (see section 2.2), then the connection will simply be abandoned instead of asking you what to do next.

This may help PSFTP's behaviour when it is used in automated scripts: using -batch, if something goes wrong at connection time, the batch job will fail rather than hang.

Section 6.2: Running PSFTP

Once you have started your PSFTP session, you will see a psftp> prompt. You can now type commands to perform file-transfer functions. This section lists all the available commands.

6.2.1 General quoting rules for PSFTP commands

Most PSFTP commands are considered by the PSFTP command interpreter as a sequence of words, separated by spaces. For example, the command ren oldfilename newfilename splits up into three words: ren (the command name), oldfilename (the name of the file to be renamed), and newfilename (the new name to give the file).

Sometimes you will need to specify file names that contain spaces. In order to do this, you can surround the file name with double quotes. This works equally well for local file names and remote file names:

The double quotes themselves will not appear as part of the file names; they are removed by PSFTP and their only effect is to stop the spaces inside them from acting as word separators.

If you need to use a double quote (on some types of remote system, such as Unix, you are allowed to use double quotes in file names), you can do this by doubling it. This works both inside and outside double quotes. For example, this command

will take a file whose current name is 'this' (with a double quote character at the beginning and the end) and rename it to a file whose name is a file with 'quotes' in it.

(The one exception to the PSFTP quoting rules is the ! command, which passes its command line straight to Windows without splitting it up into words at all. See section 6.2.16.)

6.2.2 The open command: start a session

If you started PSFTP by double-clicking in the GUI, or just by typing psftp at the command line, you will need to open a connection to an SFTP server before you can issue any other commands (except help and quit).

To create a connection, type open host.name, or if you need to specify a user name as well you can type open user@host.name.

Once you have issued this command, you will not be able to issue it again, even if the command fails (for example, if you mistype the host name or the connection times out). So if the connection is not opened successfully, PSFTP will terminate immediately.

6.2.3 The quit command: end your session

When you have finished your session, type the command quit to terminate PSFTP and return to the command line (or just close the PSFTP console window if you started it from the GUI).

You can also use the bye and exit commands, which have exactly the same effect.

6.2.4 The help command: get quick online help

If you type help, PSFTP will give a short list of the available commands.

If you type help with a command name - for example, help get - then PSFTP will give a short piece of help on that particular command.

6.2.5 The cd and pwd commands: changing the remote working directory

PSFTP maintains a notion of your 'working directory' on the server. This is the default directory that other commands will operate on. For example, if you type get filename.dat then PSFTP will look for filename.dat in your remote working directory on the server.

To change your remote working directory, use the cd command. To display your current remote working directory, type pwd.

6.2.6 The lcd and lpwd commands: changing the local working directory

As well as having a working directory on the remote server, PSFTP also has a working directory on your local machine (just like any other Windows process). This is the default local directory that other commands will operate on. For example, if you type get filename.dat then PSFTP will save the resulting file as filename.dat in your local working directory.

To change your local working directory, use the lcd command. To display your current local working directory, type lpwd.

6.2.7 The get command: fetch a file from the server

To download a file from the server and store it on your local PC, you use the get command.

In its simplest form, you just use this with a file name:

If you want to store the file locally under a different name, specify the local file name after the remote one:

This will fetch the file on the server called myfile.dat, but will save it to your local machine under the name newname.dat.

6.2.8 The put command: send a file to the server

To upload a file to the server from your local PC, you use the put command.

In its simplest form, you just use this with a file name:

If you want to store the file remotely under a different name, specify the remote file name after the local one:

This will send the local file called myfile.dat, but will store it on the server under the name newname.dat.

6.2.9 The reget and reput commands: resuming file transfers

If a file transfer fails half way through, and you end up with half the file stored on your disk, you can resume the file transfer using the reget and reput commands. These work exactly like the get and put commands, but they check for the presence of the half-written destination file and start transferring from where the last attempt left off.

The syntax of reget and reput is exactly the same as the syntax of get and put:

6.2.10 The dir command: list remote files

To list the files in your remote working directory, just type dir.

You can also list the contents of a different directory by typing dir followed by the directory name:

The ls command works exactly the same way as dir.

6.2.11 The chmod command: change permissions on remote files

PSFTP allows you to modify the file permissions on files on the server. You do this using the chmod command, which works very much like the Unix chmod command.

The basic syntax is chmod modes file, where modes represents a modification to the file permissions, and file is the filename to modify. For example:

The modes parameter can be a set of octal digits in the Unix style. (If you don't know what this means, you probably don't want to be using it!) Alternatively, it can be a list of permission modifications, separated by commas. Each modification consists of:

• The people affected by the modification. This can be u (the owning user), g (members of the owning group), or o (everybody else - 'others'), or some combination of those. It can also be a ('all') to affect everybody at once.
• A + or - sign, indicating whether permissions are to be added or removed.
• The actual permissions being added or removed. These can be r (permission to read the file), w (permission to write to the file), and x (permission to execute the file, or in the case of a directory, permission to access files within the directory).

So the above examples would do:

• The first example: go-rwx removes read, write and execute permissions for members of the owning group and everybody else (so the only permissions left are the ones for the file owner). u+w adds write permission for the file owner.
• The second example: a+r adds read permission for everybody.

In addition to all this, there are a few extra special cases for Unix systems. On non-Unix systems these are unlikely to be useful:

• You can specify u+s and u-s to add or remove the Unix set-user-ID bit. This is typically only useful for special purposes; refer to your Unix documentation if you're not sure about it.
• You can specify g+s and g-s to add or remove the Unix set-group-ID bit. On a file, this works similarly to the set-user-ID bit (see your Unix documentation again); on a directory it ensures that files created in the directory are accessible by members of the group that owns the directory.
• You can specify +t and -t to add or remove the Unix 'sticky bit'. When applied to a directory, this means that the owner of a file in that directory can delete the file (whereas normally only the owner of the directory would be allowed to).

6.2.12 The del command: delete remote files

To delete a file on the server, type del and then the filename:

The rm command works exactly the same way as del.

6.2.13 The mkdir command: create remote directories

To create a directory on the server, type mkdir and then the directory name:

6.2.14 The rmdir command: remove remote directories

To remove a directory on the server, type rmdir and then the directory name:

Most SFTP servers will probably refuse to remove a directory if the directory has anything in it, so you will need to delete the contents first.

6.2.15 The ren command: rename remote files

To rename a file on the server, type ren, then the current file name, and then the new file name:

The rename and mv commands work exactly the same way as ren.

6.2.16 The ! command: run a local Windows command

You can run local Windows commands using the ! command. This is the only PSFTP command that is not subject to the command quoting rules given in section 6.2.1. If any command line begins with the ! character, then the rest of the line will be passed straight to Windows without further translation.

For example, if you want to move an existing copy of a file out of the way before downloading an updated version, you might type:

using the Windows ren command to rename files on your local PC.

Section 6.3: Using public key authentication with PSFTP

Like PuTTY, PSFTP can authenticate using a public key instead of a password. There are two ways you can do this.

Firstly, PSFTP can use PuTTY saved sessions in place of hostnames. So you might do this:

• Run PuTTY, and create a PuTTY saved session (see section 4.1.2) which specifies your private key file (see section 4.16.5). You will probably also want to specify a username to log in as (see section 4.12.2).
• In PSFTP, you can now use the name of the session instead of a hostname: type psftp sessionname, where sessionname is replaced by the name of your saved session.

Secondly, PSFTP will attempt to authenticate using Pageant if Pageant is running (see chapter 9). So you would do this:

• Ensure Pageant is running, and has your private key stored in it.
• Specify a user and host name to PSFTP as normal. PSFTP will automatically detect Pageant and try to use the keys within it.

For more general information on public-key authentication, see chapter 8.

Previous | Contents | Next

Comments to putty@projects.tartarus.org[$Id: blurb.but,v 1.5 2001/12/16 14:56:02 simon Exp $]
[$Id: intro.but,v 1.4 2001/11/25 16:57:45 simon Exp $]

Putty Copy File To Local Machine

[$Id: gs.but,v 1.6 2001/12/06 20:05:39 simon Exp $]

How To Transfer File Using Ftp

[$Id: using.but,v 1.5 2001/12/15 12:15:24 simon Exp $]
[$Id: config.but,v 1.24 2001/12/29 17:25:07 simon Exp $]
[$Id: pscp.but,v 1.20 2001/12/31 16:15:19 simon Exp $]
[$Id: psftp.but,v 1.4 2001/12/31 16:15:19 simon Exp $]
[$Id: plink.but,v 1.13 2001/12/31 16:15:19 simon Exp $]
[$Id: pubkey.but,v 1.13 2001/12/14 09:58:07 simon Exp $]
[$Id: pageant.but,v 1.7 2001/12/20 15:27:40 simon Exp $]
[$Id: faq.but,v 1.18 2002/01/14 12:16:58 simon Exp $]
[$Id: feedback.but,v 1.2 2001/12/16 15:14:36 simon Exp $]
[$Id: licence.but,v 1.2 2002/01/08 11:57:32 simon Exp $]

How To Transfer File Using Filezilla

Introduction

PuTTY is a popular terminal emulator for Windows, but it is not only limited to Windows operating system. Being free and open source, it is popular among Linux users too. PuTTY supports a wide range of protocols such as serial, SSH, Telnet, rlogin, SCP, SFTP etc. PuTTY is used by seasoned sysadmins and hobbyists/maker-crowd alike. Sysadmins generally use PuTTY as an SSH and telnet client whereas the Maker community widely uses PuTTY for interfacing with the serial ports on their hardware. PuTTY ships with a command line tool named “psftp”, the PuTTY SFTP client, which is used to securely transfer files between computers over an SSH connection. More about PuTTY here

This article will walk through on how to install PuTTY on Ubuntu 14.04 and higher.

The simplest way to install PuTTY in Ubuntu Linux is via terminal i.e, the command line. Follow the steps below to install PuTTY on Ubuntu.

Step 1

Login into Ubuntu Desktop. Press Ctrl + Atl + T to open GNOME terminal. If for some reason the shortcut didn’t work, run the Terminal from the Ubuntu Dash.

Step 2

Run the following command in the terminal.

This command updates the Ubuntu package list with latest one. If this command is skipped, there is a good chance that Ubuntu might install older version of the softwares instead of the latest version due to the fact that it only had the older list with older version of softwares. So, whenever installing new software or intending to upgrade the software versions, it is a good idea to run this command first. The sudo prefix at the start of the command instructs the terminal to run the command as root since installing and upgrading softwares is a privilege operation and should not be performed by users which do not have sufficient access. Provide the user password when prompted by sudo and hit Enter.

Step 3

Install PuTTY using the command below.

sudo apt-get install -y putty

Step 4

PuTTY should be installed. Run it from the terminal using “putty” as command, or from the Dash.

As visible in the PuTTY screenshot above, it provides a range of connection type to choose from: Raw, Telnet, Rlogin, SSH and Serial. It also ships with command line tools for SCP (pscp), SFTP (psftp), RSA and DSA key generator (puttygen) etc, which can be run from the terminal.

Optional: Compiling from source

While it is not recommended for beginners to compile PuTTY from source, one can choose to compile PuTTY from source. Download the PuTTY source files here. Extract the archive file using the command and follow the README file inside the archive to compile PuTTY from source.