30
How can i rsync over my network without using ssh?
(discuss.tchncs.de)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 04 Feb 2024
30 points (91.7% liked)
Linux
48210 readers
930 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
I love this answer because it's exactly what he's asking, but absolutely what he shouldn't do hahahaha.
Anyone wondering, go to a computer and type
nc -lp PORT > file(Replacing PORT with the port you want to use), now go to a different computer and typenc IP PORT < FILE(Replacing IP and Port with the IP from the first machine and the PORT you ran on the command there, and FILE with a file you want to copy). Congratulations, you just copied a file from one machine to another without using SSH.You can pipe tar through it too.
Receiver:
nc -lp 12345 | tar xf -Sender:
tar cf - . | nc 192.168.0.123 12345Also
ddif you're moricated to image over the network.I mean, he asked....
What're the downsides? I'm sure it's very insecure. Is it faster?
Sends in the clear, no error checking, the
nccommand is promiscuous while its bound to the port. No crypto or compression to slow you down. Just a raw pipe of bytesIts a bad idea, part of the forbidden codex known only to old, irreverent graybeards who know better but don't care anymore. There are better ways that are both more reliable and better practice.
You might want to look into using passwordless SSH keys within your script (see
ssh -i) which isn't the most secure.practice on multiuser systems, but is Okayish in Devops and backups. Add other factors like aggressive allowed hosts settings on the receiver, and rotate the keys regularly.