Accessing Remote Files Easily and Securely
The secure shell, ssh, and its companion, scp, are tools that I use more or less on a daily basis. Being able to move files between machines without having to setup SAMBA or NFS is very handy when working with multiple systems. All that you need is to enable the secure shell daemon - sshd.
Before we go into the details of the sshfs, let's run through a quick re-cap of ssh. The secure shell daemon runs on port 22 by default. It makes it possible to run an encrypted shell session. With the -Y flag, you can even run X11-forwarding, allowing you to run X11, i.e. graphical, programs on the remote machine and displaying the windows on the terminal that you are sitting at.
You can configure sshd through the /etc/ssh/sshd_config file (that is the location on my Kubuntu machine). Here, you can disable root access, older protocols, X11 forwarding, etc. The notion is that the more limits you put on the remote access, the more secure your system is from potential attacks. You might also want to tune your hosts.allow and hosts.deny files if you plan to expose sshd to the Internet. There are many guides on hardening servers and ssh, so I will not go into details.
To get things up and running, what you need to do is to install sshd. In Ubuntu, that means the openssh-server package. For external access, you also need to enable port forwarding of port 22 in your router/firewall and find your external IP. Now, you should be able to log onto your machine using your normal user credentials.
$ ssh email@example.com firstname.lastname@example.org's password:
Having entered the password, you should now have full access to the remote system.
The handy scp command, secure copy, works in much the same way. To copy the file test.txt to user's remote home directory, simply enter:
$ scp test.txt email@example.com:
As before, you will be prompted for a password. You can copy the other way around as well. The command below demonstrates how to copy a file with an absolute path, i.e. not in the home directory of user, to your local machine.
$ scp firstname.lastname@example.org:/var/log/messages remote-messages
These two commands means that you can browse the file system, and freely copy files between machines. What sshfs does is that it exposes this functionality as a file system that you can mount. Before we look into how, let's have a quick look at sshfs.
The sshfs is implemented using FUSE, and relies on the sftp part of ssh to access the remote computer. As a remote file access protocol, sshfs is not very good. For instance, multiple users writing to the same file at once can create havoc. The benefits are the inherit security and that it is easy to setup.
So, how to use it. Let's look at a very short demonstration.
$ sshfs email@example.com: remote-home $ ls remote-home Desktop Documents Downloads Music $ fusermount -u remote-home
The initial sshfs command mounts the user's home directory to remote-home. You can specify another path after the colon to mount any other part of the remote file system. Access is only restricted by user's access rights.
Using ls, or any other ordinary command, will work as if the remote home directory was mounted locally. All tools work. For instance, you can log onto your remote machine and build software using your locally installed setup of build tools.
To unmount the filesystem, the fusermount command from the FUSE utilities package is used.
To summarize, sshfs an easy setup remote file access tool. It needs to be used with care if multiple users are involved. It makes it dead easy to temporarily access remote file systems, as well as mounting file systems from virtual machines for easier access and monitoring, as well as for remote installation, compilation and debugging. All-in-all, one of the tools I always keep handy in my toolbox.
Johan Thelin is a consultant working with Qt, embedded and free
software. On-line, he is known as e8johan.
Getting Started with DevOps - Including New Data on IT Performance from Puppet Labs 2015 State of DevOps Report
August 27, 2015
12:00 PM CDT
DevOps represents a profound change from the way most IT departments have traditionally worked: from siloed teams and high-anxiety releases to everyone collaborating on uneventful and more frequent releases of higher-quality code. It doesn't matter how large or small an organization is, or even whether it's historically slow moving or risk averse — there are ways to adopt DevOps sanely, and get measurable results in just weeks.
Free to Linux Journal readers.Register Now!
- Django Models and Migrations
- Hacking a Safe with Bash
- Secure Server Deployments in Hostile Territory, Part II
- Home Automation with Raspberry Pi
- The Controversy Behind Canonical's Intellectual Property Policy
- Huge Package Overhaul for Debian and Ubuntu
- KDE Reveals Plasma Mobile
- Shashlik - a Tasty New Android Simulator
- Embed Linux in Monitoring and Control Systems
- Purism Librem 13 Review