Re: Pyro4 over SSH (native SSH or paramiko)

Hi Irmen,

On 29/06/13 19:40, Irmen de Jong wrote:
> Native SSL support in Pyro will likely never happen (by me) because I don't have much
> SSL development experience and I think it is too hard to 'get it right'. (at this time).

Indeed, SSL might be desirable in some cases, but as you say, very
complicated given an easy solution is to just fire up an instance of
'stunnel' to get almost the same effect.

> The ssh option is more likely to appear one day but for now the way to go is to set up a
> secure connection first (ssh/vpn) and tunnel Pyro over that.

Well, this was the thought.  Thanks to Paramiko, we can write a client
that launches the Pyro4 server, figures out where the server is
listening, then opens a channel.

This can be done now without any changes in Pyro4.  It'd be nice if
there was some utility functions in Pyro4 that automated some of this,
but it can be done.  The downside of this approach is that it wastes a
TCP port on the remote end and a command channel in SSH that could
otherwise be used for the Pyro4 connection itself.

I'll have a look around but I was curious to see if the socket
communication could be abstracted a bit so that a program using Pyro4
could supply an object with a socket-like interface; Pyro4 would then do
its reads/writes as if that were a TCP socket; the program would tunnel
that via SSL/SSH/pipes/serial/smoke signals/avian carriers as required.

Obviously, the default implementation would be the sockets library as it
is now.  I figured I'd ask first before blindly barging in and
duplicating effort.

I'll have a look and see what I can come up with.

Regards,
-- 
Stuart Longland (aka Redhatter, VK4MSL)

I haven't lost my mind...
  ...it's backed up on a tape somewhere.

------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev