Make MaxMsgLen into a configurable parameter.
* Yes, this violates the spec. The limitation is arbitrary and lifiting it allows us to skip a lot of complexity in our use of the protocol. * Yes, the upstream code only enforces this for handshake messages, so I could have skipped doing this, but I may as well be explicit in what I'm doing. Ideally CipherState.Encrypt()/Decrypt() will enforce this as well, but it's not my library and I see myself rewriting it at some point anyway.
Showing with 13 additions and 4 deletions