Since SASL authentication data is all base64 encoded, don't expect more than one argument to AUTHENTICATE
Properly parse incoming SASL when the incoming data is really long
Use primes of a length better suited for more general purposes
Don't make the mechanism look for the first "parameter" anymore (since it's now just the first character in the mechanism name)
Implement the DH-AES mechanism for SASL in DB services
Make the SASL module itself handle packet lengths instead of passing that off to the agent so that it can be done right every time instead of correctness being implementation-dependent
Merge pull request #152 from ElementalAlchemist/sasl-fixes

SASL fixes - parsing and the DH-AES mechanism