Re:Termbin: Easiest way to copy over SSH
by yorwba on Tuesday January 31, 2017 @05:42AM
(#13529404)
I have no idea where the claim "Easiest way to copy over SSH" is coming from. The site itself is titled "termbin.com - terminal pastebin", which is a much better description, since there is no SSH involved.
Re:Termbin: Easiest way to copy over SSH
by dogma1138 on Tuesday January 31, 2017 @05:55AM
(#13529483)
I think people confuse terminal with ssh, or even netcat with SSH.
Netcat doesn't use SSH, it uses raw TCP pretty much.
There are versions of Netcat which can use SSL/TLS it should still work with this if you download those builds.
That said I can't recommend using a service that uploads your data to some random site, and worse basically tells you to just "download" some data that will be input into your terminal from some random site.
This whole thing looks like a social experiment of how many secrets can I get from people who should know better...
Re:Termbin: Easiest way to copy over SSH
by shubhamjain on Tuesday January 31, 2017 @06:45AM
(#13529730)
Copying a long piece of text from a SSH session is how I found the service. I felt that this particular use-case could more beneficial compared to a terminal pastebin. I agree that SCP is more useful towards copying files but when you just want to copy the output of some command, it makes sense to use this service (provided that the output isn't sensitive information).
Re:Termbin: Easiest way to copy over SSH
by dvfjsdhgfv on Tuesday January 31, 2017 @09:08AM
(#13530610)
If you use Windows, you can do yourself a favor and install Kitty - it integrates nicely with WinSCP, and basically you just need to press Sift+F3 to copy any file you need, whether text or binary, using a familiar interface.
Re:Termbin: Easiest way to copy over SSH
by jonathonf on Tuesday January 31, 2017 @05:48AM
(#13529440)
What's the best way of scp'ing from a remote server connection to local machine, if the local machine isn't externally accessible (e.g. isn't running SSH)?
e.g.
local$ ssh remote
remote$ # do some stuff
remote$ echo "Text" > file.txt
remote$ # oh, I need to copy file.txt back to my local host
remote$ #?
Re:Termbin: Easiest way to copy over SSH
by lutusp on Tuesday January 31, 2017 @11:51AM
(#13532350)
> What's the best way of scp'ing from a remote server connection to local machine, if the local machine isn't externally accessible (e.g. isn't running SSH)?
If by "not externally accessible" you mean the local machine is not running an SSH server, but has an SSH client available and the machine is connected to the network, and the remote machine is running an SSH server, then:
Re:Termbin: Easiest way to copy over SSH
by throwaway2016a on Tuesday January 31, 2017 @09:24AM
(#13530732)
If you can't do what another poster suggested and do the transfer the other way around... uploading the file to AWS S3 from the CLI works pretty well. Though unlike the solution in this post does require installing heavier software.
Also, alternatively... pipe it to `mail` and send it over email.
Re:Termbin: Easiest way to copy over SSH
by schmich on Tuesday January 31, 2017 @05:50AM
(#13529453)
If you want encryption when sharing via termbin, I put together a gist [1] some time ago that helped me. Obvious caveat applies: don't do this if you're really concerned about the privacy of your data.
If you want to copy something over ssh, try scp.
Netcat doesn't use SSH, it uses raw TCP pretty much.
There are versions of Netcat which can use SSL/TLS it should still work with this if you download those builds.
That said I can't recommend using a service that uploads your data to some random site, and worse basically tells you to just "download" some data that will be input into your terminal from some random site. This whole thing looks like a social experiment of how many secrets can I get from people who should know better...
The easiest way to copy over SSH is using `scp`.
$ scp (source path) (destination URI):(destination path)
For a stream between systems instead of a file, do it this way:
$ cat localfile | ssh user@host "cat > remotefile"
-- or --
$ ssh user@host "cat > remotefile" < localfile
e.g.
If by "not externally accessible" you mean the local machine is not running an SSH server, but has an SSH client available and the machine is connected to the network, and the remote machine is running an SSH server, then:
$ scp remoteuser@remotehost:remotepath/remotefile localfile
Also, alternatively... pipe it to `mail` and send it over email.
[1] https://gist.github.com/schmich/f2ef5c85030863d630a97ec91c1b...
Seems to capture stderr: