Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Commits on Jan 29, 2015
Commits on Jan 28, 2015
  1. quick bump to 2.0.4

    authored
Commits on Feb 26, 2014
  1. fix merge conflicts

    authored
Commits on Feb 12, 2014
  1. Merge pull request #108 from deployable/master

    authored
    Update examples for v3.2 or v4 in README.rdoc
Commits on Feb 5, 2014
Commits on Jan 22, 2014
  1. @jasonroelofs

    Bump version to 2.0.1

    jasonroelofs authored
Commits on Jan 20, 2014
  1. @jasonroelofs
  2. @jasonroelofs

    Expose the LibZMQ::zmq_curve_keypair utility method

    jasonroelofs authored
    This method returns a Z85 encoded public and private key pair to be used
    in CURVE security setups.
  3. @jasonroelofs

    Let ruby-ffi handle String pointer parameters itself

    jasonroelofs authored
    ZeroMQ's new security constructs, specifically CURVE key management, is very
    explicit about what strings it will accept (keys MUST be a 32 byte long binary
    key or a 40 byte long Z85 encoded key with NULL terminiator). Whereas this code
    seems to have worked for a very long time, it was allocating byte buffers that
    weren't quite right for the CURVE settings and meant any attempt to use CURVE
    would simply fail with no visible reason (The server's private/public keys in
    the initial handshake didn't agree and the client was dropped).
    
    When I dropped down to the raw ffi-rzmq-core calls to set up CURVE
    authentication, communication proceeded perfectly. I realized that given a line
    like this:
    
        LibZMQ::zmq_setsockopt(socket, ::ZMQ::CURVE_SECRETKEY,
          SERVER_PRIVATE_KEY, SERVER_PRIVATE_KEY.length)
    
    where SERVER_PRIVATE_KEY is just a 40-character string, that we don't
    need to allocate any new data for passing string values into FFI. Once I
    made this change and re-ran my code with ffi-rzmq calls, everything
    worked perfectly.
    
    This change is unfortunately quite difficult to build an automated test
    around, so instead I'll add an example showing off the CURVE
    communication options, and as long as that's running then this feature
    still works.
Commits on Jan 11, 2014
  1. @deployable
Commits on Jan 8, 2014
  1. prepare for 2.0 release

    authored
Commits on Dec 20, 2013
  1. Merge pull request #105 from schmurfy/msg_fix

    authored
    match changes in ffi-rzmq-core
  2. @schmurfy
Commits on Dec 6, 2013
  1. Merge pull request #104 from mzaccari/socket-doc-fixes

    authored
    Minor documentation fixes for ZMQ::Util.errno
  2. @mzaccari
Commits on Nov 14, 2013
  1. update path to library

    authored
  2. update rubinius target

    authored
  3. depend on ffi-rzmq-core

    authored
  4. misc fixups

    authored
Commits on Nov 12, 2013
  1. Merge branch 'master' of github.com:chuckremes/ffi-rzmq into v2

    authored
    Conflicts:
    	History.txt
    	ffi-rzmq.gemspec
    	lib/ffi-rzmq/constants.rb
    	lib/ffi-rzmq/context.rb
    	lib/ffi-rzmq/libc.rb
    	lib/ffi-rzmq/libzmq.rb
    	lib/ffi-rzmq/message.rb
    	lib/ffi-rzmq/socket.rb
    	lib/ffi-rzmq/util.rb
    	lib/ffi-rzmq/version.rb
Commits on Nov 6, 2013
  1. Merge pull request #100 from stakach/master

    authored
    Improve FFI syntax and readability
Commits on Nov 4, 2013
  1. Improve FFI syntax and readability

    Stephen von Takach authored
Commits on Oct 17, 2013
  1. @minrk

    Merge pull request #99 from devin-c/master

    minrk authored
    Make sure the API gets loaded for version 4
Something went wrong with that request. Please try again.