Rmissh communication protocol documentation: no mention about how to generate/setup public/private keys
activeeon-bot opened this issue · 0 comments
activeeon-bot commented
Original issue created by Lorenzo Cantelmi on 18, Aug 2014 at 15:07 PM - PALIGHT-64
It seems that ProActive requires a password-less private key generation ( that cloud open an issue from security point of view, if someone steals the private key). Moreover, a public keys exchange needs to take place between the client and the server, in order to achieve the communication via ssh.
Unfortunately, in the following documentation such a remark and eventual related risks are not pointed out (maybe I am using an old doc).
http://proactive.inria.fr/trunk/Programming/ReferenceManual/multiple_html/SSHTunneling.html