Active Oldest Votes. Improve this answer. This was awesome! Thank you so much, works just as expected — TheCuriouslyCodingFoxah. So I have saved the above script to an sh file and I'm executing as: bash download. No problem; the code above was designed to be copy-pasted into a bash terminal after adapting it to suit your needs. I'll add another answer below with instructions on how to make it into a bash script and how to execute it.
Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Podcast An oral history of Stack Overflow — told by its founding team. You might be having a redirect and not following it the -L param. If you do not want change directory context, use the following script:! Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password.
Post as a guest Name. Email Required, but never shown. The Overflow Blog. Podcast An oral history of Stack Overflow — told by its founding team. Millinery on the Stack: Join us for Winter Summer? Bash, ! Featured on Meta. Not very surprising, really. This is obviously silly, since without using external utilities, there's not much we can do with the downloaded file, not even make it executable. So you can also use SSH to upload to it. Which is functionally equivalent to downloading of software packages etc.
As shown in this answer , you would execute the following on your local machine to place a file on your remote headless server:.
The disadvantage of the above solution compared to downloading is lower transfer speed, since the connection with your local machine usually has much less bandwidth than the connection between your headless server and other servers. To solve that, you can of course execute the above command on another server with decent bandwidth.
To make that more comfortable avoiding a manual login on the third machine , here is a command to execute on your local machine. See the explanations below for the reason. The command will ssh to your third machine intermediate-host , start downloading a file to there via wget , and start uploading it to target-host via SSH. Downloading and uploading use the bandwidth of your intermediate-host and happen at the same time due to Bash pipe equivalents , so progress will be fast.
For the -T -e none SSH options when using it to transfer files, see these detailed explanations. This command is meant for cases where you can't use SSH's public key authentication mechanism — it still happens with some shared hosting providers, notably Host Europe.
To still automate the process, we rely on sshpass to be able to supply the password in the command. It requires sshpass to be installed on your intermediate host sudo apt-get install sshpass under Ubuntu. We try to use sshpass in a secure way, but it will still not be as secure as the SSH pubkey mechanism says man sshpass.
In particular, we supply the SSH password not as a command line argument but via a file, which is replaced by bash process substitution to make sure it never exists on disk. The printf is a bash built-in, making sure this part of the code does not pop up as a separate command in ps output as that would expose the password [ source ].
And that without using a temp file [ source ]. But no guarantees, maybe I overlooked something. Again to make the sshpass usage safe, we need to prevent the command from being recorded to the bash history on your local machine. For that, the whole command is prepended with one space character, which has this effect.
Normally, SSH would then wait for user input to confirm the connection attempt. We make it proceed anyway. So we have to rewrite the typical wget -O - … ssh … command into a form without a bash pipe, as explained here.
Sign up to join this community. After you take a few moments to look it over, I'll walk you through it one step at a time. We'll begin with the single command to download any messages currently residing in my S3 bucket by the way, I've changed the names of the bucket and other filesystem and authentication details to protect my privacy.
Now's the time to do that if you haven't already. The next section sets two variables that will make it much easier for me to specify filesystem locations through the rest of the script. That's because I want to refer to the files within that directory, rather than the directory itself. I'll create a new permanent directory within the The name of this new directory will be the current date.
I then test for the existence of a directly using that name - which would indicate that I've already received emails on that day and, therefore, there's no need to recreate the directory. If such a directory does not exist , then mkdir will create it for me.
0コメント