Hi everybody.
I read a problem posted months ago about nimadm and SSH (After several months I had had the same problem, and I had to face the fact nimadm is almost an "As Is" feature.
So to circumvent the rsh limitation problem I wrote a shell script "wrapper" which intercepts any rsh calls, controls if they come from a "nimadm" invocation and convert them in SSH calls, otherwise simply send them to rsh.
The only fee to pay for this method is to copy the NIM server's public key on each client to migrate... but... we are speaking of a migration so, probably, the root authority of those clients would be available at this time.
If anybody is interested I can publish this very simple script/solution for free
I read a problem posted months ago about nimadm and SSH (After several months I had had the same problem, and I had to face the fact nimadm is almost an "As Is" feature.
So to circumvent the rsh limitation problem I wrote a shell script "wrapper" which intercepts any rsh calls, controls if they come from a "nimadm" invocation and convert them in SSH calls, otherwise simply send them to rsh.
The only fee to pay for this method is to copy the NIM server's public key on each client to migrate... but... we are speaking of a migration so, probably, the root authority of those clients would be available at this time.
If anybody is interested I can publish this very simple script/solution for free
