Swiftdiff options
| author | Mili Verma <mili.verma@isode.com> | 2015-06-22 13:06:58 (GMT) |
|---|---|---|
| committer | Kevin Smith <kevin.smith@isode.com> | 2015-06-30 07:06:06 (GMT) |
| commit | a3564b7aca44f5ccab3881e6f723dfb64bf66884 (patch) | |
| tree | b92c151a77842d521615c9c5e9b5a4bfb70ea477 /Swiften/Examples/BenchTool | |
| parent | 394642c69bc232429621e209b787d3496967b37b (diff) | |
| download | swift-a3564b7aca44f5ccab3881e6f723dfb64bf66884.zip swift-a3564b7aca44f5ccab3881e6f723dfb64bf66884.tar.bz2 | |
Remove when sending an empty response
In RFC 6120, there are only 2 places where "=" is allowed - in the initial
client auth and in the final server success response.
While testing challenge response exchanges in Kerberos, it was seen that Swift
was adding an '=' in other empty responses. This patch fixes it by sending an
empty response instead of an '='.
Test-information:
Tested on Windows using a WIP GSSAPI authentication exchange with M-Link.
Change-Id: I1f82bddbd1380361cbe43e45a2804156249582ae
Diffstat (limited to 'Swiften/Examples/BenchTool')
0 files changed, 0 insertions, 0 deletions