Re: client (slave)-server with authentication

Hi, Richard.

Philip Gwyn would know about using IKC with SSL.  If they don't work  
together yet, you could use stunnel or ssh tunnels to encrypt  
communications.

Server authentication.  Once IKC has been established, the server  
could publish a method to identify itself.  A client can disconnect if  
it doesn't like the answer... although why would it be connecting to  
unknown hosts in the first place?

Client authentication.  Same thing, sort of.  The server can publish a  
login method and refuse all other interaction if the client hasn't  
successfully called that.

-- 
Rocco Caputo - [email protected]


On Dec 18, 2008, at 14:03, [email protected] wrote:

> Hi guys,
>
> I could do with some pointers on where to start. I'm trying to create
> a system with a server on a network and "slave" clients which connect
> to the server, publish a few methods and then sit and wait until the
> server calls one of the methods (on an individual basis, not
> necessarily broadcasting to all clients). So far, I've written a
> server and client using POE::IKC::Client and POE::IKC::Server, and it
> works ok. However, I also need:
>
> Server authentication - I want the client to be sure they've connected
> to the right server.
> Client authentication - I want the server to know who's connecting
> (login/password), and treat them differently depending on who they
> are.
>
> I'm not sure POE::IKC is the way to go, but it seems pretty easy so I
> started there. Any suggestions as to which modules to use would be
> very welcome. I've looked at POE::Component::SSLify but can't see how
> to combine that with POE::IKC, and it looks like it only uses SSL as a
> transport layer, rather than for authentication etc.
>
> Thanks in advance.
>