| 1 |
> Additionally, dealing with the SSH known hosts file is somewhat of a |
| 2 |
> problem. If no additional options are passed to SSH, in many cases it |
| 3 |
> is expected that the user would not have added the keys for the relevant |
| 4 |
> host to /root/.ssh/known_hosts before running the ebuild command; thus, |
| 5 |
> the client would not allow the connection. |
| 6 |
|
| 7 |
You can write an interface inbetween the eclass and ssh using popen and |
| 8 |
forktty. I did this for work. It's fairly aggitating to do, but does |
| 9 |
work. forktty opens master and slave pty's and you use the master as |
| 10 |
the stderr pipe that communicates with ssh for the password and the |
| 11 |
host messages. The data you have to do close() and dup() operations |
| 12 |
to get them forwarded to the interface's stdout and stdin. |
| 13 |
|
| 14 |
--NJ |
| 15 |
|
| 16 |
|
| 17 |
-- |
| 18 |
gentoo-dev@g.o mailing list |
Archives