Radek Zikmund
Radek Zikmund
[TestFailure] System.Net.Security.Tests.CertificateValidationRemoteServer.DefaultConnect_EndToEnd_Ok
Link to test in AzDO: https://dev.azure.com/dnceng-public/public/_build/results?buildId=519054&view=ms.vss-test-web.build-test-results-tab&runId=12192474&resultId=176645&paneView=debug
[TestFailure] System.Net.Security.Tests.CertificateValidationRemoteServer.DefaultConnect_EndToEnd_Ok
Triage/reporting blocked by https://github.com/dotnet/runtime/issues/96035
[TestFailure] System.Net.Security.Tests.CertificateValidationRemoteServer.DefaultConnect_EndToEnd_Ok
This issue was filed for issues occuring on windows, but I don't see any recent hits on that OS. So this is no longer actionable. I will close this and...
I tried to find what RFC says about changing the certificate during connection, while I did not find anything specifically forbidding it, I have some notes: - in TLS 1.3,...
After reading the entire discussion, it seems to me that you are perceiving there is a problem which, in fact, is not there (the reasoning was IMO sufficiently explained by...
SslStream does support PHA and renegotiation, but you can't currently change the certificate once it is set (I think even the certificate selection callback option will cache the first returned...
I should probably start with this: I **strongly suggest** you avoid trying to implement a custom "better" secure protocol. These things are hard to get right and existing protocols are...
Reopening for CI monitoring.
@mikelle-rogers the test was disabled on February 14th, all the failures from the table above are older than that.
looks like https://github.com/dotnet/runtime/pull/97979 did not help, I will look into it