Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Several fixes #1

Merged
merged 1 commit into from
May 10, 2016
Merged

Several fixes #1

merged 1 commit into from
May 10, 2016

Conversation

brson
Copy link

@brson brson commented May 10, 2016

When there's data already buffered at entry to read just return it.
Simple and correct. Maybe doesn't fix real bugs.

If the previous DecryptMessage resulted in SECBUFFER_DATA then
just run that data through DecryptMessage again before calling
read on the socket. This prevents read timeouts.

Add a 5th SecBuffer to the DecryptMessage calls, per MSDN.

Handle DecryptMessage errors.

When there's data already buffered at entry to `read` just return it.
Simple and correct. Maybe doesn't fix real bugs.

If the previous DecryptMessage resulted in SECBUFFER_DATA then
just run that data through DecryptMessage again before calling
read on the socket. This prevents read timeouts.

Add a 5th SecBuffer to the DecryptMessage calls, per MSDN.

Handle DecryptMessage errors.
@brson
Copy link
Author

brson commented May 10, 2016

There are definitely more problems here, but this gets rid of the hanging.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants