What is the easiest way to send a file or a text message from a server to a client if SSH is not an option?
What is the easiest way to send a file or a text message securely from a server to a client if SSH is not an option?
Hello,
I am working on a cloud server and I want to send a small file or text message securely (important) from the server to a client. Ideally I want to receive the file or message directly in the client Terminal. There is no X so everything has to be through command line.
SSH is not an option, too many Firewalls and stuff.
Syncthing is too complicated to use from command line (have to use the REST API, no flags or commands available).
Talk does not seem to work for this purpose.
E-mail is probably not secure enough.
Tmate cannot do this as far as I know and it's not persistent over sessions.
Vesa
Edit: Please note, there is no X so everything has to be through command line. Also the solution should be scriptable without need for manual intervention.
linux file-transfer messaging
asked Jan 23 at 0:04
VesaVesa
175211
add a comment |
What is the easiest way to send a file or a text message securely from a server to a client if SSH is not an option?
Hello,
I am working on a cloud server and I want to send a small file or text message securely (important) from the server to a client. Ideally I want to receive the file or message directly in the client Terminal. There is no X so everything has to be through command line.
SSH is not an option, too many Firewalls and stuff.
Syncthing is too complicated to use from command line (have to use the REST API, no flags or commands available).
Talk does not seem to work for this purpose.
E-mail is probably not secure enough.
Tmate cannot do this as far as I know and it's not persistent over sessions.
Vesa
Edit: Please note, there is no X so everything has to be through command line. Also the solution should be scriptable without need for manual intervention.
linux file-transfer messaging
asked Jan 23 at 0:04
VesaVesa
175211
3
What do you mean by "securely"? Do you just want to be sure that the message arrives? Or that it arrives unchanged? Or that no one else can read it? Can you share a separate secret (password) between the server & client?
– Xen2050
Jan 23 at 1:18
Well, granted, the message should arrive, otherwise there would not be any point in sending it. It should also be impossible to read for others and yes, unchanged as well. The server and client can be preconfigured to store passwords.
– Vesa
Jan 23 at 5:12
"Easiest" is very much a function of "what tools do you have available, and how is the whole system set up". "Too many firewalls" indicate complications we know nothing about.
– dirkt
Jan 23 at 6:02
@dirkt The server is running Ubuntu, very recent version and I can access most tools there are. So there are probably some good solutions for this issue. With regard to the firewalls I have tested SSH and ruled it out because I don't want to run an SSH server either on the sending computer or the receiving computer.
– Vesa
Jan 23 at 10:06
1
If the problem isn't that ssh can't get through the firewalls: You'll have to run some sort of "server" anyway, no matter if you "type" the server on your commandline using available tools, or if you just start it. Setting up an ssh-server is trivial, secure, and solves all the problems you'd need to solve manually. If you insist on doing it manually, first thing that comes to mind is socat/netcat (which will start a temporary "server") on both the receiving and teh sending computer. You'll have to encrypt and decrypt yourself.
– dirkt
Jan 23 at 11:49
add a comment |
What is the easiest way to send a file or a text message securely from a server to a client if SSH is not an option?
Hello,
I am working on a cloud server and I want to send a small file or text message securely (important) from the server to a client. Ideally I want to receive the file or message directly in the client Terminal. There is no X so everything has to be through command line.
SSH is not an option, too many Firewalls and stuff.
Syncthing is too complicated to use from command line (have to use the REST API, no flags or commands available).
Talk does not seem to work for this purpose.
E-mail is probably not secure enough.
Tmate cannot do this as far as I know and it's not persistent over sessions.
Vesa
Edit: Please note, there is no X so everything has to be through command line. Also the solution should be scriptable without need for manual intervention.
linux file-transfer messaging
asked Jan 23 at 0:04
VesaVesa
175211
What is the easiest way to send a file or a text message securely from a server to a client if SSH is not an option?
Hello,
I am working on a cloud server and I want to send a small file or text message securely (important) from the server to a client. Ideally I want to receive the file or message directly in the client Terminal. There is no X so everything has to be through command line.
SSH is not an option, too many Firewalls and stuff.
Syncthing is too complicated to use from command line (have to use the REST API, no flags or commands available).
Talk does not seem to work for this purpose.
E-mail is probably not secure enough.
Tmate cannot do this as far as I know and it's not persistent over sessions.
Vesa
Edit: Please note, there is no X so everything has to be through command line. Also the solution should be scriptable without need for manual intervention.
linux file-transfer messaging
linux file-transfer messaging
asked Jan 23 at 0:04
VesaVesa
175211
asked Jan 23 at 0:04
VesaVesa
175211
edited Jan 23 at 23:20
Vesa
asked Jan 23 at 0:04
VesaVesa
175211
asked Jan 23 at 0:04
VesaVesa
175211
asked Jan 23 at 0:04
VesaVesa
175211
175211
3
What do you mean by "securely"? Do you just want to be sure that the message arrives? Or that it arrives unchanged? Or that no one else can read it? Can you share a separate secret (password) between the server & client?
– Xen2050
Jan 23 at 1:18
Well, granted, the message should arrive, otherwise there would not be any point in sending it. It should also be impossible to read for others and yes, unchanged as well. The server and client can be preconfigured to store passwords.
– Vesa
Jan 23 at 5:12
"Easiest" is very much a function of "what tools do you have available, and how is the whole system set up". "Too many firewalls" indicate complications we know nothing about.
– dirkt
Jan 23 at 6:02
@dirkt The server is running Ubuntu, very recent version and I can access most tools there are. So there are probably some good solutions for this issue. With regard to the firewalls I have tested SSH and ruled it out because I don't want to run an SSH server either on the sending computer or the receiving computer.
– Vesa
Jan 23 at 10:06
1
If the problem isn't that ssh can't get through the firewalls: You'll have to run some sort of "server" anyway, no matter if you "type" the server on your commandline using available tools, or if you just start it. Setting up an ssh-server is trivial, secure, and solves all the problems you'd need to solve manually. If you insist on doing it manually, first thing that comes to mind is socat/netcat (which will start a temporary "server") on both the receiving and teh sending computer. You'll have to encrypt and decrypt yourself.
– dirkt
Jan 23 at 11:49
add a comment |
3
What do you mean by "securely"? Do you just want to be sure that the message arrives? Or that it arrives unchanged? Or that no one else can read it? Can you share a separate secret (password) between the server & client?
– Xen2050
Jan 23 at 1:18
Well, granted, the message should arrive, otherwise there would not be any point in sending it. It should also be impossible to read for others and yes, unchanged as well. The server and client can be preconfigured to store passwords.
– Vesa
Jan 23 at 5:12
"Easiest" is very much a function of "what tools do you have available, and how is the whole system set up". "Too many firewalls" indicate complications we know nothing about.
– dirkt
Jan 23 at 6:02
@dirkt The server is running Ubuntu, very recent version and I can access most tools there are. So there are probably some good solutions for this issue. With regard to the firewalls I have tested SSH and ruled it out because I don't want to run an SSH server either on the sending computer or the receiving computer.
– Vesa
Jan 23 at 10:06
1
If the problem isn't that ssh can't get through the firewalls: You'll have to run some sort of "server" anyway, no matter if you "type" the server on your commandline using available tools, or if you just start it. Setting up an ssh-server is trivial, secure, and solves all the problems you'd need to solve manually. If you insist on doing it manually, first thing that comes to mind is socat/netcat (which will start a temporary "server") on both the receiving and teh sending computer. You'll have to encrypt and decrypt yourself.
– dirkt
Jan 23 at 11:49
3
3
What do you mean by "securely"? Do you just want to be sure that the message arrives? Or that it arrives unchanged? Or that no one else can read it? Can you share a separate secret (password) between the server & client?
– Xen2050
Jan 23 at 1:18
What do you mean by "securely"? Do you just want to be sure that the message arrives? Or that it arrives unchanged? Or that no one else can read it? Can you share a separate secret (password) between the server & client?
– Xen2050
Jan 23 at 1:18
Well, granted, the message should arrive, otherwise there would not be any point in sending it. It should also be impossible to read for others and yes, unchanged as well. The server and client can be preconfigured to store passwords.
– Vesa
Jan 23 at 5:12
Well, granted, the message should arrive, otherwise there would not be any point in sending it. It should also be impossible to read for others and yes, unchanged as well. The server and client can be preconfigured to store passwords.
– Vesa
Jan 23 at 5:12
"Easiest" is very much a function of "what tools do you have available, and how is the whole system set up". "Too many firewalls" indicate complications we know nothing about.
– dirkt
Jan 23 at 6:02
"Easiest" is very much a function of "what tools do you have available, and how is the whole system set up". "Too many firewalls" indicate complications we know nothing about.
– dirkt
Jan 23 at 6:02
@dirkt The server is running Ubuntu, very recent version and I can access most tools there are. So there are probably some good solutions for this issue. With regard to the firewalls I have tested SSH and ruled it out because I don't want to run an SSH server either on the sending computer or the receiving computer.
– Vesa
Jan 23 at 10:06
@dirkt The server is running Ubuntu, very recent version and I can access most tools there are. So there are probably some good solutions for this issue. With regard to the firewalls I have tested SSH and ruled it out because I don't want to run an SSH server either on the sending computer or the receiving computer.
– Vesa
Jan 23 at 10:06
1
1
If the problem isn't that ssh can't get through the firewalls: You'll have to run some sort of "server" anyway, no matter if you "type" the server on your commandline using available tools, or if you just start it. Setting up an ssh-server is trivial, secure, and solves all the problems you'd need to solve manually. If you insist on doing it manually, first thing that comes to mind is socat/netcat (which will start a temporary "server") on both the receiving and teh sending computer. You'll have to encrypt and decrypt yourself.
– dirkt
Jan 23 at 11:49
If the problem isn't that ssh can't get through the firewalls: You'll have to run some sort of "server" anyway, no matter if you "type" the server on your commandline using available tools, or if you just start it. Setting up an ssh-server is trivial, secure, and solves all the problems you'd need to solve manually. If you insist on doing it manually, first thing that comes to mind is socat/netcat (which will start a temporary "server") on both the receiving and teh sending computer. You'll have to encrypt and decrypt yourself.
– dirkt
Jan 23 at 11:49
add a comment |
1 Answer
1
active
oldest
votes
Answering the original "What is the easiest way to send a file or a text message securely from a server to a client if SSH is not an option?":
If by "securely" you mean that no one else can read it, then I think the easiest answer is to just use GPG and encrypt the file.
Either by using a (secret) shared passphrase and gpg's -c, --symmetric option, or create a keypair at both ends, share the public keys, and create messages back & forth through any private or public means available, plain email, telnet, a public webpage, usenet, anything that can send a file.
With the question edited to remove the secure requirement, the easiest is probably to just send an email.
However, with edits constantly moving the goalpost (not secure, no GUI, command line only, then no manual intervention) I'm not sure what the root question is anymore. So just use ssh, or ftp, or netcat, or telnet, but they all need servers set up & ports opened in firewalls, etc. Or wget, or lynx with a 3rd server somewhere.
answered Jan 23 at 1:22
Xen2050Xen2050
11k31536
Wait, it's the last part I need help with. I don't need a lot of help encrypting with GPG. As I said, I have already ruled out e-mail and SSH. I would ideally want to receive the file or text message directly in my Terminal on the client side. I have considered Telnet but I'm not sure about how to configure it. I would prefer not having to set up servers on either side of the network.
– Vesa
Jan 23 at 5:14
1
Why not just send an email? If you've got "too many Firewalls and stuff" preventing ssh, I'm not sure if telnet would be very different. Or an IM program that sends files, like pidgin, empathy, gajim, kopete, etc
– Xen2050
Jan 23 at 6:27
This is command line only. I have tested a lot of email clients and servers for Terminal over the years but never found anything that feels like the right tool for the job. There might be some package and some way to configure it to make it suitable but I have never found it yet over the course of the years. Actually i have been thinking about this issue for a while, there should be some dead easy and smooth way to send a message from one Terminal to another over the Internet. If you know an efficient way, please let me know.
– Vesa
Jan 23 at 10:11
That wasn't a hard requirement of the question originally (honestly it's still a rather vague question, I was only going to comment originally but technically I seemed to have "an answer"...) but anyway ssh sounds best, or ftp/sftp, or telnet, but they all need servers set up & ports opened in firewalls, etc. Or there'swgetto download a file from a web server, or even the terminal web browserlynxcould sign into web email with (gmail might not work, but they're not the only email game in town, there still should be cheap/free shell accounts with email around somewhere)
– Xen2050
Jan 23 at 11:27
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1397225%2fwhat-is-the-easiest-way-to-send-a-file-or-a-text-message-from-a-server-to-a-clie%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Answering the original "What is the easiest way to send a file or a text message securely from a server to a client if SSH is not an option?":
If by "securely" you mean that no one else can read it, then I think the easiest answer is to just use GPG and encrypt the file.
Either by using a (secret) shared passphrase and gpg's -c, --symmetric option, or create a keypair at both ends, share the public keys, and create messages back & forth through any private or public means available, plain email, telnet, a public webpage, usenet, anything that can send a file.
With the question edited to remove the secure requirement, the easiest is probably to just send an email.
However, with edits constantly moving the goalpost (not secure, no GUI, command line only, then no manual intervention) I'm not sure what the root question is anymore. So just use ssh, or ftp, or netcat, or telnet, but they all need servers set up & ports opened in firewalls, etc. Or wget, or lynx with a 3rd server somewhere.
answered Jan 23 at 1:22
Xen2050Xen2050
11k31536
Wait, it's the last part I need help with. I don't need a lot of help encrypting with GPG. As I said, I have already ruled out e-mail and SSH. I would ideally want to receive the file or text message directly in my Terminal on the client side. I have considered Telnet but I'm not sure about how to configure it. I would prefer not having to set up servers on either side of the network.
– Vesa
Jan 23 at 5:14
1
Why not just send an email? If you've got "too many Firewalls and stuff" preventing ssh, I'm not sure if telnet would be very different. Or an IM program that sends files, like pidgin, empathy, gajim, kopete, etc
– Xen2050
Jan 23 at 6:27
This is command line only. I have tested a lot of email clients and servers for Terminal over the years but never found anything that feels like the right tool for the job. There might be some package and some way to configure it to make it suitable but I have never found it yet over the course of the years. Actually i have been thinking about this issue for a while, there should be some dead easy and smooth way to send a message from one Terminal to another over the Internet. If you know an efficient way, please let me know.
– Vesa
Jan 23 at 10:11
That wasn't a hard requirement of the question originally (honestly it's still a rather vague question, I was only going to comment originally but technically I seemed to have "an answer"...) but anyway ssh sounds best, or ftp/sftp, or telnet, but they all need servers set up & ports opened in firewalls, etc. Or there'swgetto download a file from a web server, or even the terminal web browserlynxcould sign into web email with (gmail might not work, but they're not the only email game in town, there still should be cheap/free shell accounts with email around somewhere)
– Xen2050
Jan 23 at 11:27
add a comment |
Answering the original "What is the easiest way to send a file or a text message securely from a server to a client if SSH is not an option?":
If by "securely" you mean that no one else can read it, then I think the easiest answer is to just use GPG and encrypt the file.
Either by using a (secret) shared passphrase and gpg's -c, --symmetric option, or create a keypair at both ends, share the public keys, and create messages back & forth through any private or public means available, plain email, telnet, a public webpage, usenet, anything that can send a file.
With the question edited to remove the secure requirement, the easiest is probably to just send an email.
However, with edits constantly moving the goalpost (not secure, no GUI, command line only, then no manual intervention) I'm not sure what the root question is anymore. So just use ssh, or ftp, or netcat, or telnet, but they all need servers set up & ports opened in firewalls, etc. Or wget, or lynx with a 3rd server somewhere.
answered Jan 23 at 1:22
Xen2050Xen2050
11k31536
Wait, it's the last part I need help with. I don't need a lot of help encrypting with GPG. As I said, I have already ruled out e-mail and SSH. I would ideally want to receive the file or text message directly in my Terminal on the client side. I have considered Telnet but I'm not sure about how to configure it. I would prefer not having to set up servers on either side of the network.
– Vesa
Jan 23 at 5:14
1
Why not just send an email? If you've got "too many Firewalls and stuff" preventing ssh, I'm not sure if telnet would be very different. Or an IM program that sends files, like pidgin, empathy, gajim, kopete, etc
– Xen2050
Jan 23 at 6:27
This is command line only. I have tested a lot of email clients and servers for Terminal over the years but never found anything that feels like the right tool for the job. There might be some package and some way to configure it to make it suitable but I have never found it yet over the course of the years. Actually i have been thinking about this issue for a while, there should be some dead easy and smooth way to send a message from one Terminal to another over the Internet. If you know an efficient way, please let me know.
– Vesa
Jan 23 at 10:11
That wasn't a hard requirement of the question originally (honestly it's still a rather vague question, I was only going to comment originally but technically I seemed to have "an answer"...) but anyway ssh sounds best, or ftp/sftp, or telnet, but they all need servers set up & ports opened in firewalls, etc. Or there'swgetto download a file from a web server, or even the terminal web browserlynxcould sign into web email with (gmail might not work, but they're not the only email game in town, there still should be cheap/free shell accounts with email around somewhere)
– Xen2050
Jan 23 at 11:27
add a comment |
Answering the original "What is the easiest way to send a file or a text message securely from a server to a client if SSH is not an option?":
If by "securely" you mean that no one else can read it, then I think the easiest answer is to just use GPG and encrypt the file.
Either by using a (secret) shared passphrase and gpg's -c, --symmetric option, or create a keypair at both ends, share the public keys, and create messages back & forth through any private or public means available, plain email, telnet, a public webpage, usenet, anything that can send a file.
With the question edited to remove the secure requirement, the easiest is probably to just send an email.
However, with edits constantly moving the goalpost (not secure, no GUI, command line only, then no manual intervention) I'm not sure what the root question is anymore. So just use ssh, or ftp, or netcat, or telnet, but they all need servers set up & ports opened in firewalls, etc. Or wget, or lynx with a 3rd server somewhere.
answered Jan 23 at 1:22
Xen2050Xen2050
11k31536
Answering the original "What is the easiest way to send a file or a text message securely from a server to a client if SSH is not an option?":
If by "securely" you mean that no one else can read it, then I think the easiest answer is to just use GPG and encrypt the file.
Either by using a (secret) shared passphrase and gpg's -c, --symmetric option, or create a keypair at both ends, share the public keys, and create messages back & forth through any private or public means available, plain email, telnet, a public webpage, usenet, anything that can send a file.
With the question edited to remove the secure requirement, the easiest is probably to just send an email.
However, with edits constantly moving the goalpost (not secure, no GUI, command line only, then no manual intervention) I'm not sure what the root question is anymore. So just use ssh, or ftp, or netcat, or telnet, but they all need servers set up & ports opened in firewalls, etc. Or wget, or lynx with a 3rd server somewhere.
answered Jan 23 at 1:22
Xen2050Xen2050
11k31536
edited Jan 24 at 1:07
answered Jan 23 at 1:22
Xen2050Xen2050
11k31536
answered Jan 23 at 1:22
Xen2050Xen2050
11k31536
answered Jan 23 at 1:22
Xen2050Xen2050
11k31536
11k31536
Wait, it's the last part I need help with. I don't need a lot of help encrypting with GPG. As I said, I have already ruled out e-mail and SSH. I would ideally want to receive the file or text message directly in my Terminal on the client side. I have considered Telnet but I'm not sure about how to configure it. I would prefer not having to set up servers on either side of the network.
– Vesa
Jan 23 at 5:14
1
Why not just send an email? If you've got "too many Firewalls and stuff" preventing ssh, I'm not sure if telnet would be very different. Or an IM program that sends files, like pidgin, empathy, gajim, kopete, etc
– Xen2050
Jan 23 at 6:27
This is command line only. I have tested a lot of email clients and servers for Terminal over the years but never found anything that feels like the right tool for the job. There might be some package and some way to configure it to make it suitable but I have never found it yet over the course of the years. Actually i have been thinking about this issue for a while, there should be some dead easy and smooth way to send a message from one Terminal to another over the Internet. If you know an efficient way, please let me know.
– Vesa
Jan 23 at 10:11
That wasn't a hard requirement of the question originally (honestly it's still a rather vague question, I was only going to comment originally but technically I seemed to have "an answer"...) but anyway ssh sounds best, or ftp/sftp, or telnet, but they all need servers set up & ports opened in firewalls, etc. Or there'swgetto download a file from a web server, or even the terminal web browserlynxcould sign into web email with (gmail might not work, but they're not the only email game in town, there still should be cheap/free shell accounts with email around somewhere)
– Xen2050
Jan 23 at 11:27
add a comment |
Wait, it's the last part I need help with. I don't need a lot of help encrypting with GPG. As I said, I have already ruled out e-mail and SSH. I would ideally want to receive the file or text message directly in my Terminal on the client side. I have considered Telnet but I'm not sure about how to configure it. I would prefer not having to set up servers on either side of the network.
– Vesa
Jan 23 at 5:14
1
Why not just send an email? If you've got "too many Firewalls and stuff" preventing ssh, I'm not sure if telnet would be very different. Or an IM program that sends files, like pidgin, empathy, gajim, kopete, etc
– Xen2050
Jan 23 at 6:27
This is command line only. I have tested a lot of email clients and servers for Terminal over the years but never found anything that feels like the right tool for the job. There might be some package and some way to configure it to make it suitable but I have never found it yet over the course of the years. Actually i have been thinking about this issue for a while, there should be some dead easy and smooth way to send a message from one Terminal to another over the Internet. If you know an efficient way, please let me know.
– Vesa
Jan 23 at 10:11
That wasn't a hard requirement of the question originally (honestly it's still a rather vague question, I was only going to comment originally but technically I seemed to have "an answer"...) but anyway ssh sounds best, or ftp/sftp, or telnet, but they all need servers set up & ports opened in firewalls, etc. Or there'swgetto download a file from a web server, or even the terminal web browserlynxcould sign into web email with (gmail might not work, but they're not the only email game in town, there still should be cheap/free shell accounts with email around somewhere)
– Xen2050
Jan 23 at 11:27
Wait, it's the last part I need help with. I don't need a lot of help encrypting with GPG. As I said, I have already ruled out e-mail and SSH. I would ideally want to receive the file or text message directly in my Terminal on the client side. I have considered Telnet but I'm not sure about how to configure it. I would prefer not having to set up servers on either side of the network.
– Vesa
Jan 23 at 5:14
Wait, it's the last part I need help with. I don't need a lot of help encrypting with GPG. As I said, I have already ruled out e-mail and SSH. I would ideally want to receive the file or text message directly in my Terminal on the client side. I have considered Telnet but I'm not sure about how to configure it. I would prefer not having to set up servers on either side of the network.
– Vesa
Jan 23 at 5:14
1
1
Why not just send an email? If you've got "too many Firewalls and stuff" preventing ssh, I'm not sure if telnet would be very different. Or an IM program that sends files, like pidgin, empathy, gajim, kopete, etc
– Xen2050
Jan 23 at 6:27
Why not just send an email? If you've got "too many Firewalls and stuff" preventing ssh, I'm not sure if telnet would be very different. Or an IM program that sends files, like pidgin, empathy, gajim, kopete, etc
– Xen2050
Jan 23 at 6:27
This is command line only. I have tested a lot of email clients and servers for Terminal over the years but never found anything that feels like the right tool for the job. There might be some package and some way to configure it to make it suitable but I have never found it yet over the course of the years. Actually i have been thinking about this issue for a while, there should be some dead easy and smooth way to send a message from one Terminal to another over the Internet. If you know an efficient way, please let me know.
– Vesa
Jan 23 at 10:11
This is command line only. I have tested a lot of email clients and servers for Terminal over the years but never found anything that feels like the right tool for the job. There might be some package and some way to configure it to make it suitable but I have never found it yet over the course of the years. Actually i have been thinking about this issue for a while, there should be some dead easy and smooth way to send a message from one Terminal to another over the Internet. If you know an efficient way, please let me know.
– Vesa
Jan 23 at 10:11
That wasn't a hard requirement of the question originally (honestly it's still a rather vague question, I was only going to comment originally but technically I seemed to have "an answer"...) but anyway ssh sounds best, or ftp/sftp, or telnet, but they all need servers set up & ports opened in firewalls, etc. Or there's
wget to download a file from a web server, or even the terminal web browser lynx could sign into web email with (gmail might not work, but they're not the only email game in town, there still should be cheap/free shell accounts with email around somewhere)– Xen2050
Jan 23 at 11:27
That wasn't a hard requirement of the question originally (honestly it's still a rather vague question, I was only going to comment originally but technically I seemed to have "an answer"...) but anyway ssh sounds best, or ftp/sftp, or telnet, but they all need servers set up & ports opened in firewalls, etc. Or there's
wget to download a file from a web server, or even the terminal web browser lynx could sign into web email with (gmail might not work, but they're not the only email game in town, there still should be cheap/free shell accounts with email around somewhere)– Xen2050
Jan 23 at 11:27
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1397225%2fwhat-is-the-easiest-way-to-send-a-file-or-a-text-message-from-a-server-to-a-clie%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
3
What do you mean by "securely"? Do you just want to be sure that the message arrives? Or that it arrives unchanged? Or that no one else can read it? Can you share a separate secret (password) between the server & client?
– Xen2050
Jan 23 at 1:18
Well, granted, the message should arrive, otherwise there would not be any point in sending it. It should also be impossible to read for others and yes, unchanged as well. The server and client can be preconfigured to store passwords.
– Vesa
Jan 23 at 5:12
"Easiest" is very much a function of "what tools do you have available, and how is the whole system set up". "Too many firewalls" indicate complications we know nothing about.
– dirkt
Jan 23 at 6:02
@dirkt The server is running Ubuntu, very recent version and I can access most tools there are. So there are probably some good solutions for this issue. With regard to the firewalls I have tested SSH and ruled it out because I don't want to run an SSH server either on the sending computer or the receiving computer.
– Vesa
Jan 23 at 10:06
1
If the problem isn't that ssh can't get through the firewalls: You'll have to run some sort of "server" anyway, no matter if you "type" the server on your commandline using available tools, or if you just start it. Setting up an ssh-server is trivial, secure, and solves all the problems you'd need to solve manually. If you insist on doing it manually, first thing that comes to mind is socat/netcat (which will start a temporary "server") on both the receiving and teh sending computer. You'll have to encrypt and decrypt yourself.
– dirkt
Jan 23 at 11:49