SECURE PIPES 2.0.14 User guide

Console and SFTP

Open an SSH console or transfer files using a saved host without creating a forwarding profile first.

Open a remote console

In Connections → Host Presets, right-click the desired host and choose Open Console. Open Console (Window) uses a separate window instead of the right-hand console area.

Check the selected host, username and fingerprint before entering credentials. A host preset is not proof that authentication has succeeded. If the app is configured to require interface authentication for Console/SFTP, unlock it first.

Selecting a private key makes the console use that configured key. Without configured credentials, the console can prompt interactively. Server-requested passphrases and other authentication challenges may still require input.

To use a local shell instead, choose Open Local Console from the connection toolbar. Local commands run on your Mac, not on the SSH server. Be sure which console is active before running any command.

Open SFTP

Right-click a host and choose Open SFTP. Connect with the account allowed to access the desired remote files. SFTP is file transfer over SSH; it is not FTP and does not require exposing an additional forwarding port.

Navigate to the desired location before transferring files. Check the destination and remote permissions. Treat replace/delete operations as changes to the actual server, not to a disposable preview.

Upload and download files

The file browser has a local pane for your Mac, a remote pane for the SSH server, and a Transfers queue. Open the destination folder before adding a transfer.

  1. To upload, select files in the local pane, navigate to the intended remote folder, and click Upload.
  2. To download, choose the destination in the local pane, select files in the remote pane, and click Download.
  3. Follow the task in Transfers. Queuing a task does not mean that it has completed. Check its final state and refresh the destination listing when investigating a missing file.

For uploads, an existing destination produces a Skip / Cancel prompt. Skip leaves that destination unchanged; Cancel stops adding further uploads from that batch. Do not expect an overwrite command in this prompt. Use a different name or resolve the existing destination deliberately before uploading again. Use a separate local folder for downloads when you need to preserve existing files.

Cancel acts on selected transfers, Remove Pending removes pending tasks, and Clear Completed clears finished entries from the queue. Clearing a queue entry is not a command to delete its destination file.

Manage files and permissions

Right-click a file or folder for the actions available on that side:

Location Actions
Local pane Upload, New Folder, Rename, Move to Trash, Properties, Reveal in Finder, Copy Path and Refresh
Remote pane Download, New Folder, Rename, Delete, Permissions, Properties, Copy Path and Refresh

Some commands require a single selected item. Double-click a folder to navigate into it. Use Copy Path when you need the full path rather than only the displayed filename.

Remote Delete changes the server and should not be treated as Finder's recoverable Trash. Check the path and confirmation before proceeding. Permissions accepts an octal mode, such as 600 for an owner-readable/writable file or 700 for an owner-only directory. Apply permissions appropriate to the file's purpose; changing them can prevent the service or account from using it.

App lock is separate

The master password, Touch ID and app OTP protect access to the interface. They do not replace remote SSH authentication. Locking the interface does not itself disconnect active tunnels.

If a console or SFTP connection fails, first test the saved host's server address, SSH port, account and identity. A working forwarding profile can still differ from a console in its selected credentials or server policy.

Verification scope

The host action entries and app-lock controls were inspected for this guide. The transfer, queue and file-management instructions were checked against the implementation. Remote shell commands and file upload/download require your own authorized test server; these examples do not demonstrate an actual remote transfer.

Based on Secure Pipes 2.0.14 · Updated October 18, 2026