-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Added missing *Async overrides to TlsStream #91750
Conversation
Tagging subscribers to this area: @dotnet/ncl Issue Details#82644 replaced custom IAsyncResult with call to I added Note that we do not have any coverage for SSL enabled SMTP. So in order to add tests for this, I'll need add support for SSL into Fixes #91377
|
Ouch, sorry about that. Thanks for tracking it down. |
Agreed, let's push the fix into 8.0 with manual validation. And let's file a tracking issue to add the automated tests during 9.0 - we can then prioritize it appropriately against other work items we will have based on cost, value and risk we impose if we do not have the automation. |
Build error is #91705 |
/backport to release/8.0 |
Started backporting to release/8.0: https://github.com/dotnet/runtime/actions/runs/6122263567 |
this looks like major test gap. We should look into it IMHO. I know @filipnavara had more insight to additional test gaps. |
#82644 replaced custom IAsyncResult with call to
ReadAsync
onBufferedReadStream
. ButTlsStream
doesn't haveReadAsync
and the call went to the base classNetworkStream.ReadAsync
effectively bypassingSslStream.Decrypt
of the data.I added
Read/WriteAsync
overrides to call into_sslStream
as is expected.Note that we do not have any coverage for SSL enabled SMTP. So in order to add tests for this, I'll need add support for SSL into
LoopbackSmtpServer
. @karelz this might take some time, so let me know, if you want to move forward with this fix with just local validation and do the test afterwards.Fixes #91377