Hello,
I managed to get a CZMQ dll under windows. That fine so far. Actually I
am not doing "C", but bind it to a smalltalk dialect. Now the problem
when using (for example): zstr_recv().
It is said that the caller must free the receiving string, but how is
this done, when you only have a high
Hello,
rather than writing a binding under Windows against low-level libzmq I
now consider doing the work against czmq. But is there a precompiled dll
available. I tried to do this by myself, but I rather get messed up with
all that linking and compiling errors (pointer conversions) ... actuall
Hi Laurent,
No problem with taking the security concerns to CurveCP. I just want to
note that the 'MAY' part of authenticating C indicates a per application
decision. Some applications - like yours - require authentication of
clients, others do not (e.g. an anonymous, but securely encrypted
filese
On Sun, Aug 18, 2013 at 5:26 PM, Laurent Alebarde wrote:
> Hi Pieter,
>
> You are right. That makes sense. BTW, I suppose you wanted to write :
> "it's wise that CurveZMQ track CurveCP as close as possible".
>
English is *such* a ridiculous language!
I double-checked with my wife, who's into th
Greetings all,
I am a third year student at the Auckland University of Technology. Me and
my fellow team mate, Rafsan Siraj, for our final year project, are going to
be working on adding support for SCTP to ØMQ. We are currently in the
planning/research stages, so we don't have much to report so f
On Sun, Aug 18, 2013 at 5:32 PM, Lucas Hope wrote:
> Hi James,
>
> On Mon, Aug 19, 2013 at 3:30 AM, James Gatannah
> wrote:
>
>>
>> It is very edifying to hear that. Users and pull requests are welcome.
> Though I hope the binding isn't too buggy!! Anyway, please let me know your
> experiences.
I'm a maintainer for JZMQ and more recently, my company donated Clojure
bindings to the community: https://github.com/zeromq/cljzmq
-Trev
On Sun, Aug 18, 2013 at 7:32 PM, Lucas Hope wrote:
> Hi James,
>
> On Mon, Aug 19, 2013 at 3:30 AM, James Gatannah
> wrote:
>
>> This is awesome! Thank you
Hi Luke,
Thank you very much for your remarks. Some comments below. As Pieter
rightly suggested it, let's go on with the CurveCP mailing list as of now.
Cheers,
Laurent.
Le 18/08/2013 23:43, Lucas Hope a écrit :
Hi Laurent,
I had a think about this, and there are a couple of issues with
Hi James,
On Mon, Aug 19, 2013 at 3:30 AM, James Gatannah wrote:
> This is awesome! Thank you for taking it off my plate.
>
> I have this on my "most urgent...but not quite yet" todo list. So I'll
> probably start pinging you with issues/pull requests in about 2 weeks (OK,
> that's optimistic).
>
Hi Pieter,
You are right. That makes sense. BTW, I suppose you wanted to write :
"it's wise that CurveZMQ track CurveCP as close as possible".
Cheers,
Laurent.
Le 18/08/2013 19:09, Pieter Hintjens a écrit :
Laurent,
I think it's wise that CurveZMQ track CurveCP as far as possible,
changing
Hi Pieter.
Nice stuff! If you want to update the CL examples in the Guide to use
> this, that'll make it 'the' binding.
>
Thank you.
I want to get through Chapter 3 of the examples first - that's where they
go from 'toy' to 'science experiment'. It also means the coverage with this
binding will
Hi Laurent,
I had a think about this, and there are a couple of issues with the logic.
If there is a vulnerability where you suggest, then that vulnerability
would render the whole encryption scheme useless. I guess what I‘m saying
is that you’ve found an incredibly huge leak, or it isn‘t a leak a
This is awesome! Thank you for taking it off my plate.
I have this on my "most urgent...but not quite yet" todo list. So I'll
probably start pinging you with issues/pull requests in about 2 weeks (OK,
that's optimistic).
Between you and Trevor Bernard, my life just got at least 100x easier.
Thank
Laurent,
I think it's wise that CurveZMQ track CurveCP as far as possible,
changing only when it's clearly appropriate to the TCP transport
(CurveCP being designed for UDP). This means any weakness in CurveZMQ
should be matched by CurveCP, and the discussion can be done there.
Would you raise thi
Hi all,
Studying CurveZMQ, CurveCP, libsodium and NaCl, I find it good to
discuss possible weaknesses on the protocol, especially the Hello packet :
Notation, I use the modified notation (C',0,Box[0'](c'->S)) instead of
(C',0,Box[0'](C'->S)) from the original
(http://curvecp.org/packets.html
On Thu, Aug 15, 2013 at 4:52 PM, Michael Keselman
wrote:
> At the moment I solved the problem by implementing a connection pool with a
> number of connected sockets.
Sounds fair; you just want to make sure there is a full memory barrier
when switching sockets between threads. (I've no idea how t
Uli,
If you can find the change that fixed this, we can backport it to
3.2.x. Otherwise, my plan is to make a 4.0 unstable release in
September.
-Pieter
On Sun, Aug 18, 2013 at 4:04 AM, Uli Köhler
wrote:
> Hi,
> just a quick followup on this.
>
> By using the current libzmq trunk with CZMQ 1.4.
Lucas,
Nice stuff! If you want to update the CL examples in the Guide to use
this, that'll make it 'the' binding.
-Pieter
On Sat, Aug 17, 2013 at 3:07 AM, Lucas Hope wrote:
> Hi all,
>
> I decided my new binding for common-lisp, cl-czmq is complete enough to be
> released.
>
> Here it is: https
Thanks for this analysis. I'll look at it when I have an hour or two;
it's too tricky to fix in passing.
On Thu, Aug 15, 2013 at 12:30 PM, Laurent Alebarde wrote:
> Hi all,
>
> I am reviewing the curvezmq code with a debugger :
>
> Fact :
> in curvezmq_codec.c (s_encrypt from s_produce_hello, lin
Hi Guys,
In my application I'm using push\pull sockets with ZMQ_HWM option calling the
non-blocking send API.
When we first evaluated ZMQ we noticed that in high QPS the send operation is
sometimes returning EAGAIN error code and I read it usually means that we need
to retry so we implemented a
Hi Laurent,
Thanks for that! It seemed relatively straightforward, except for the magic
functions and their properties which I just took as given. I don't quite
have the background for that.
The examples in code were nice, but it did take a fair bit of re-reading to
work out why things were being
21 matches
Mail list logo
