Hi all,
First, the obligatory note of thanks to Pieter and the 0MQ community for such a
beautiful artefact. I have finally managed to engineer an opportunity to use
0MQ at work and am enjoying it immensely!
On to business: I think I'm experiencing this issue (or at least a close
relation),
Apologies, forgot to include details of my config:
0MQ 4.0.4, CZMQ 2.1.0
OpenSUSE 13.1 x86_64 (Linux 3.11.10-7)
HP ProBook 440 Notebook, Intel Core i7
-Original Message-
From: zeromq-dev-boun...@lists.zeromq.org
[mailto:zeromq-dev-boun...@lists.zeromq.org] On Behalf Of Procter, Stephen
I don't know CURVE well, but in general, key management is a hard problem.
Usually encryption assumes keys have been pre-distributed somehow, and
they are almost never baked into an executable (that isn't secure).
Take ssh, for instance. The common use-case is to run ssh-keygen, and then
put your
Fabien VITIELLO
Ingénieur logiciels embarqués / Embedded Software Engineer
ESG France SAS
Centre Paris Pleyel, 153 Bd Anatole France
93521 Saint Denis Cedex
Tél : +33 1 55 87 05 70
Fax : +33 1 55 87 05 79
E-mail : fabien.vitie...@esg-group.frmailto:fabien.vitie...@esg-group.fr
keys have been pre-distributed somehow may be performed with use of
the Diffie--Hellman key exchange algorithm:
http://en.wikipedia.org/wiki/Diffie%E2%80%93Hellman_key_exchange
Le 03/04/2014 10:23, Lindley French a écrit :
I don't know CURVE well, but in general, key management is a hard
Thanks for the clear test case.
I've found the problem, which is a mix of poor documentation and poor
code. The zmq_sendmsg man page doesn't really explain what to do in
case of an error. However if the message can't be sent, then the
caller must free it. CZMQ doesn't do that.
It works for very
Hi Steve,
Sorry that there are loose ends. It's a massive project and at about
80% I had to go back to paying work.
zauth, zcert, and zcertstore form a package, you can understand, use,
and improve them together. They implement a specific ZAP handler
design based on simple text encoded
Hi all,
I am experiencing problem with message delivery from Dealer (as client) to
Router (as server).
Dealer and Router are configured to use Curve.
I am using ZMQ 4.0.3. Server is running on Centos x64. Client is running on
Windows 7.
Usually everything works OK. But eventually one client
Pieter,
Unfortunately I can't do that right now. Problem occurred in public
environment. It is used for demo purposes and there are some testers online. I
have access to problem client and I can hack it. I can add some traces on
server side and restart it. But I have to preserve protocol.
Our
Pieter, Laurent, Lindley--
Many thanks for the responses.
Laurent's mention of secure public key exchange got me thinking.
=== A Quick Trip to a Perfect World?
As to the global, high-level view of this curve stuff,
What If:
A. Every Server and Every Client creates a brand-new, fresh zcert
Hi Carlos,
You could also have a look at https://github.com/lhope/cl-czmq which wraps
or - when wrapping is impractical - re-implements czmq (the c binding for
ZMQ) rather than ZMQ itself.
It is a bit out of date, but may be still usable with later versions of
zmq+czmq. If you post issues or
Dear All ...
I read :
1. http://zguide.zeromq.org/page:all#Transport-Bridging
2. http://zguide.zeromq.org/py:wuproxy
My Case :
i. Publishers at 192.168.55.x send messages each second
ii. Un-reliable network
My question is : what will happend to the Published messages when
connection between
12 matches
Mail list logo
