SSH, SCP, SFTP GUI or CLI -- Working with Files or Folders on Tux or Remote Hosts
Introduction
You have a number of ways, using an application or program GUI (graphical user interface) or a terminal or console CLI (command line interface), to connect to, read, list, edit, copy, or transfer files and folders to and from Tux or other remote server or computer hosts.
Copy from a Professor's (or someone else's) Directory?
You need to get from the professor, or other person, or the assignment in Blackboard Learn the name of the remote host/server and the folder file path or directory file path. Our examples assume Tux, and often involve you copying to/from a remote computer to your computer using Tux and SSH or SCP or SFTP. If we do not have this information, we cannot help you, and there are limits to how much help we can provide with homework. We are NOT CA's or TA's or your Instructor.
READ ASSIGNMENT INSTRUCTIONS CAREFULLY!
GUIs for Secure File Copy/Transfer
GUI = Graphical User Interace. The one you click a lot in, and don't just type in.
- Cyberduck
- FileZilla
- WinSCP and see... Text editor config for WinSCP
- VS Code for Mac, Windows, and Linux
Tux Help
CLI Terminal Commands for SCP or SFTP or rsync -- Secure File Copy/Transfer
CLI = Command Line Interface: The one that you type into, and looks old school.
- SCP by Mac Terminal CLI or Command Line Interface
- SCP by Windows 10 PowerShell CLI Command Line Interface
- rsync
- SSH, SCP, SFTP GUI or CLI -- Working with Files or Folders on Tux or Remote Hosts
NOTE FOR WINDOWS USERS
Especially if you are asked to use PuTTY:
- This applies whether you are using SCP, SSH, SFTP, Cmd.exe, Command Prompt, PowerShell, Windows Terminal, or otherwise typing old school commands into a command prompt window...
- "The latest builds of Windows 10 and Windows 11 include a built-in SSH server and client...By default, the OpenSSH client will be located in the directory: C:\Windows\System32\OpenSSH. You can also check that it is installed in Windows Settings > Apps > Optional features, then search for "OpenSSH" in your installed features."
- Search in your Windows pre-installed apps for Windows Terminal or Cmd.exe or Powershell, and just try to SSH from there as you would in PuTTY or similar. If it connects, you don't need PuTTY.
- Windows Terminal is pretty slick, though. Search in your Windows pre-installed apps. See Tutorial: SSH in Windows Terminal . Also, if no Windows Terminal installed, we recommend seeing Install and get started setting up Windows Terminal.
What about PuTTY?
PuTTY is an old SSH client for Windows. It was a staple for decades, but see previous section. You don't need it.
A lot of people do like the interface, and its ability to save multiple hosts/servers to connect to, along with profiles for each (colors and other settings).
But if you're not ssh'ing much, or you already SSH using an IDE or TextEditor (vscode, for example) or a GUI for SCP/SFTP, it can quickly become superfluous.
That said, PuTTY is still very usable, if you prefer that. And it may fit what you see in your instructor's or other assignments' or lab instructions' screenshots.
- PuTTY -- OLD SSH Client for Windows
- And on the off-chance someone tells you to use Putty SCP, though should really ask if you really have to (like as the instructor), but if you still have to... Putty SCP or PSCP. But Putty SCP or PSCP is generally not needed.