Help › Functions

Terminal and SSH

Work with SSH servers – directly or through one of your devices, with keys that stay on this device.

FreemacOSWindowsiPhone & iPad · Coming soonWebAndroidLinux

DeskRanger connects you to your servers over SSH: the NAS at home, a Raspberry Pi or a server in a data centre. The hosts belong to your account and appear on all your devices. Passwords and keys, however, stay on the device where you enter or create them.

macOS

You find everything under Terminal in the sidebar. At the top are Your devices, whose terminal you open without SSH, below them Favorites and Recently Connected, then your SSH hosts, sorted by your account's groups. This Mac's keys are in the Keys section.

The Terminal page: your devices, favorites, recently connected and the SSH hosts in their groups with tagsThe Terminal page: your devices, favorites, recently connected and the SSH hosts in their groups with tags

Windows

You find everything under Terminal in the sidebar: Favorites, Recently Connected and your SSH hosts, sorted by your account's groups. This PC's keys are in the Keys section.

iPhone & iPad

On the iPhone you find everything under More › Terminal, on the iPad under Terminal in the sidebar: at the top Open terminals, then Your devices, Favorites, Recently Connected and your SSH hosts by group. This device's keys are in the Keys section.

The Terminal page: your devices, favorites, recently connected and the SSH hosts in their groups with tagsThe Terminal page: your devices, favorites, recently connected and the SSH hosts in their groups with tags

Android

Open the menu and choose Terminal. At the top are Your devices, whose terminal you open without SSH, below them Favorites and Recently Connected, then your SSH hosts, sorted by your account's groups. This device's keys are in the Keys section.

The Terminal page: your devices, favorites, recently connected and the SSH hosts in their groups with tagsThe Terminal page: your devices, favorites, recently connected and the SSH hosts in their groups with tags

The terminal of your own devices

For your own devices with DeskRanger you need no SSH and no open port.

macOS

Choose Open Terminal under Your devices on the Terminal page or on the card of a Mac, PC or Linux device. A terminal opens with your shell on that device, as if you were sitting in front of it. If a session with the device is already running, you also find Open Terminal in the session window's menu.

The Mac Studio's terminal: the Mac mini would like the keyboard, with “Keep” and “Hand Over Keyboard”The Mac Studio's terminal: the Mac mini would like the keyboard, with “Keep” and “Hand Over Keyboard”

Windows

Choose Open Terminal under Your devices on the Terminal page, on a device's card or in its menu. A tab opens with the device's shell, as if you were sitting in front of it. If a session with the device is already running, you also find Open Terminal in the session window's menu. On a Windows PC the shell is PowerShell.

iPhone & iPad

Tap a device under Your devices, or touch and hold its card and choose Open Terminal. The terminal covers the app; the down arrow takes you back to the list and the terminal stays open.

The Mac Studio's terminal: the Mac mini would like the keyboard, with “Keep” and “Hand Over Keyboard”The Mac Studio's terminal: the Mac mini would like the keyboard, with “Keep” and “Hand Over Keyboard”

Web

In the browser console, open the menu of a device that offers a terminal and choose Open Terminal. The terminal opens full screen with the shell of that device. The device's person has to allow the connection, just as for a screen session; for an unattended device you confirm on another of your devices. Request Keyboard and Hand Over Keyboard work as in the apps, Disconnect – Keep Running leaves the shell running, and A− and A+ change the text size. Ctrl-click (⌘-click on a Mac) opens a link. On a touch device a key row sits above the on-screen keyboard with Esc, Ctrl, Alt, Tab, the arrows and |, ~, /, -: Ctrl and Alt apply to the next key, tapped twice they stay on, and an arrow held down sends Home, End, Page Up or Page Down. You choose a terminal's profile (colors, font, cursor, scrollback) in the ⋯ menu under Profile …; Import Color Scheme … makes a profile from a color scheme file, and it applies in this browser only. You edit profiles in the apps; SSH hosts and split panes are described under “SSH hosts in the browser” below.

Android

Tap Terminal on a server's card, choose Open Terminal in a card's menu, or tap the device on the Terminal page. Switch between open terminals with the bar at the top. The terminal's menu has Disconnect – Keep Running and the device's other terminals. If the connection drops while DeskRanger is in the background, it reconnects as soon as you come back.

The Mac Studio's terminal: the Mac mini would like the keyboard, with “Keep” and “Hand Over Keyboard”The Mac Studio's terminal: the Mac mini would like the keyboard, with “Keep” and “Hand Over Keyboard”
  • The shell runs as the person signed in on the device, with their rights. Never as administrator (root).
  • When nobody is signed in on a Linux computer and no terminal user is set, the terminal shows “Terminal at the sign-in screen”: you type the user name and password of an account of that computer, and the shell runs as that account; a strip says “Signed in as “…” at the sign-in screen”. This works only from your own devices; the password goes to the computer encrypted only and is stored nowhere. If something is wrong it says “The user name or password is wrong. … tries left.”; after five wrong passwords, tries pause for 15 minutes (“Too many wrong tries. Try again in … minutes.”). Your other devices hear of it: they show the notice “Terminal at the sign-in screen” when one of your own devices opened a terminal there, and “Sign-in paused” when the tries paused. DeskRanger never reports a single wrong password, and never the account or the password. The form is in the apps for Mac, Windows and Linux; the other apps say “Nobody is signed in on this device.”.
  • Terminals to your own devices do not count as a session of your plan.
  • Programs in this shell may put text on the clipboard of the device you are using. They can never read your clipboard.
  • If you open the same terminal on a second device, you watch there. Request Keyboard asks for the keyboard, Hand Over Keyboard passes it on. Only one device types at a time.
  • Disconnect – Keep Running closes the window, the shell keeps running. If the connection drops, DeskRanger reconnects by itself. From any of your devices you continue where you were, with the screen and the history.

macOS

On the Mac whose terminal is used, the menu bar menu, the red indicator and the banner show every terminal and who watches or types. End disconnects a device, End ends the shell. How long a shell keeps running after a dropped connection is set in the settings under Keep Terminals Running.

The menu bar menu: who uses this Mac's terminal, who types and who watches, with “Disconnect” and “End”The menu bar menu: who uses this Mac's terminal, who types and who watches, with “Disconnect” and “End”
The “Keep Terminals Running” setting under “This Mac”The “Keep Terminals Running” setting under “This Mac”

Windows

On the PC whose terminal is used, the icon in the notification area is red, a red banner with End shows at the top of the screen, and the notification area's menu shows every terminal and who watches or types. End disconnects a device, End ends the shell. How long a shell keeps running after a dropped connection is set in the settings under This PC with Keep Terminals Running. The shell runs with your normal rights – if DeskRanger was started as administrator, the PC offers no terminal.

iPhone & iPad

If you switch to another app on the iPhone or iPad, the terminal stays connected for a short while. If you stay away longer, DeskRanger disconnects and the shell keeps running on the device. When you come back, DeskRanger reconnects to the same shell by itself. An SSH connection to a server, however, drops when iOS suspends the app; Reconnect connects again. If you close a terminal with the ×, it ends at once: a device's shell closes for you, the SSH connection is ended.

Android

If you switch to another app on Android, a device's terminal stays connected for a short while. If you stay away longer, DeskRanger disconnects it and the shell keeps running on the device; nobody counts as connected on the device or in your list of active sessions. When you come back, DeskRanger reconnects to the same shell by itself. An SSH connection to a server cannot be resumed: DeskRanger keeps it open in the background while it runs, and Android shows the notification "Terminal connected" for it. It goes away when the last SSH connection ends. If you close a terminal with the ×, it ends at once: a device's shell closes for you, the SSH connection is ended.

If someone from another account wants to open your terminal, DeskRanger always asks and names Terminal. If you decline, no shell starts.

“This device offers no terminal.”

DeskRanger must be running on the device and allow connections. There is no shell before sign-in, in the Mac App Store version, or when DeskRanger was started as administrator on a PC.

SSH through one of your own devices

macOS

If this Mac serves as the way into its network and you allow the terminal to one of your own devices, that device can also reach SSH servers in your network from inside its session, without those servers having to be on the internet. The request then reads Terminal (also SSH through this device); allowing it allows both. Only SSH entries you released for this Mac as the way in are reachable, and only addresses in your local network. Whoever uses SSH is listed on the Network page among the running tunnels: “‹device› is using SSH to ‹name› (‹address›) through this Mac”, with End. Pausing the session opens no new connections; ending the session closes all of them. A request from another account or with a support code never mentions SSH and never gets it.

Windows

If this PC serves as the way into its network and you allow the terminal to one of your own devices, that device can also reach SSH servers in your network from inside its session, without those servers having to be on the internet. The request then reads Terminal (also SSH through this device); allowing it allows both. Only SSH entries you released for this PC as the way in are reachable, and only addresses in your local network. This holds while someone is signed in on the PC and DeskRanger runs there, even if only in the notification area; at the sign-in screen there is no SSH through the PC. Whoever uses SSH is listed among the running connections: “‹device› is using SSH to ‹name› (‹address›) through this PC”, with End. Ending the session closes all of them. A request from another account or with a support code never mentions SSH and never gets it.

iPhone & iPad

This function is coming soon to iPhone & iPad.

Linux

SSH through this Linux computer from a DeskRanger session comes later. The platform overview in this article shows the current status.

Keep a session on one of your own devices

If another of your devices is always on, such as a Mac mini or a PC in the office, it can hold an SSH session for you. The session keeps running on that device when you close your window, close the lid or change networks. You continue it from any of your devices, with the full screen as you left it.

For this, pick an SSH host in the terminal and then Keep Session on …, in the host's context menu or with the arrow next to the connect button. The entry only appears when another of your devices is online and offers to hold SSH sessions, and the host has a user and is reached without a gateway device and without jump hosts: the device makes the connection itself.

You sign in as usual. The device asks you when the server is seen for the first time (trust its key), for the password or for a code. The questions appear on the device you are sitting at, in the same windows as for a normal connection. Your keys do not leave this device: it signs the login itself, the holding device only sees the result. A password is never remembered.

Held sessions are in the list of other terminals on the device, marked „held“. There you continue them or watch them from a second device. A held session keeps running even when nobody is watching. With Disconnect – Keep Running you leave it running; if you close it, the session ends on the server.

Windows

A PC holds SSH sessions under the same conditions as it shares its terminal: it belongs to your account, someone is signed in and DeskRanger runs, even if only in the notification area. At the sign-in screen, when DeskRanger was started as administrator, and on a PC that was paired without an account, it holds nothing. The PC makes the SSH connection itself, with its own network access. The notification area's menu lists the held sessions with the terminals: “‹device› is using the terminal (‹user@server›)” while someone watches, otherwise “‹user@server› keeps running, nobody connected”. End ends one at once. Its row carries the mark “held”, on a Mac in the live menu as well. The setting Keep Terminals Running does not shorten a held session: it keeps running even when nobody is watching. Signing out of Windows or restarting the PC ends held sessions.

iPhone & iPad

On the iPhone and iPad touch and hold an SSH host and choose Keep Session on … (with one device it is named after it). The terminal opens over the app as usual; the questions of the login appear in it. The phone itself does not hold sessions, because iOS suspends the app in the background; it attaches to a session another of your devices keeps, and picks it up again from the list of other terminals when you come back.

Android

On Android open the ⋮ menu of an SSH host on the Terminal page and choose Keep Session on … (with one device it is named after it, with several you pick one). The session opens in a tab as usual; the questions of the login appear there: whether to trust a new server key, the password or the server's other questions. The password you type is never remembered for a held session. The phone itself does not hold sessions; it attaches to a session another of your devices keeps. In the tab's ⋮ menu you find Disconnect – Keep Running, which leaves the session running, and the held sessions of the device (“‹server› · held since ‹time›”) and its shells to continue or watch. If the device cannot reach the server, or the server refuses the login, the tab says so.

Linux

In the Terminal page, the row of an SSH host has a button with a server icon (tooltip: Keep Session on …) when a device of yours is online and offers to hold SSH sessions; its menu lists the devices, “Keep Session on ‹device›”. The session opens in a tab of the terminal window. At the top of the tab you find Disconnect – Keep Running, which leaves the session running, and, as soon as the device runs other terminals, the button “Other Terminals on …” with the held sessions (“‹server› · held since ‹time›”) and shells to watch or continue. Closing the tab ends the session on the server. A Linux computer holds SSH sessions under the same conditions as it shares its terminal, whether DeskRanger Server (with a terminal user) or the DeskRanger app with sharing switched on; the computer makes the SSH connection itself. A password is never remembered for a held session. On the holding Linux computer the DeskRanger app lists every terminal in a window of its own that cannot be closed while one runs: who uses it and who types, the mark “held” on a held session, End per terminal and End per device. The same rows are in the bubble of “This computer”.

tmux or zellij when connecting

If the server has tmux or zellij, DeskRanger can resume the session “deskranger” in it when connecting instead of opening a new shell. If the connection drops, everything keeps running on the server; the next time you connect you are right back where you were. This needs no other device of yours, only the program on the server. If the server lacks it, the normal shell opens.

macOS

Edit the SSH host, open Advanced and choose Resume tmux session or Resume zellij session under On connect. Normal shell opens the normal shell again.

Windows

Edit the SSH host, open Advanced and choose Resume tmux session or Resume zellij session under On connect. Normal shell opens the normal shell again.

iPhone & iPad

Edit the SSH host, open Advanced and choose Resume tmux session or Resume zellij session under On connect. Normal shell opens the normal shell again.

Web

Edit the SSH host and choose Resume tmux session or Resume zellij session under On connect. Normal shell opens the normal shell again. The console in the browser then opens the host with the chosen session.

Android

Edit the SSH host and choose under On connect Resume tmux session or Resume zellij session. Normal shell opens the normal shell again.

Linux

Edit the SSH host and choose Resume tmux session or Resume zellij session under On connect. Normal shell opens the normal shell again.

The choice belongs to the host and applies on all your devices, also where you cannot change it yet. In tmux you detach with Ctrl-b and then d; the connection ends, the session keeps running.

Add an SSH host

macOS

Choose Add Device and then Add a remote desktop, VNC or SSH server. Switch to SSH at the top and enter the address, port and User name. Under Sign-in you choose whether this Mac signs in with its keys, with the password or automatically. You can enter the password right away under Password (stored on this device only) (Passwords and keys).

Add an SSH host: address, user, sign-in, key and “Access via”Add an SSH host: address, user, sign-in, key and “Access via”

Windows

Choose Add Device and then Add a remote desktop, VNC or SSH server, or Add SSH Host on the Terminal page. Switch to SSH at the top and enter the address, port and User name. Under Sign-in you choose whether this PC signs in with its keys, with the password or automatically. You can enter the password right away under Password (stored on this device only) (Passwords and keys). Under Advanced you find the SSH agent, agent forwarding, the SSH certificate, ProxyJump and environment variables.

iPhone & iPad

Tap “+” on the Terminal page, or choose SSH Host under Add Device. Enter the address, port and User name and set under Sign-in how this device signs in. In a host's menu (touch and hold) choose Edit Host…. Remote desktops are still added on the Mac.

Add an SSH host: address, user, sign-in, key and “Access via”Add an SSH host: address, user, sign-in, key and “Access via”

Android

On the Terminal page, tap “+” (Add SSH Host) at the top. Enter the address, port and User name, and choose under Sign-in how this device signs in. Here you also choose Access via, ProxyJump via and Agent forwarding. DeskRanger asks for the password on the first connection; with Remember on this device it stays on this device. You edit remote desktops on the Mac or PC.

Add an SSH host: address, user, sign-in, key and “Access via”Add an SSH host: address, user, sign-in, key and “Access via”

Linux

On the Terminal page, choose Add SSH Host. Enter the address, port and User name, and under Sign-in choose whether this computer signs in with its keys, with the password or automatically. Under Key you can pick one of this computer's keys for the host, otherwise DeskRanger tries all of them. Under Environment variables you can add variables for the server's shell; their values stay protected on this computer, and the server decides which variables it accepts. The key choice applies to this computer only; the variables travel with your other devices only if you switched on syncing of logins (Passwords and keys).

If the server is in another network, choose a device that runs there under Access via. DeskRanger then passes the encrypted SSH connection through that device, without any port open on the router. The device in between sees only encrypted data.

SSH hosts in the browser

iPhone & iPad

This function is coming soon to iPhone & iPad.

Web

Open Terminal, a link on the devices page. You see your Your devices and your SSH hosts; the search field finds a host by name, address or tag, the star keeps a favourite at the top. Add SSH Host opens the form for an SSH host: name, address, port, user and Access via. The browser reaches a server only through one of your own devices in the same network, so choose that device there; the password goes encrypted straight to the server and is not stored.

Each host opens in a tab. The first time, the browser shows the server's host key with its fingerprint; Trust and connect remembers it, and if it ever changes, DeskRanger stops and shows both. If you know why it changed, Edit Host… opens the host's form there; choose Forget Host Key and open the host again: it asks again with the fingerprint. A tab's menu splits it side by side (Split side by side) or top and bottom (Split top and bottom), into several panes, each with its own connection. Saved layouts are not available in the browser. You choose a host's profile in its form under Profile.

Ctrl+K (⌘K on a Mac) opens Quick connect: type a few letters of a device or host and press Enter. Inside a terminal pane the shell keeps Ctrl+K for itself, so use Ctrl+Shift+K (⌘⇧K on a Mac) there. Type user@host to sign in as another user; an address that is not saved yet opens the form with the entries filled in, because a device serves only saved hosts. The ranking of the matches is computed in the browser and can differ slightly from the apps.

Hosts reached through jump servers (ProxyJump) you can edit in the browser, but they do not open there yet: the row says so. Use the apps for these hosts for now.

Taking over hosts from other programs

Import Hosts… takes over your hosts from another SSH program. DeskRanger first shows what it found. Hosts your account has already are not chosen. You decide which ones come in.

macOS

You find the command in the menu of the SSH Host button. Read ~/.ssh/config reads your SSH configuration including the files it includes. Choose File… picks an export file from PuTTY, MobaXterm, SecureCRT or a CSV file, for example from Termius or Royal TS.

Import hosts: the SSH configuration read, with groups, a jump host and a host that is already thereImport hosts: the SSH configuration read, with groups, a jump host and a host that is already there

Windows

You find the command on the Terminal page next to SSH Host. This PC's PuTTY sessions reads the sessions PuTTY saved on this PC. Read ~/.ssh/config reads your SSH configuration. Choose File… picks an export file from MobaXterm, SecureCRT or a CSV file.

iPhone & iPad

You find the command in the menu of the SSH Host button: touch and hold it. With Choose File… you pick an export file from PuTTY, MobaXterm, SecureCRT or a CSV file, for example from Termius or Royal TS, or an SSH config.

Android

You find the command on the Terminal page in the ⋮ menu at the top right. With Choose File… you pick an export file from PuTTY, MobaXterm, SecureCRT or a CSV file, for example from Termius or Royal TS, or an SSH config.

  • Name, address, port, user, folder (as a group), tags, jump hosts and forwards come in.
  • Passwords and private keys never come in. If a key file is named, DeskRanger shows it. You then take over the key in the Keys section.
  • A forward that the other program shared on the network first works for this device only. You can share it deliberately in the host's settings.
  • DeskRanger asks about the host key on the first connection, as always.

Jump through other servers

Some servers can only be reached through another one, for example a bastion host. Add each server as an SSH host. On the destination, choose Add hop at ProxyJump via under Advanced, in the order in which DeskRanger jumps through them.

  • Each server has its own host key. On the first connection DeskRanger asks for each one, then never again.
  • If the first server can only be reached from another network, choose one of your devices under Access via on that server.

Port forwards

A forward lets you reach services behind a server as if they ran on your device – a database or a web interface, for example.

  • Local: a port on your device leads to a destination the server can reach.
  • Remote: a port on the server leads to a destination your device can reach.
  • SOCKS proxy: set a SOCKS proxy at 127.0.0.1 and the chosen port in your browser. Its pages then go online through the server.

Forwards that should start with every connection belong in the host's settings under Port forwards. For the running connection, choose Port forwards and Add Forward … in the terminal window. You see running forwards there, on the Mac, on Windows and on Linux also under Terminal › Port forwards, on your other devices under Access & Tunnels; End ends one.

macOS

A terminal window's port forwards: local to the database, a SOCKS proxy, one the server refused and one shared on the network that waits for “Start” on this deviceA terminal window's port forwards: local to the database, a SOCKS proxy, one the server refused and one shared on the network that waits for “Start” on this device
Terminal › “Forwards” with the running SSH forwards and “End”Terminal › “Forwards” with the running SSH forwards and “End”

iPhone & iPad

Start forwards for the open connection in the terminal's ••• menu under Port forwards with Add Forward …. They run while the app is open. Forwards that start with every connection are set up on the Mac or PC; on this device you see them in the host’s settings (touch and hold the host, then Edit Host…) under Port forwards, and you start them with Start.

Android

Start forwards for the open connection in the terminal's menu under Port forwards with Add Forward …. They run while a terminal is open – also in the background. Forwards that start with every connection are set up on the Mac or PC; on this phone you start them with Start.

A forward reaches only your own device at first. Only with Share on the network can other devices on your network use it too – without signing in. Turn this on only in a network you trust.

A host's settings apply on all your devices. So a forward that opens this device or its network – shared on the network, or any Remote – starts on each device only once you agree there. It is listed as “Starts only after you agree on this device”; Start starts it, and this device remembers your yes for the host. If you set up the forward on this device yourself, DeskRanger does not ask here. If it changes elsewhere, or the host points to another server, DeskRanger asks again.

“The server refused this forward.”

The server does not allow forwarding (AllowTcpForwarding), the port is already in use there, or it is below 1024 and needs administrator rights on the server.

Files on the server

Under Files, your SSH hosts are listed at Servers (SFTP). When you open one, DeskRanger signs in as in the terminal: through the same jumps, with the same keys, and the first time with the host key question. Then you see your home folder and the whole server.

iPhone & iPad

This function is coming soon to iPhone & iPad.

Android

On Android you can browse a host, download and upload: Download saves a file in your download folder, uploading takes files from the system picker. The fingerprint and password questions are the terminal’s. Renaming, moving, deleting and editing are on the Mac and the PC.

  • Downloading, uploading, new folders, renaming and moving work as with your devices. Everything goes into the same Transfers list.
  • If the connection breaks or you pause, it continues later with the bytes that are already there – in both directions. If the server has a checksum program (sha256sum or shasum), DeskRanger then compares a resumed file with the original.
  • Nothing on your device is overwritten: if the name exists, the new file gets a number. If the name exists on the server, DeskRanger asks. Replace overwrites there, because a server has no trash.
  • Delete deletes on the server for good, a folder with everything in it. DeskRanger asks first.
  • If the server needs a password, transfers wait until you open it under Files and sign in. In the list, Sign In takes you there.
  • Edit opens a server's file with its app (on Linux, with the program your system names for that file type). Every save goes back to the server. If someone else changed it there meanwhile, you decide: Overwrite or Keep Both. Under Transfers it is listed at Being edited; Done sends a last change and removes the copy from your device. If you quit DeskRanger while files are still being edited, it asks first; copies left over go to the trash at the next start.
  • Downloaded files are marked like downloads from a browser: macOS checks a program before it first runs, Windows shows documents in Protected View.

macOS

The Files page with “Servers (SFTP)” in the sidebar and the NAS’s home folder in the listThe Files page with “Servers (SFTP)” in the sidebar and the NAS’s home folder in the list
Transfers with “Being edited”: a saved file of the NAS and one that was changed there meanwhileTransfers with “Being edited”: a saved file of the NAS and one that was changed there meanwhile

iPhone & iPad

This function is coming soon to iPhone & iPad.

“… does not offer SFTP. The server needs OpenSSH’s SFTP subsystem turned on.”

The server lacks the SFTP subsystem. For OpenSSH, sshd_config has a line “Subsystem sftp …” for it.

Keys from other apps and agent forwarding

With Use SSH agent under Advanced, DeskRanger signs in with keys from another app. You choose which app in the Keys area under Keys from other apps. The keys stay in that app.

macOS

On the Mac these are macOS's SSH agent (OpenSSH), 1Password and Secretive.

Windows

On Windows these are Windows' OpenSSH agent – which 1Password for Windows also provides – and Pageant.

iPhone & iPad

This function is coming soon to iPhone & iPad.

Android

Android has no keys from other apps. Agent forwarding with this device's keys works all the same.

The agent forwarding question: a program on the server wants to sign with the Mac's key, with “Decline” and “Use”The agent forwarding question: a program on the server wants to sign with the Mac's key, with “Decline” and “Use”

With Agent forwarding, programs on the server may sign with your keys, for example when you sign in to another server from there with ssh or work with git. Your keys never leave your device. Every single signature asks first: Use allows exactly that one, Decline declines it. If you do not answer in time, it is declined.

macOS

The agent forwarding question: a program on the server wants to sign with the Mac's key, with “Decline” and “Use”The agent forwarding question: a program on the server wants to sign with the Mac's key, with “Decline” and “Use”

iPhone & iPad

On the iPhone and iPad there are no keys from other apps. Agent forwarding with this device's keys works here too.

iPhone & iPad

The agent forwarding question: a program on the server wants to sign with the Mac's key, with “Decline” and “Use”The agent forwarding question: a program on the server wants to sign with the Mac's key, with “Decline” and “Use”

Organise and find

Your SSH hosts are in the same groups as your devices. A group such as “Office” can hold the office's PCs and its servers, and it appears on all your devices. Drag hosts onto a group in the sidebar or onto a group's heading, or choose Add to Group in a host's menu. The star puts a host into Favorites. Recently Connected is remembered on this device only.

  • Tags are free keywords such as prod or backup. You add them in a host's information, or for several hosts with Tags…. A click on a tag in the Tags strip shows only the hosts with that tag.
  • Search finds hosts by name, address, user, tag, group, system and the device they are reached through.
  • Filter narrows by group, tag, Access via and system. Active filters sit above the list as small cards; a click removes them.
  • Many hosts are best shown as a list. Select several to open them together with Open in Tabs, put them in a group, tag them or remove them.

macOS

Your SSH hosts are also in Favorites, Recently Connected and your groups. There the SSH · … chip shows only them. Remote desktops are under Devices with the Remote Desktop · … chip.

macOS

⌘I opens a host's information: the way to the server, the connection, the sign-in and its host key. DeskRanger fills in the server's system at the first connection when the server names it; you can change it there.

An SSH host's information: the way through the jump host, connection, system, sign-in, host key, groups and tagsAn SSH host's information: the way through the jump host, connection, system, sign-in, host key, groups and tags

Windows

Your SSH hosts are also in Favorites, Recently Connected and your groups. There the SSH · … chip shows only them. Remote desktops are under Devices with the Remote Desktop · … chip.

Windows

Ctrl+I opens a host's information: the way to the server, the connection, the sign-in and its host key. DeskRanger fills in the server's system at the first connection when the server names it; you can change it there.

iPhone & iPad

Your SSH hosts and remote desktops are also in “All Devices”. The Remote servers · … filter shows only them.

Android

Touch and hold a host to select it, then tap more. At the bottom, Open in Tabs, Tags…, Access via… and Remove… appear. You change a single host's tags in its menu. You enter a host's system when you edit it.

Linux

Click an entry to pick it; hold Ctrl or Shift to add more, Ctrl+A picks all, Esc lets go. A double click or Enter opens the terminal, a right click opens the menu. With several entries picked, a bar appears at the bottom with Open in Tabs, Group…, Tags…, Access via…, the star and Remove…. You drag entries onto a group's heading in the grid or onto a group in the sidebar, also from the list; a picked entry takes the whole pick with it. Open the information with Ctrl+I or with Get Info in the entry's menu: it appears as a column at the right edge, over the list when there is little room. There you see the way to the server, the connection, the sign-in, its host key and the saved forwards, and you change the system, groups and tags. DeskRanger remembers whether you chose the grid or the list.

Local shell

Local Shell on the Terminal page opens a shell of this device in a new tab – in the same terminal as your SSH connections, without any network. It runs as your user account, never with administrator rights. Closing the tab ends the shell.

macOS

On the Mac it is your login shell, usually zsh. The edition from the Mac App Store has no local shell: apps from there may not start a shell.

Windows

On Windows it is PowerShell.

iPhone & iPad

This function is coming soon to iPhone & iPad.

Android

Android has no local shell: apps may not start programs of their own there.

Quick connect

macOS

⌘K opens Quick connect from anywhere in the main window. Type a few letters of a host or device and press Return. In the terminal window, ⌘T opens the same search for the next tab.

Quick connect with ⌘K: “anna@stu” finds an SSH host, a new connection and an own deviceQuick connect with ⌘K: “anna@stu” finds an SSH host, a new connection and an own device

Windows

Ctrl+K opens Quick connect in the device library. Type a few letters of a host and press Enter. In the terminal window, Ctrl+Shift+T and “+” open the same search for the next tab.

iPhone & iPad

Tap the bolt on the Terminal page, or press ⌘K with a keyboard on the iPad. You can also type user@host straight into the list's search field. In the terminal, New terminal… in the menu of open terminals opens the same search.

Quick connect with ⌘K: “anna@stu” finds an SSH host, a new connection and an own deviceQuick connect with ⌘K: “anna@stu” finds an SSH host, a new connection and an own device

Android

The field at the top of the Terminal page searches, ranks the matches and connects: type a few letters, then tap the match. If you type user@host, DeskRanger connects once; below it you can save the server as an SSH host.

Quick connect with ⌘K: “anna@stu” finds an SSH host, a new connection and an own deviceQuick connect with ⌘K: “anna@stu” finds an SSH host, a new connection and an own device
  • Type a user in front, for example anna@nas, and DeskRanger signs in to that host as anna.
  • For a server you need only once, type user@host or user@host:port. The connection is not saved unless you explicitly save it as an SSH host.

Keys

A key is safer and more convenient than a password. Your keys are on the Terminal page in the Keys section. Create Key creates a new key on this device. Its private part stays on this device and is never synced.

macOS

On the Mac, the private key lives in the keychain.

Windows

On Windows, the private key is protected by your Windows account and stored on this PC only.

iPhone & iPad

This function is coming soon to iPhone & iPad.

Android

On Android the private key is sealed with the Android Keystore and stored on this device only. Choose key files with Import…; Export… saves an encrypted file wherever you like.

  • Copy Public Key puts the line for the server's authorized_keys file on the clipboard.
  • If you are already connected to a server, Set Up Key on Server in the window's menu does it for you.
  • You take over existing keys (OpenSSH, PEM, PuTTY) with Import…. Export is encrypted only, with a passphrase.

Keys in the security chip

macOS

If your Mac has a Secure Enclave, Create Key creates the key there. Its private part is made in the chip and never leaves it. It can't be exported or copied to another Mac. With Confirm every use, the Mac asks for Touch ID or your Mac password before every sign-in. Without that confirmation, the chip does not sign.

Create a key: in the Secure Enclave, confirmed on every useCreate a key: in the Secure Enclave, confirmed on every use

Windows

If your PC has a TPM, Create Key creates the key there. Its private part is made in the TPM and never leaves it. It can't be exported or copied to another PC. With Confirm every use, Windows Hello asks before every sign-in.

iPhone & iPad

On the iPhone and iPad, the private key lives in this device's keychain. You can also share the public part, for example by mail.

Android

From Android 11, Create Key can create the key in the Android Keystore – in StrongBox if your phone has its own security chip. The private part never leaves it and can't be exported. With Confirm every use, Android asks for your fingerprint, face or screen lock before every sign-in.

  • Such a key is an ECDSA key (P-256). Practically every server knows it.
  • DeskRanger first asks the server whether it knows the key. Only then does the prompt appear.
  • If the chip is reset or you change devices, the key is gone. Then create a new one and set it up on your servers.

The first connection

The first time, DeskRanger shows the server's fingerprint. Compare it with what the server itself shows, then choose Trust and Connect. After that, DeskRanger does not ask again. The servers this device trusts are listed under Known hosts in the Keys section.

The question on the first connection: the server's address, key type and fingerprintThe question on the first connection: the server's address, key type and fingerprint

If the server later presents another key, DeskRanger does not connect. It then sends neither a password nor a key.

The server identifies differently than before: not connected, both fingerprintsThe server identifies differently than before: not connected, both fingerprints

iPhone & iPad

The iPhone and iPad create the key in the Secure Enclave. It never leaves the chip. With Confirm every use, the device asks for Face ID, Touch ID or the device passcode before every sign-in.

Create a key: in the Secure Enclave, confirmed on every useCreate a key: in the Secure Enclave, confirmed on every use
  • Such a key is an ECDSA key (P-256). Practically every server knows it.
  • DeskRanger first asks the server whether it knows the key. Only then does the prompt appear.
  • If the chip is reset or you change devices, the key is gone. Then create a new one and set it up on your servers.

Import from OpenSSH

If you already trusted your servers in OpenSSH, you do not have to confirm the fingerprints again. In the Keys section under Known hosts, choose Import from known_hosts…, then Read ~/.ssh/known_hosts or Choose File…. DeskRanger shows which of your SSH hosts the file names, with key type and fingerprint. Hosts with one clear key are preselected. Check the selection, then import it.

Host keys from known_hosts: two hosts to import, one named only by a pattern, one with another remembered keyHost keys from known_hosts: two hosts to import, one named only by a pattern, one with another remembered key

iPhone & iPad

This function is coming soon to iPhone & iPad.

Android

On Android you pick the file with Import from known_hosts…, for example a copy of your known_hosts from the Files app.

  • Only a host that has no key on this device yet is imported. A key that is already remembered is never replaced, even if the file names another one.
  • If the file names several keys of the same type for a host, or the key is marked @revoked, DeskRanger imports nothing for it.
  • Hosts the file names only through a pattern with * or ?, hosts reached through a gateway, and hosts whose key you forgot here on purpose are marked and not preselected. Compare their fingerprint before you select them.
  • Exactly the key DeskRanger showed you is imported. If the file changed in the meantime, nothing is imported for that host.
  • From the first connection on, imported hosts get the hard stop when the key changes. DeskRanger asks the server for the key type from the file first, as OpenSSH does.
  • @cert-authority lines are not imported. You trust certificate authorities per group, see below.
  • The file stays unchanged. The keys apply to this device only.

Host certificates of a group

If your team uses an SSH certificate authority that signs its servers' host keys, you can trust it for a group. Servers in that group that present a matching host certificate then connect without the fingerprint question.

macOS

In the More actions menu next to the group's name, choose Host CAs…. Paste the authority's public key or choose From File…, then Add.

Host certificate authorities of the group “Office”: one authority for *.office.exampleHost certificate authorities of the group “Office”: one authority for *.office.example

Windows

In the More actions menu to the right of the group's name, choose Host CAs…. Paste the authority's public key or choose From File…, then Add.

iPhone & iPad

This function is coming soon to iPhone & iPad.

Android

On the Terminal page, tap the menu next to the group's name and choose Host CAs…. Paste the authority's public key and choose Add.

  • The certificate must name the server as you connect to it and be valid right now.
  • A line such as @cert-authority *.example.com ssh-ed25519 AAAA… from a known_hosts file limits the authority to matching names.
  • The trust applies to this device only. Servers without a matching certificate work as described above: a question the first time, a hard stop when the key changes.
  • If this device already knows a server with another key, the hard stop stays. If you know why, choose Forget Host Key once; from then on the certificate counts.
  • Stop Trusting takes the trust back.

Colors, font and profiles

A profile decides what a terminal looks like: the color scheme, the font and its size, ligatures, the cursor and how many lines of history it keeps. Profiles apply only on the device where you create them.

macOS

You find them in Settings (⌘,) › Terminal under Profiles. There you add a profile with New Profile, copy one with Duplicate, remove it with Delete and choose the profile for new terminals with Set as Default. Below the list, in the editor, you set everything; the preview underneath is the real terminal. Every change applies at once to the terminals that are open.

Settings › Terminal › Profiles: the list with the default profile and an imported color scheme, below it the editor with color scheme, font, ligatures, cursor and previewSettings › Terminal › Profiles: the list with the default profile and an imported color scheme, below it the editor with color scheme, font, ligatures, cursor and preview

Windows

You find them in Settings › Terminal under Profiles. There you add a profile with New Profile, copy one with Duplicate, remove it with Delete and choose the profile for new terminals with Set as Default. Below the list, in the editor, you set everything; the preview is the real terminal. Every change applies at once to the terminals that are open.

iPhone & iPad

This function is coming soon to iPhone & iPad.

  • The profile DeskRanger is always there and stays as it is: light or dark like your system, with the system font. To change it, choose Duplicate.
  • As Color scheme you can pick one of a few ready-made schemes, among them Solarized Dark, Dracula, Nord and High Contrast.
  • Import Color Scheme … reads a color scheme from an iTerm2 (.itermcolors), Windows Terminal (.json) or base16 (.yaml) file and creates a profile for it. If the file is too large, damaged or incomplete, DeskRanger says what is wrong and changes nothing.
  • As Font you get the fixed-width fonts your device brings. DeskRanger ships no font of its own. If the chosen font is missing on this device, DeskRanger uses the system font.
  • Ligatures joins characters such as -> or != into one symbol if the font supports it (for example Fira Code or JetBrains Mono).

Which profile a host uses, you choose under Profile in its form and in its information; the same goes for the terminal of one of your devices. Default uses the default profile.

iPhone & iPad

On iPhone and iPad you find the profiles under Account › Terminal. Tap a profile to edit it; swipe a row to delete it or to make it the default. Two fingers in the terminal change the font size for you; once you set the size in a profile, the profile's size counts again. The host's profile is chosen in the SSH host form under Profile.

Android

On Android you find the profiles under Settings › Terminal. Import Color Scheme … opens the system's file picker. The phone draws its system font, so there is no font choice and no ligatures. Two fingers in the terminal change the font size for you; once you set the size in a profile, the profile's size counts again. The host's profile is chosen in the SSH host form under Profile.

Snippets

Commands you need often can be saved as a snippet. A snippet is inserted into the terminal but not run: you see the command at the prompt and send it yourself. If you turn on Run for a snippet, it runs at once. Snippets apply only on the device where you create them.

macOS

You create them in Settings (⌘,) › Terminal under Snippets: New snippet, Edit and Delete. In a terminal window, insert one with Insert snippet in the toolbar.

Windows

You create them in Settings › Terminal under Snippets: New snippet, Edit and Delete. In the terminal window, insert one with Insert snippet at the top right.

iPhone & iPad

You create them under More › Settings › Terminal › Snippets: New snippet, tap a snippet to change it, swipe left to Delete. In a terminal, insert one with Insert snippet in the More menu.

Web

You create them on the Terminal page under Snippets: New snippet, Edit and Delete. In a terminal pane, insert one from the ⋯ menu with Insert snippet …. The snippets stay in this browser.

Android

You create them in Settings › Terminal under Snippets: New snippet, Edit and Delete. In a terminal, open the menu (⋮) and choose Insert snippet.

Linux

You create them in the Terminal area under Snippets: New snippet, Edit and Delete. In the terminal window, insert one with Insert snippet at the top right.

A snippet can hold placeholders that are filled when you insert it:

  • {{host}} and {{user}} become the server and the user name of the connection. If the terminal does not know them, for example in a local shell, DeskRanger asks for them.
  • {{ask:Name}} asks for a value before inserting, for example journalctl -fu {{ask:Service}}. If the same name appears more than once, DeskRanger asks only once.

Filled-in values stay on one line, so a value cannot add another command. If a snippet has several lines, DeskRanger asks before sending them, just as when you paste from the clipboard.

Sending input to several sessions

If you want to type the same command into several terminals, for example on a row of servers, you can send your input to several sessions at once. It is off until you switch it on, and it is never saved: it ends when you close the app and is never restored.

macOS

In the terminal window, open Send input to several in the toolbar and choose Send input to several again in the menu. The current tab is the first target. With the menu open you can tick the other tabs that should get your input.

Windows

In the terminal window, open Send input to several at the top right and choose Send input to several again in the menu. The current tab is the first target. With the menu open you can tick the other tabs that should get your input; the button is red while the mode is on.

iPhone & iPad

In a terminal, open the More menu and choose Send input to several. The current tab is the first target. Once it is on, the same entry opens a list where you tick the other tabs that should get your input. Switch between tabs with the tab button at the top; the red bar tells you in every ticked tab that the mode is on.

Web

On the Terminal page, open the More menu of a pane and choose Send input to several. That pane is the first target. Once it is on, the same entry in the other panes' menus has a tick that you set for each pane that should get your input; a pane can also sit in another tab, you tick it there. The mode ends when you leave the Terminal page or reload it, and is never saved. The panes of one tab are the sessions; the red bar sits above each ticked pane.

Android

In a terminal, open the menu (⋮) and choose Send input to several. The current tab is the first target; in the list that opens you tick the other tabs that should get your input. The red bar at the top shows the number of sessions and Stop.

Linux

In the terminal window, open Send input to several at the top right and choose Send input to several again in the menu. The current tab is the first target. With the menu open you can tick the other tabs that should get your input; the button is red while the mode is on.

Every tab that gets your input shows a red bar at the top with the number of sessions, and the button Stop. One click on it ends the mode in all tabs. What you type goes to every ticked tab; each tab handles the keys itself, as if you had typed there. Typing into a tab that is not ticked stays in that tab.

Every paste asks first, and so does every snippet you insert, because it goes to all ticked tabs. The question says how many sessions get it.

Working in the terminal

macOS

Each host opens in its own window. Several windows become tabs; ⌘T opens the next one. Links show their target when you move the pointer over them and open with ⌘-click.

A terminal window with an SSH session on the NASA terminal window with an SSH session on the NAS

Windows

All hosts open as tabs in one terminal window. Ctrl+Shift+T or “+” opens the next one, Ctrl+Tab switches. Ctrl+T and the other Ctrl keys go to the program on the server. Copy with Ctrl+Shift+C – or with Ctrl+C while text is selected – and paste with Ctrl+V. Links show their target when you move the pointer over them and open with Ctrl-click. Narrator reads the terminal's screen and announces new output.

iPhone & iPad

A terminal covers the app. Above the keyboard is a key row with Esc, Ctrl, Alt, Tab and the arrows; on a narrow iPhone, |, ~, /, - and F1–F12 are under “…”. Ctrl and Alt apply to the next key; tapped twice they stay on. Touch and hold an arrow to send Home, End, Page Up or Page Down. Swipe along the row to move the cursor.

  • Scroll through the history with one or two fingers; pinch to change the text size.
  • Touch and hold the text to select a word; drag to select more. Then choose Copy, Paste or Select All.
  • With a keyboard on the iPad, arrows, Esc, Tab, function keys and Ctrl combinations go to the program; ⌘C, ⌘V and ⌘+ stay with the iPad.
  • Several terminals stay open at once. Switch between them at the top; the list shows them under Open terminals.
  • VoiceOver reads the terminal's screen and announces new output.
A terminal window with an SSH session on the NASA terminal window with an SSH session on the NAS

Android

Switch between terminals with the bar at the top; “+” opens the page for the next one. Above the keyboard there is a key row: Esc, Ctrl and Alt (tap once for the next key, twice to keep it), Tab, the arrows (touch and hold: Home, End, Page Up, Page Down) and | ~ / -. Pinch with two fingers to change the text size, drag with one to scroll. Touch and hold to select a word; then Copy and Paste appear. With a hardware keyboard, Ctrl and Alt go to the program; copy and paste with Ctrl+Shift+C and Ctrl+Shift+V. Light and dark follow the system. TalkBack reads the terminal's screen and announces new output.

While a terminal is open, Android shows the notification “Terminal connected”: this keeps the connection when you briefly switch to another app. It disappears when you close the last terminal.

A terminal window with an SSH session on the NASA terminal window with an SSH session on the NAS

If you paste several lines at once, DeskRanger asks first: otherwise every line would run as a command right away. Hidden control characters are removed when pasting.

Programs on the server may put text on your clipboard only when Share Clipboard is on for the host. They can never read your clipboard.

Save Output… saves what the terminal shows as a text file.

“The server does not answer.”

Is the server on and reachable from this device? If it is in another network, choose a device that runs there under Access via.

“Sign-in refused.”

Check the user name. If you sign in with a key, its public part must be in the authorized_keys file on the server.

Was this helpful?

Checked for version 0.1.0 · as of 2026-11-14