From: Stelian P. <po...@cy...> - 2000-02-18 22:35:12
|
On Fri, 11 Feb 2000, Frank Koormann wrote: > Performing remote dumps I use ssh instead of rsh. > However due to changes in common/dumprmt.c (1.11) > the password is no langer transfered to the ssh > but can be seen in plain text on the console. > > I don't think this is really a bug but only a > smaller problem. Hence I am refering to this list. Yes, I am aware of this issue, but it's not that simple to deal with it... The old way to handle RSH caused the rsh process (ssh in your case) to be killed when the user pressed ^C. Dump itself catches the signal and asks if you really want to abort the dump. If you respond with 'no', you're out of luck because ssh itself catched the signal and died. So the backup will fail. This is what the patch solved. The only way to make ssh not interpret the ^C was to put it into a new process group, detached from the terminal. The ^C works this way, but ssh, since it has no more a terminal to read from, cannot ask anymore for a password... The solution would be to make ssh not ask for a password, using one of its RSAHosts or RSA methods of authentificate. Both two ways are not satisfying me, but I don't see any either solution... Stelian. -- /\ / \ Stelian Pop / DS \ Email: po...@cy... \____/ |