topic Re: regarding SFTP in Operating System - HP-UX

regarding SFTP

Sachin_29 — Wed, 23 Jun 2004 22:00:26 GMT

Hi:
I am trying to SFTP some files thru Ksh I want to run the script(see below) thru scheduler. If I run this script it prompts for the password, Is there any way that it could be automated or read thru some file.
I know we could do it in FTP but FTP is not an option .. i HAVE to use SFTP
Please let me know if there is any way
#!/usr/bin/ksh
$INFILE="Input.txt"
while read -r i
do
cd /home/$i/logs
/usr/bin/sftp user@host <>output.log
put *.log
quit
EOF
done<$INFILE
Thanks

Re: regarding SFTP

Simon Hargrave — Thu, 24 Jun 2004 04:24:21 GMT

The "best" way to do this is setup a key pair and use ssh-agent to cache the credentials.

The next best way is to set up a key pair, with a blank passphrase. This is still secure data transfer, but if the keys are compromised, so is access.

The poorest way is to use an "expect" script. You can get expect from the HP porting center.

Regards, Simon

Re: regarding SFTP

Sachin_29 — Thu, 24 Jun 2004 09:30:03 GMT

Simon,
Thanks for the response.
I have couple of questions,
How could i do that if I have to SFTP files from 6 different server to one single server??
How is SCP ? Is it different from SFTP?
Is that an option ?
Appreciate your feedback

Re: regarding SFTP

RAC_1 — Thu, 24 Jun 2004 09:42:02 GMT

You can use scp/sftp.

You need to authentication to exchange of public/private keys.

Generate the keys. ssh-keygen -t dsa
It will create the public and private keys. (*.pub) is pubic key.

Put this key in server_where_you_want_to_sftp/scp:$HOME/.ssh/authorized_keys.

Do not do cut/paste business to copy the key to authorized_keys file. Transfer the *.pub file by ftp/sftp/scp/rcp etc.

Once you are set for authentication to exchange of private/public keys, use your code to pull the files from all 6 servers to one server.

Anil

Re: regarding SFTP

R. Sri Ram Kishore_1 — Thu, 24 Jun 2004 09:42:04 GMT

Hi,

For the difference between SCP and SFTP, see:
http://www.cam.ac.uk/cs/filetransfer/compare.html

HTH.

Regards,
Sri Ram

Re: regarding SFTP

Steven E. Protter — Thu, 24 Jun 2004 09:46:41 GMT

scp is the way to go.

scp is the rcp replacement that is secure, it is part of openssh.

Here is how you script it

$LOGDIR=/home$i/logs
cd $LOGDIR
scp *.log user@hostname://directory

You can do this password free if you follow the document I am giving you to exchange publickeys between the two servers.

You can use cat, the doc says use X but you can do it all with cat commands.

see doc

SEP

Re: regarding SFTP

Sachin_29 — Thu, 24 Jun 2004 11:59:46 GMT

Hi :
thanks it works between my test server for me here..
But the remote server I have access to doesnt have my $HOME directory.
I could put the authorized_key files in one of the folder ? In this case how does this work??
Please let me know

Re: regarding SFTP

Abdul Rahiman — Thu, 24 Jun 2004 14:42:27 GMT

Sachin,
You don't have a home directory in the remote server for the login name?
Is it for only to do the sftp or something?

I think if the remote server is running ssh1, it expects the key files to be in the ~/.ssh directory.

But if it is ssh2, thre is a parameter called "UserConfigDirectory", which need to be setup in their sshd_config file. But the catch is this is a system wide parameter and all user's authorized keys file location would change.

Here is the excerpts from a ssh documentation,
5.4.1.5. User SSH directory
sshd1 expects a user's SSH-related files to be found in the directory ~/.ssh. This location can't be changed by serverwide configuration. (You have to modify the source code.)

sshd2 expects user files to be in the directory ~/.ssh2 by default, but this can be changed with the UserConfigDirectory keyword. The directory name may be literal, as in:

# SSH2 only
UserConfigDirectory /usr/local/ssh/my_dir
or it may be specified with printf-like patterns, as in:

# SSH2 only
UserConfigDirectory %D/.my-ssh
The %D pattern expands to the user's home directory. So the preceding example expands to ~/.my-ssh. The following table shows the available patterns:

Here is the full link,
http://216.239.51.104/search?q=cache:AdvSrye6xRkJ:secu.zzu.edu.cn/book/NetWork/NetworkingBookshelf_2ndEd/ssh/ch05_04.htm+ssh+userconfigdirectory&hl=en

HTH,
Abdul.

Re: regarding SFTP

RAC_1 — Thu, 24 Jun 2004 15:01:17 GMT

If you do not have $HOME on that particulat server, then where does it take you when you login?? Try creating .ssh in there and putting *.pub in .ssh/authorized_keys.

Don't know, if this will work or not.

Anil

Re: regarding SFTP

Sachin_29 — Thu, 24 Jun 2004 17:17:34 GMT

Unfortunately, there is a very limited access to the remote server. Once I log in to the remote server, I get logged on to / i have write permission on only one directory
A. I creatd .ssh/authorized_keys under A doesnt help.. and also authorized_keys under A (just for the heck of it) ..
Truly appreciate all of your help.. learnt a lot from this thread.
Any solution is always welcome .. If i find any solution I would post it ..Last optionis to try expect which I would try to avoid..
thanks a lot..
Sachin

Re: regarding SFTP

Jon A. Miller — Fri, 25 Jun 2004 09:41:12 GMT

May I extend the breadth of this thread:
We also are implementing SFTP; our problem is
converting our customers from the GUI WS_FTP
that I believe uses anonymous ftp, to WINSCP
GUI. Problem is preventing the customer from transversing up the directory. We have read the numerous 'chroot jail' solutions, but it seems so 'messy'. We have a common
directory for all customers who can transverse many different subdirectories. Permissions is not a viable alternative.
We are soliciting comments/best practices /solutions.
Thank you in advance