https://bugs.winehq.org/show_bug.cgi?id=39264
Jacek Caban jacek@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED CC| |jacek@codeweavers.com Resolution|--- |INVALID
--- Comment #6 from Jacek Caban jacek@codeweavers.com ---
This means after reading a maximum of (conn->ssl_sizes.cbHeader+conn->ssl_sizes.cbMaximumMessage+conn->ssl_sizes. cbTrailer) bytes, the implementation should be able to tell if its a correct message (SEC_E_OK) or if an error occurred, but definitely shouldn't return SEC_E_INCOMPLETE_MESSAGE anymore.
Agreed, it's even documented by the assert. DecryptMessage should definitely be able to decrypt buffered data in this case. I'd suggest to take another look and try to fix it in ReactOS schannel.dll implementation.