Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I want to write a short script that will, among other things, copy some files to a different server via scp. Doing this from the command line is easy, but if I want to script it, how do I incorporate the password into my script so that I can run it without being asked for the password (e.g. via cron)?
I want to write a short script that will, among other things, copy some files to a different server via scp. Doing this from the command line is easy, but if I want to script it, how do I incorporate the password into my script so that I can run it without being asked for the password (e.g. via cron)?
Kenn
Don't!
SSH supports certificate authentication, and this is widely used and documented. Just generate an SSH key pair, put your public key on the server you are SCPing to and SCP & SSH will no longer as for a password as you will be 'pre-authenticated'.
For the proper way, you should set up public key authentication. Here's how.
The "wrong" way to do it is to use expect. expect is a library which allows a program to pretend to be a user at a terminal, watch for patterns in the output of the program which is being run, and send commands accordingly. It can also attach the real user to the program. This is, in general the wrong approach for login automation as expect will have to store the account password somewhere, and this is very difficult to do in a secure way.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.