Martin Hurton
53bc53da04
Update PLAIN mechanism to the latest ZAP revision
2013-07-18 10:59:34 +02:00
Martin Hurton
783bb890a9
Check socket types during mechanism handshake
2013-07-01 10:12:08 +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
Martin Hurton
b12be41736
Rename parse_properties to parse_metadata
2013-06-23 09:01:52 +02:00
Martin Hurton
99d4974580
Refactor how properties are parsed
2013-06-22 19:02:08 +02:00
Martin Hurton
fa0f0e21b8
Make ZAP optional for PLAIN mechanism
2013-06-22 16:05:46 +02:00
Martin Hurton
20a7978d67
Stop ZMTP handshake when an unexpected message comes
2013-06-22 08:12:11 +02:00
Pieter Hintjens
6ff51ee909
Updated ZAP request for changed protocol draft
...
- username and password sent as two string frames
- fixed test case to match
2013-06-07 15:50:36 +02:00
Martin Hurton
2928c91a6d
Implement ZAP and integrate it with PLAIN mechanism
2013-06-06 13:28:21 +02:00
Martin Hurton
4e47084dd4
Minor cleanups
2013-06-06 13:28:21 +02:00
Pieter Hintjens
73562112b8
Whitespace fixes
2013-05-18 11:53:20 +01:00
Pieter Hintjens
f909b9c722
plain_mechanism now uses options.as_server
...
- we need to switch to PLAIN according to options.mechanism
- we need to catch case when both peers are as-server (or neither is)
- and to use username/password from options, for client
2013-05-17 17:21:59 +01:00
Martin Hurton
182a224bb0
Use socket options to select security mechanism
2013-05-17 15:49:59 +02:00
Martin Hurton
4eecda8af3
Implement ZMTP/3.0 PLAIN mechanism
...
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.
2013-05-14 11:20:13 +02:00
