Uh oh!
There was an error while loading. Please reload this page.
[QUIC] Cleaned up TlsSecret and added test. - #93119
Conversation
ghost
commented
Oct 6, 2023
Tagging subscribers to this area: @dotnet/ncl Issue DetailsAdded test for SSLKEYLOGFILE, fixed missing writing of the secret and removed direct reference from safe handle (now held by IDisposable).
|
ghost
commented
Oct 6, 2023
Tagging subscribers to this area: @dotnet/ncl Issue DetailsAdded test for SSLKEYLOGFILE, fixed missing writing of the secret and removed direct reference from safe handle (now held by IDisposable).
|
Uh oh!
There was an error while loading. Please reload this page.
| if (_tlsSecrets is not null) | ||
| { | ||
| NativeMemory.Clear(_tlsSecrets, (nuint)sizeof(QUIC_TLS_SECRETS)); | ||
| NativeMemory.Free(_tlsSecrets); |
There was a problem hiding this comment.
I'm not sure this is safe. It feels like we can free the memory while MsQuic still may be trying to write to that. That was one reason why originally the native memory was tight to the MsQuic handle lifecycle.
There was a problem hiding this comment.
The dispose is called when the connection handle gets released, not from QuicConnection.DisposeAsync.
c131283 to
58851d5Compare58851d5 to
51a5be4Compare
Added test for SSLKEYLOGFILE, fixed missing writing of the secret and removed direct reference from safe handle (now held by IDisposable).