next »

[perkiset]

Hey all -

I have a need to scp a file nightly to a vendor. Accounts are good, doing it manually floats without complaint.

I've used the techniques described here: http://www.linuxjournal.com/node/8600/print to try to make it work in a script, but it still asks for the password when it runs (obviously it's not cron-able then). I have done the keygen, sent them the key, they are looking again to make sure that it is placed correctly. Is there anything special that I need to do on my side, or is there a special nudge-nudge-wink-wink-handkshake I might need to get this working correctly?

Any help greatly appreciated,
/p

[nop_90]

dig up that post i make on syndk8 ages ago about how to do that.
it was on a polish linux site (but was in english).
i think the title was controlling your boxes remotely.

even more cool is with ssh you can run apps on server, and pipe output back to client

example
ssh server ls
will give you listing

[perkiset]

I just searched my brains out, and am not in a place to walk backwards through all of your posts to find it... you wouldn't happen to remember anything about the polish linux site, would you?

BTW, I get where you're going with the ssh stuff as well... there's lots of coolness in there...

[nop_90]

sorry
http://polishlinux.org/apps/ssh-tricks/

there used to be an OS section there, but it seems to be missing :O

[perkiset]

Great page, thanks a bunch. I'll probably scoff a bunch of it and post it here so that it doesn't go away...

[nop_90]

I use it constantantly
I use scp to move the files up to my server
ssh to run shit on server and then pipe to me
basically with ssh you can do everything remotely that you do on ur desktop

and he explains how to set the key so u do not need password
also i think he has article how to make ssh into a proxy/tunnel

[gnarlyhat]

Nice info nop. I myself use a SSH tunneling server set up a home. I use it as a poor man's VPN whenever I'm outside using unsecured networks and wireless hotspots just to make sure that my data is not sniffed/hijacked. It's been sitting there collecting dust a lot lately as I don't see the need for me to be using unsecured public networks to access my sensitive sites/data.

[thedarkness]

 

[ratthing]

The first time you connect to the server via ssh, you have to do it interactively so you can accept the server's RSA fingerprint.

When using ssh to run commands, if the shell returns any kind of information to standard out, you'll have problems because of the nature of a non-interactive shell. 

Try ssh'ing over using the key without any commands to check what's being displayed on your terminal.

If you can't get in with the key due to it prompting with the password, you'll need to check the sshd_config file on the server side.  Sometimes key login is turned off.  And it's stating the obvious, but root logins are almost always turned off, with or without keys.

I get around this latter by executing "sudo" commands over ssh as a normal user.

There are also some weird escapes that have to be done when you send over ssh commands.  I can dig around for some old shell scripts  so I can remember the details if you need more info on that.

HTH--
=RT=