Well, you should be using ssh, sftp, scp, rsync, sshfs, x2go, .... as the protocols between different Unix/Linux systems.
On all the systems, run this:
Code:
sudo apt install ssh fail2ban
After doing that, almost all Linux file managers will accept sftp://{insert-IP-address}/ in the URL to connect to a different system. Pretty easy and fast. Sorta ... just works. fail2ban prevents brute force attacks.
I use caja on my 20.04 desktop (that's the default Mate desktop file manager). Because I have a DNS server and my internal LAN uses static IPs for all systems (or DHCP reservations), I can use sftp://istar/ to connect to my other system named istar. I could use the IP address for it, but that's what DNS is for - so I don't have to know it.
Once you have ssh installed (that is a meta-package for both the ssh-client and the ssh-server), there are about 50 other tools that work for connecting Unix-to-Unix systems.
ssh is enough for
- secure remote access to files via sftp
- secure remote filesystem access via sshfs
- secure remote CLI/shell access to systems with plain ssh
- securely run applications on a different machine, but display the window locally
- secure remote desktops via x2go/freenx
- secure remote file replication with rsync (ssh is the default rsync protocol)
- secure port forwarding of selected ports
- secure remote editing with vim/gvim and other editors
- pseudo-VPN with sshuttle
http://diogomelo.net/blog/10/ssh-tricks for people completely new to ssh wonders.
http://blogs.perl.org/users/smylers/...vity-tips.html as you learn more.
ssh has been used since the mid-1990s. It is the only system-to-system connection tool that I know which is both more secure AND more convenient once keys have been setup for key-based authentication. This authentication is valid for any ssh-based connection. Imagine being asked for a password only once a day (or every 12 hours) to unlock the ssh-key, but then have full access to a different system. The system can be on your LAN or halfway around the world. ssh is how a single Unix/Linux admin can manage thousands of servers spread around the world. There are millions of these servers being managed by a relatively few people.
In the time you've spent already, you could have installed and been using key-based authentication between both your systems. When you know what you are doing, it is about 60 seconds of effort to install and configure ssh-keys. Plus, Windows supports ssh and sftp for about 2-3 yrs (Win10). Don't know why it took them so long.
I've provided steps to setup ssh-keys and transfer those keys in these forums a number of times.
https://ubuntuforums.org/showthread....6#post13916386
https://ubuntuforums.org/showthread....8#post13959278
Of course, there are thousands of different protocols. If you weren't using laptops, I'd suggest some others like NFS. But NFS needs a system that doesn't move. Isn't powered off and stays at the same location on the network. That isn't a typical laptop purpose. But NFS is the native way for Unix systems to share storage. 99.95% of the time, the NFS-client system doesn't know that the storage is actually from another system. All problems (cough .... almost all), work perfectly using NFS storage. NFS performance is excellent when the wired network connecting the clients and server are excellent.
"Talking" can mean by a number of other things like DLNA, XMPP, IRC, video streaming using webcams ... thousands of methods. But nobody can help if you aren't clear on what you hope to see "talk" between these systems.
5 Cups of Ubuntu
Originally Posted by josephfg
Posting Permissions
Adv Reply
Bookmarks