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 there remains another method of feeding this passwd to that progB. What is/are that/they ? So instead of of all these I let the progB prompt for passwd. This specific passwd asking external/separate prog I exec internally from within that progB. From machineA when I do "ssh machineB <prog_in_machineB>". So that prompt appears to me here in machineA. This way the password is not being captured & stored in any variable in progA at least. Actually only progB requires that password for it's task.
--- On Thu, 10/27/11, [email protected] <[email protected]> wrote: Why Not prompt for the password on machine a at the beginning?
_______________________________________________ Perl-Win32-Users mailing list [email protected] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
