Fix XMPPAuthenticator to support non-optimized message flow

While RFC6120 allows and encourages sending data with the success
message it is also legal to send the same data as a challenge and
await an empty response. This rework honors that fact.
This commit is contained in:
Florian Zeitz 2011-09-18 21:33:19 +02:00
parent 64f131641f
commit 74727c159c
6 changed files with 83 additions and 69 deletions

View file

@ -36,6 +36,7 @@
OFDataArray *serverSignature;
XMPPConnection *connection;
BOOL plusAvailable;
BOOL authenticated;
}
/**
@ -114,4 +115,6 @@
- (OFDataArray*)XMPP_hiWithData: (OFDataArray *)str
salt: (OFDataArray *)salt_
iterationCount: (intmax_t)i;
- (OFDataArray*)XMPP_parseServerFirstMessage: (OFDataArray*)data;
- (OFDataArray*)XMPP_parseServerFinalMessage: (OFDataArray*)data;
@end