7 Commits

Author	SHA1	Message	Date
Jeremy Rossi	19ca8a0fc0	Add the Socket Identity info to the ZAP Messages ... 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.	2013-08-20 13:48:05 -04:00
Richard Newton	a83baa9b0b	Fix up threading code from port tests to windows.	2013-08-17 14:23:22 +01:00
Richard Newton	7f74fc7c99	Port tests to windows and add to cmake build.	2013-08-17 13:43:45 +01:00
Martin Hurton	d65231be1c	Update CURVE mechanism to the latest ZAP revision	2013-07-18 10:59:31 +02:00
Pieter Hintjens	7041770108	Added Z85 support ... The use of binary for CURVE keys is painful; you cannot easily copy these in e.g. email, or use them directly in source code. There are various encoding possibilities. Base16 and Base64 are not optimal. Ascii85 is not safe for source (it generates quotes and escapes). So, I've designed a new Base85 encoding, Z85, which is safe to use in code and elsewhere, and I've modified libzmq to use this where it also uses binary keys (in get/setsockopt). Very simply, if you use a 32-byte value, it's Base256 (binary), and if you use a 40-byte value, it's Base85 (Z85). I've put the Z85 codec into z85_codec.hpp, it's not elegant C++ but it is minimal and it works. Feel free to rewrap as a real class if this annoys you.	2013-06-28 22:10:22 +02:00
Pieter Hintjens	7832addd20	Updated security mechanisms to use variable-length commands ... RFC23, RFC24, RFC26 now use variable-length command names that end in null octet (valid C strings) instead of fixed-length space padded strings.	2013-06-28 11:42:54 +02:00
Ian Barber	211bf2b08e	Added security curve test ... Test is skipped if no libsodium. Added warning if libsodium not configured	2013-06-22 16:17:25 +01:00