in reply to Re: Passing client information between multiple sockets...
in thread Passing client information between multiple sockets...

Are you suggestion that he have Expect enter the password to ssh/slogin? Were does Expect store the password? Does it store it encrypted manner? The only thing I can think of would be to use ssh Public Key Authenication and avoid having to enter a password all together thus removing the need for Expect.

Plankton: 1% Evil, 99% Hot Gas.
  • Comment on Re: Re: Passing client information between multiple sockets...

Replies are listed 'Best First'.
Re: Re: Re: Passing client information between multiple sockets...
by belden (Friar) on May 15, 2004 at 01:53 UTC
    I think Expect will be used for more than just automating the login; it'll also interact with the db shell.
      I don't disagree with you there, but a even a shell script can interact with the db shell. Example ...
      #/bin/sh ssh user@db_server sqlplus /nolog <<EOT connect user passwd select * from whatever where something = $1; EOT
      Also how is Expect going to proctect the login password?

      Plankton: 1% Evil, 99% Hot Gas.