surely, this does not deliver application level security, but this should anyway (IMHO) be implemented clearly on top of zmq (well, there could be some (also ontop) libs helping zmq-apps to do so).
^5
Sven
---------------------------------------------------------
E = mc² ± 2dBA ----- everything is relative
---------------------------------------------------------
-----Original Message-----
Date: Thu, 18 Nov 2010 11:04:26 +0100
Subject: Re: [zeromq-dev] More security thoughts
From: Pieter Hintjens <[email protected]>
To: ZeroMQ development list <[email protected]>
On Thu, Nov 18, 2010 at 9:07 AM, Martin Sustrik <[email protected]> wrote:
> Right. And both actually boil down to the same model:
>
> Application-thread <-> Encryption(device)-thread <-> I/O-thread
>
> You can even think of running several encryption threads in parallel
> (parallelised pipeline a.k.a. PUSH/PULL).
Hmm, doing that in parallel would mean that messages would end up out
of order unless you resynchronize them.
A generic security device would be cool but possibly quite hard to
design, since it'd need to support multiple socket patterns.
-Pieter
_______________________________________________
zeromq-dev mailing list
[email protected]
http://lists.zeromq.org/mailman/listinfo/zeromq-dev
_______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
