Actually the password is needed for the program which runs on machineB (progB).
Well, we can prompt for passwd when the first program (progA) runs on machineA
and then pass it to the progB. But in this method we will have to pass it as
cli option to machineB prog which I do not want to. Hence
Ok. I understand now. This sounds fine to me.
Am 28.10.2011 um 10:22 schrieb p sena senapati2...@yahoo.com:
Actually the password is needed for the program which runs on machineB
(progB). Well, we can prompt for passwd when the first program (progA) runs
on machineA and then pass it to the
What I did is, removed the facility of taking passwords as CLI options totally.
I just have to prompt for it and user will supply it in the prompt. So I
construct the command in machineA and push that command to machineB via ssh.
Then machineB actually run one program and from it exec's another
Why Not prompt for the password on machine a at the beginning?
Am 27.10.2011 um 09:25 schrieb p sena senapati2...@yahoo.com:
What I did is, removed the facility of taking passwords as CLI options
totally. I just have to prompt for it and user will supply it in the prompt.
So I construct the
Why Not just use ssh options? Ssh Server 'docommand' check Password on machine
a and then sudo to a generic user who has ssh Keys for machine b and executes
then.
Am 23.10.2011 um 04:10 schrieb p sena senapati2...@yahoo.com:
Adding to the original below. Even of in the history it doesn't
Adding to the original below. Even of in the history it doesn't show up
depending on the setup type. But it will definitely show up in the 'ps aux
|grep command_name' output. So this command having some where option value as
'--passwd someabcxyz' and run in machineB how will it be done in a
