Hi folks,
I’m writing a package
That I want to distribute with setuptools
That requires pyzmq
…to be built with libsodium
I’m wondering what is the best way to achieve this. If I simply declare in my
setup.py
> install_requires=['pyzmq>=14.0.1’]
This creates a dependency on pyzmq, however it
to solve the issue immediately.
>
> Actually, most issues don't require immediate attention most of time.
>
> On Fri, Feb 21, 2014 at 10:36 PM, Drew Crawford
> wrote:
>> I'm not sure I understand your question, crocket. Are you asking why this
>> issue has
I’m not sure I understand your question, crocket. Are you asking why this
issue has stalled for so long? Or are you asking how to do things at your day
job so that they stall at least as long as this #802? ;-)
On Feb 21, 2014, at 7:01 AM, crocket wrote:
> terms -> in terms
>
> On Feb 21,
I’ve edited the page. Thanks!
On Feb 20, 2014, at 2:04 PM, Sean Robertson wrote:
> http://zeromq.org/build:iphone might be a good place
>
> On Thu, Feb 20, 2014 at 5:24 AM, Drew Crawford
> wrote:
>> Certainly. I'm not entirely sure where the logical place to put th
Certainly. I’m not entirely sure where the logical place to put the
information would be.
On Feb 20, 2014, at 7:22 AM, Pieter Hintjens wrote:
> Drew,
>
> It'd be great to get that info onto the wiki, is that possible do you think?
>
> -Pieter
>
> On Thu, Feb
https://github.com/drewcrawford/libzmq-ios/releases
On Feb 20, 2014, at 1:08 AM, Pankaj Dhiman wrote:
> Hi Gents,
>
> i tried a bit but not able to build zmq for iOS on XCode 5+ (iOS 6 - 7)
> i m getting linker errors
>
> so please send me steps to build zmq client for iOS.
>
>
> --
> Th
. The client
is just reconnecting over and over to the server, wasting server resources,
only to be rejected and immediately reconnect. The libzmq client should report
some kind of useful error and give up in this case.
On Feb 14, 2014, at 8:20 AM, Drew Crawford wrote:
> It returns 0, whic
It returns 0, which I think is the pass condition. Good idea though, I
wouldn’t have thought of that.
On Feb 14, 2014, at 7:51 AM, Laurent Alebarde wrote:
> Does the selftest test_security_curve pass ?
>
> Le 14/02/2014 14:39, Drew Crawford a écrit :
>> Hello folks,
>>
Hello folks,
For some reason, a message sent from the REQ side of a REQ/ROUTER isn’t
arriving. I know from experience this is some kind of CURVE issue, but I have
stared at my curve usage for several hours now without seeing the problem. I’m
hoping to collect some general strategies on how to
, Jan 1, 2014 at 10:19 PM, Pieter Hintjens wrote:
>> There's no issue open for this. Feel free to create one (we use the
>> github issue tracker now). I'll start by changing ZAP to provide the
>> client id.
>>
>> On Wed, Jan 1, 2014 at 9:04 PM, Drew Crawford
&g
;
> On Wed, Jan 1, 2014 at 1:12 PM, Drew Crawford wrote:
>
>>> 2. we publish all ZAP replies to a secondary inproc:// socket (PUB-SUB)
>>
>> This also seems curious. I’m wondering if you’re envisioning a more
>> complicated ZAP handler in some faraway modul
;>
>>
>>
>> On Wed, Jan 1, 2014 at 12:28 PM, Pieter Hintjens wrote:
>>> The ZAP handler gets the identity of the client (along with all
>>> metadata) and can validate it. So you can use client identity + public
>>> key authentication, and then e
n use client identity + public
> key authentication, and then each message will report the
> authenticated sender.
>
> On Tue, Dec 31, 2013 at 7:08 PM, Drew Crawford
> wrote:
>> I think I can supply a patch that is at least good enough to get cleaned up
>> and merged b
woodwork and identify which solution is the one that should be tried.
Drew
On Dec 31, 2013, at 11:51 AM, Nicolas Delaby wrote:
> On 12/31/2013 06:30 PM, Drew Crawford wrote:
>> Hi Nicolas,
>>
>> I’m reasonably sure we have the same problem, and I’ve gotten somewhat
>> furth
Hi Nicolas,
I’m reasonably sure we have the same problem, and I’ve gotten somewhat further
along without solving it. We may want to compare notes. Take a look at my
thread "How do I find out which ZAP user I'm talking to?”.
Drew
On Dec 31, 2013, at 6:27 AM, Nicolas Delaby wrote:
>
>
> Le
pick their own keypair, so unless you have the public key
> then it's moot. If the client claims to be billgates and signs their message
> (and you have their pubkey) then they're authenticated, no?
>
>
>
>
>
> On Tuesday, December 31, 2013 7:01 AM, Drew Crawford
>
wn custom identity if they have unique names.
>
>
>
>
>
> On Tuesday, December 31, 2013 6:51 AM, Drew Crawford
> wrote:
> Hey folks,
>
> I’ve got a REQ-ROUTER architecture where clients (with a REP socket) connect
> to a server (with a ROUTER socket). Thi
Hey folks,
I’ve got a REQ-ROUTER architecture where clients (with a REP socket) connect to
a server (with a ROUTER socket). This connection is authenticated via CURVE.
I need to figure out some person/username/unique identifier that is associated
with the incoming REQ. There are a couple of r
18 matches
Mail list logo
