Using IBM i? Need to create Excel, CSV, HTML, JSON, PDF, SPOOL reports? Learn more about the fastest and least expensive tool for the job: SQL iQuery.
Happy Friday. Everything I've been reading says not to use a passphrase in a private/public key for an SSH connection if the job is going to run in batch, because someone has to answer it manually. The users that I'm developing the SFTP process for want a passphrase for additional security. Is there a way to automate the entry of the passphrase? Maybe in the script file or something like that? I know that kind of defeats the purpose for "additional security".
Maybe I just need to tell them that unless they want to run the job and enter the passphrase every time it comes up a passphrase can't be used.
Thoughts?????
Let me refer you again to Scott Klement's presentation and read the part about the EXPECT utility which emulates a Unix terminal in batch (starts on page 35). That may or may not work depending on your requirements, but it's worth a look.
Hi Brian. Yeah, I looked at it, but don't think it will work for us. I also tried installing it and it had numerous "file or directory in the path name does not exist" errors.
I'm curious, did you try it in the !--script-- file (-b xxx)? What happened?
Brian,
I too just went through the process of setting up sFTP and found that trying to use a passphrase was too much of a hassle and really does provide that extra level of security if someone has to run the process from a terminal session.
The extra time and effort of having to install and use EXPECT in the !--script-- didn't make sense for a process that is already secure.
Unless they really insist, I would not go through the effort.
Scott Sonntag