> Additionally, dealing with the SSH known hosts file is somewhat of a > problem. If no additional options are passed to SSH, in many cases it > is expected that the user would not have added the keys for the relevant > host to /root/.ssh/known_hosts before running the ebuild command; thus, > the client would not allow the connection.
You can write an interface inbetween the eclass and ssh using popen and forktty. I did this for work. It's fairly aggitating to do, but does work. forktty opens master and slave pty's and you use the master as the stderr pipe that communicates with ssh for the password and the host messages. The data you have to do close() and dup() operations to get them forwarded to the interface's stdout and stdin. --NJ -- [EMAIL PROTECTED] mailing list
