Differences

This shows you the differences between two versions of the page.

--- saltbush:sftp [2026-11-09 16:05] – Saltbush Terminal 1.4.0 guides slaterm
+++ saltbush:sftp [2026-11-11 14:59] (current) – Saltbush Terminal 1.9.2 guides slaterm
@@ Line 5: / Line 5: @@
 Right-click an SSH session in the **Session Manager** and choose **SFTP Browser…**, or choose **Transfer → SFTP Browser…** while an SSH tab is active. The browser logs in with the built-in SSH engine; questions such as a new host key, a password or a key passphrase appear in the window, with an **Answer** box.
-  * **Double-click** a folder to open it; **Up** goes to the parent folder; type a path and press **Go** to jump to it.
+The window has two panes: **This computer** on the left and the server on the right. The left pane starts in the session's download folder.
-  * Click to select, **Ctrl+click** to select several.
-  * **Download…** copies the selected files and folders to a folder you choose. Files are saved as ''name.part'' until complete.
+  * **Double-click** a folder to open it; **Up** goes to the parent folder; type a path and press **Go** to jump to it. **Home** (left side) goes to your home folder.
-  * **Upload Files…** and **Upload Folder…** copy to the folder shown. You can also drop files on the window.
+  * Click to select, **Ctrl+click** to select several, **Shift+click** to select a range.
-  * **New Folder…**, **Rename…** and **Delete…** (Delete asks first, and deletes folders with everything in them).
+  * **Upload >>** copies the selected files and folders on the left to the server folder on the right. **<< Download** copies the selected server files and folders to the folder on the left. Double-clicking a file copies it to the other side. You can also drop files on the window to upload them.
+  * **New Folder…**, **Rename…** and **Delete…** work on either side. Delete asks first and deletes folders with everything in them; on this computer it is permanent (no recycle bin).
+  * **Permissions…** (server side): tick **read**, **write** and **run** for the owner, the group and others, then **Apply**. The number (for example ''0644'') shows the same setting. It changes the selected items only, not what is inside a folder.
   * A progress bar shows the current file; **Cancel** stops the transfer.
-Several browser windows can be open at once. The browser cannot open sessions that need the OpenSSH client (a jump host or extra ''-o'' options); use **Transfer → Open SFTP Tab…** for those.
+==== Resuming transfers ====
+A file being copied is saved as ''name.part'' until it is complete: on this computer for downloads, on the server for uploads. If a transfer is cancelled or the connection drops, the ''.part'' file stays. Send the same file again to the same folder and Saltbush continues from where it stopped; the status line says how many files were resumed.
+Saltbush only continues when the ''.part'' file is not longer than the original and was written after the original last changed. Otherwise it starts again from the beginning. To force a fresh start, delete the ''.part'' file.
+Copied files keep their modification time. Uploads from Linux also keep the file's permissions (a runnable script stays runnable).
+Several browser windows can be open at once; each new one opens a little lower and to the right, and each side of a browser is in its own outlined box. The browser cannot open sessions that need the OpenSSH client (a jump host or extra ''-o'' options); use **Transfer → Open SFTP Tab…** for those.
+===== Copy Public Key to Server =====
+To log in with a key instead of a password, the server needs your public key in ''~/.ssh/authorized_keys''. Saltbush can put it there for you, like ''ssh-copy-id'':
+  - Right-click an SSH session in the **Session Manager** and choose **Copy Public Key to Server…**, or choose **Tools → Copy Public Key to Server…** (it uses the active SSH tab, or the session selected in the Session Manager). After making a key with **Generate…** on the session's SSH2 page, the **Copy to Server…** button does the same.
+  - Choose the public key (the ''.pub'' file). The session's own key is offered first, then the keys in ''~/.ssh''. **Browse…** picks another one.
+  - Click **Copy Key to Server** and answer the questions in the window (the server's host key the first time, then your password).
+Saltbush then:
+  * creates ''~/.ssh'' and ''~/.ssh/authorized_keys'' if they are missing,
+  * sets the permissions SSH insists on: ''700'' for the folder and ''600'' for the file (SSH ignores the file if others can write to it),
+  * adds the key unless it is already there (a commented-out copy does not count),
+  * logs in again with only that key, to check that it works.
+If the server has a file called ''authorised_keys'' (British spelling), Saltbush tells you: SSH only reads ''authorized_keys'' and ignores it.
+The server needs a Unix-like shell (Linux, BSD, macOS). Windows OpenSSH servers keep keys elsewhere (''administrators_authorized_keys'' for administrators), so add the key there by hand. Sessions that need the OpenSSH client (a jump host or extra ''-o'' options) cannot use it; run ''ssh-copy-id'' in a terminal instead.
 ===== SSH agent =====