1. 14 May, 2014 3 commits
  2. 12 May, 2014 1 commit
  3. 06 May, 2014 1 commit
  4. 05 May, 2014 1 commit
  5. 02 May, 2014 1 commit
  6. 01 May, 2014 1 commit
  7. 29 Apr, 2014 1 commit
  8. 12 Jan, 2014 1 commit
  9. 02 Jan, 2014 1 commit
  10. 09 Sep, 2013 1 commit
    • Pieter Hintjens's avatar
      Added ZMQ_ZAP_DOMAIN socket option · 6725c464
      Pieter Hintjens authored
      * This is passed to the ZAP handler in the 'domain' field
      
      * If not set, or empty, then NULL security does not call the ZAP handler
      
      * This resolves the phantom ZAP request syndrome seen with sockets where
        security was never intended (e.g. in test cases)
      
      * This means if you install a ZAP handler, it will not get any requests
        for new connections until you take some explicit action, which can be
        setting a username/password for PLAIN, a key for CURVE, or the domain
        for NULL.
      6725c464
  11. 04 Sep, 2013 1 commit
    • Pieter Hintjens's avatar
      Updated libzmq to match RFC 23, 24, 25, 26 · 28b0a5fa
      Pieter Hintjens authored
      * Command names changed from null terminated to length-specified
      * Command frames use the correct flag (bit 2)
      * test_stream acts as test case for command frames
      * Some code cleanups
      28b0a5fa
  12. 02 Sep, 2013 2 commits
    • Pieter Hintjens's avatar
      Fixed ZAP authentication · fb67e160
      Pieter Hintjens authored
      - if ZAP server returns anything except 200, connection is closed
      - all security tests now pass correctly
      - test_security_curve now does proper client key authentication using test key
      - test_security_plain now does proper password authentication
      fb67e160
    • Pieter Hintjens's avatar
      Fixed 'make check' failures · fba56120
      Pieter Hintjens authored
      - Split off NULL security check from PLAIN
      - Cleaned up test_linger code a little
      - Got all tests to pass, added TODOs for outstanding issues
      - Added ZAP authentication for NULL test case
      - NULL mechanism was not passing server identity - fixed
      - cleaned up test_security_plain and removed option double-checks (made code ugly)
      - lowered timeout on expect_bounce_fail to 150 msec to speed up checks
      - removed all sleeps from test_fork and simplified code (it still passes :-)
      fba56120
  13. 20 Aug, 2013 1 commit
    • Jeremy Rossi's avatar
      Add the Socket Identity info to the ZAP Messages · 19ca8a0f
      Jeremy Rossi authored
      This change adds the socket identity infomartion from the socket to the
      zap frames.  In doing this the ZAP is able preform different operations
      based on different sockets.  This is not compaitable with the current ZAP
      RFC, but that can be updated.  As the ZAP rfc is currently draft for I
      did not change the version number.
      
      Tests also modified and passing.
      19ca8a0f
  14. 18 Jul, 2013 1 commit
  15. 01 Jul, 2013 1 commit
  16. 28 Jun, 2013 1 commit
  17. 23 Jun, 2013 1 commit
  18. 22 Jun, 2013 3 commits
  19. 07 Jun, 2013 1 commit
  20. 06 Jun, 2013 2 commits
  21. 18 May, 2013 1 commit
  22. 17 May, 2013 2 commits
  23. 14 May, 2013 1 commit
    • Martin Hurton's avatar
      Implement ZMTP/3.0 PLAIN mechanism · 4eecda8a
      Martin Hurton authored
      This implements protocol handshake.
      We still need to design and implement 1) API changes so a user
      can set username and password, and 2) a mechanism for engine
      to authenticate users.
      4eecda8a