Re: Changing an existing tool to talk over ssh

From: all mail refused (elvis_at_notatla.org.uk)
Date: 03/16/04 

Date: 16 Mar 2004 19:05:06 GMT

In article <RZG5c.10158$ON5.225@newssvr23.news.prodigy.com>, Steve Turner wrote:

>I'm investigating the modification of an existing tool (written in C)
>that connects to a daemon version of itself and converses in a slightly
>complex synchronous read/write protocol over a single socket. Knowing
>next to nothing about how ssh-enabled tools speak to each other at the
>level of the programming interfaces, am I right in thinking that the
>tool would first need to be modified to hold its conversation over two
>separate socket handles (duped to stdin and stdout respectively) before
>it could use ssh as the transport?

These days I use more Perl than C but I do synchronous read/write
protocols over a single socket with SSH.

On "how ssh-enabled tools speak to each other": this is up to you.

For programming interface I use the existing ssh binary and call
it code reuse. 

-- 
Elvis Notargiacomo  master AT barefaced DOT cheek