The way to do scp transfers without a password is to set up SSH key authentication on both boxes.
Here's a starting point. Google away for more info: http://www.linuxquestions.org/linux/articles/Jeremys_Magazine_Articles/Using_Keys_with_SSH Micah On Thu, Oct 23, 2008 at 2:05 PM, Eric Shubert <[EMAIL PROTECTED]> wrote: > There is a -B (batch mode) option that prevents asking for passwords. > I'm not sure how that would work though. I expect that the target > system's user account would need to have no password in that case, but > I'm not sure of that. > > rsync really isn't much different syntax wise from scp, and it allows > for a --password-file option that's handy when using the command in scripts. > > Josef Lowder wrote: >> And the scp file transfer worked. >> It did ask for a password, though. >> Not a big problem, but is there any way >> to avoid that requirement for an extra manual step? >> Perhaps put the password in the initial syntax somehow? >> >> >> On Thu, Oct 23, 2008 at 3:15 PM, Josef Lowder <[EMAIL PROTECTED]> wrote: >>> Thanks, Eric. That solved the sshd issue. >>> So now, I will try scp again. >>> >>> >>> On Thu, Oct 23, 2008 at 3:12 PM, Eric Shubert <[EMAIL PROTECTED]> wrote: >>>> Trial and error. I'd start with making sure sshd is running on the >>>> target machine. Usually (depending on distro), >>>> # /etc/init.d/sshd status >>>> will tell if it's running or not. If it's not running, >>>> # /etc/init.d/sshd start >>>> should start it up, but only until the next reboot. The method of making >>>> it persistent depends on the distro. >>>> >>>> Josef Lowder wrote: >>>>> So how do I determine which is the problem >>>>> and how do I fix or get around that? >>>>> >>>>> On 10/23/08, Eric Shubert <[EMAIL PROTECTED]> wrote: >>>>>> Josef Lowder wrote: >>>>>> > Well, I think I'm finally getting closer, now that I understand >>>>>> > what the actual syntax should look like with real data in it. >>>>>> > This is what I tried: >>>>>> > >>>>>> > $ scp /home/joe/mydata/track2 [EMAIL >>>>>> PROTECTED]:/home/joe/mydata/track2 >>>>>> > >>>>>> > That seemed to almost work ... except I got this reply: >>>>>> > >>>>>> > ssh: connect to host 192.168.1.66 port 22: Connection refused >>>>>> > lost connection >>>>>> > >>>>>> > So why would that connection be refused, and how do I fix that? >>>>>> >>>>>> >>>>>> Either a firewall is blocking port 22, or sshd isn't running on the >>>>>> target machine? >>>>>> >>>>>> >>>>>> -- >>>>>> -Eric 'shubes' >>>>>> >>>> -- >>>> -Eric 'shubes' >>>> >>>> --------------------------------------------------- >>>> PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us >>>> To subscribe, unsubscribe, or to change your mail settings: >>>> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss >>>> >>>> > > > -- > -Eric 'shubes' > > --------------------------------------------------- > PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us > To subscribe, unsubscribe, or to change your mail settings: > http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss > --------------------------------------------------- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
