The SSH library
The SCP subsystem has far less functionnality than the SFTP subsystem. However, if you only need to copy files from and to the remote system, it does its job.
Like in the SFTP subsystem, you don't handle the SSH channels directly. Instead, you open a "SCP session".
When you open your SCP session, you have to choose between read or write mode. You can't do both in the same session. So you specify either SSH_SCP_READ or SSH_SCP_WRITE as the second parameter of function ssh_scp_new().
Another important mode flag for opening your SCP session is SSH_SCP_RECURSIVE. When you use SSH_SCP_RECURSIVE, you declare that you are willing to emulate the behaviour of "scp -r" command in your program, no matter it is for reading or for writing.
Once your session is created, you initialize it with ssh_scp_init(). When you have finished transferring files, you terminate the SCP connection with ssh_scp_close(). Finally, you can dispose the SCP connection with ssh_scp_free().
The example below does the maintenance work to open a SCP connection for writing in recursive mode:
The example below shows how to open a connection to read a single file:
You create directories with ssh_scp_push_directory(). In recursive mode, you are placed in this directory once it is created. If the directory already exists and if you are in recursive mode, you simply enter that directory.
Creating files is done in two steps. First, you prepare the writing with ssh_scp_push_file(). Then, you write the data with ssh_scp_write(). The length of the data to write must be identical between both function calls. There's no need to "open" nor "close" the file, this is done automatically on the remote end. If the file already exists, it is overwritten and truncated.
The following example creates a new directory named "helloworld/", then creates a file named "helloworld.txt" in that directory:
Let's say you want to copy the following tree of files to the remote site:
+-- file1 +-- B --+ | +-- file2 -- A --+ | +-- file3 +-- C --+ +-- file4
You would do it that way:
To leave a directory, call ssh_scp_leave_directory().
To receive files, you pull requests from the other side with ssh_scp_pull_request(). If this function returns SSH_SCP_REQUEST_NEWFILE, then you must get ready for the reception. You can get the size of the data to receive with ssh_scp_request_get_size() and allocate a buffer accordingly. When you are ready, you accept the request with ssh_scp_accept_request(), then read the data with ssh_scp_read().
The following example receives a single file. The name of the file to receive has been given earlier, when the scp session was opened:
In this example, since we just requested a single file, we expect ssh_scp_request() to return SSH_SCP_REQUEST_NEWFILE first, then SSH_SCP_REQUEST_EOF. That's quite a naive approach; for example, the remote server might send a warning as well (return code SSH_SCP_REQUEST_WARNING) and the example would fail. A more comprehensive reception program would receive the requests in a loop and analyze them carefully until SSH_SCP_REQUEST_EOF has been received.
If you opened the SCP session in recursive mode, the remote end will be telling you when to change directory.
In that case, when ssh_scp_pull_request() answers SSH_SCP_REQUEST_NEWDIRECTORY, you should make that local directory (if it does not exist yet) and enter it. When ssh_scp_pull_request() answers SSH_SCP_REQUEST_ENDDIRECTORY, you should leave the current directory.