------art_10004_20915294.1155943675971
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On 8/18/06, Hal Fulton <hal9000 / hypermetrics.com> wrote:
>
>  Probably not. That's because there are probably multiple problems
> I have in mind.
>
> Basically I want to talk securely to a machine that that knows ssh
> while spending as little time as possible porting my old code that
> uses ftp and telnet libs. (And spending as few neurons in the process
> as I can.)
>
> If you want more concrete examples: I have a habit of keeping multiple
> copies of certain files on different servers. I have a tool that is
> smart enough to sync them as needed each time I edit (no matter which
> one I edited last). It works when the machines' clocks are off, and
> even when they are in different timezones.
>
> Another app I have is to to do some remote config on a server -- run
> a command line app on the client, and it manipulates the server via
> telnet and ftp.
>
> But it's not secure. And my host now is getting hard to access via
> ftp, and impossible via telnet.
>
> Any clearer?



Thanks, Hal. I just asked by way of thinking about if there is an easy way
to solve this without reinventing any wheels. This may sound strange, but
why not use tacked-up SSH tunnels? I've used that approach before, even on
WAN links, and it's workable if you write a little watchdog off a cron job
that makes sure the tunnel stays up.

------art_10004_20915294.1155943675971--