The way ssh usually works is you generate a host key on the target system,
transfer it to the source system, and it uses that in lieu of a password.
(It's stored in the /etc/ssh/ directory on my linux system.)

I don't know if there's any real way to "hardcode" an ssh password anywhere
without doing some interesting scripting.

Dave

On Fri, Jul 08, 2005 at 08:51:44PM -0400, Greg Stigers wrote:
> After some effort, and some offlist help, I have openssh doing what I need
> it to do: encrypting and forwarding specific traffic to an outside service
> provider. So far, so good. What has me absolutely stumped is that I cannot
> get ssh to recognize my netrc file. Our provider requires a password, in
> addition to encrypting with a public key. And there seems to be no way to
> feed openssh a password, on MPE. I realize that netrc files are hardly
> popular on 3000s. But I hoped that someone might have an idea of what I
> might be overlooking.
>
> Greg Stigers
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

--
+--David Oksner-----http://www.case.net/--+
|Murphy's Military Laws:                  |
|8. Incoming fire has the right of way.   |
[log in to unmask]

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *