Kalgoorlie Retro Docs

Documentation for the Kalgoorlie Retro BBS, its games and servers

User Tools

Site Tools


saltbush:sftp

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
saltbush:sftp [2026-11-09 23:38] – Saltbush Terminal 1.6.0 guides slatermsaltbush:sftp [2026-11-11 14:59] (current) – Saltbush Terminal 1.9.2 guides slaterm
Line 22: Line 22:
 Copied files keep their modification time. Uploads from Linux also keep the file's permissions (a runnable script stays runnable). 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. The browser cannot open sessions that need the OpenSSH client (a jump host or extra ''-o'' options); use **Transfer → Open SFTP Tab…** for those.+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 ===== ===== SSH agent =====
saltbush/sftp.1794267514.txt.gz · Last modified: by slaterm