Bug 60410 - [New Web Stack][Need-Triage] Error: SecureChannelFailure in NuGet.
Summary: [New Web Stack][Need-Triage] Error: SecureChannelFailure in NuGet.
Status: NEW
Alias: None
Product: Class Libraries
Classification: Mono
Component: Mono.Security ()
Version: 5.2 (2017-04)
Hardware: PC Linux
: Normal normal
Target Milestone: Untriaged
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2017-10-27 08:49 UTC by Mikhail Filippov
Modified: 2017-12-11 20:16 UTC (History)
4 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report for Bug 60410 on GitHub or Developer Community if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: GitHub Markdown or Developer Community HTML
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:
Status:
NEW

Description Mikhail Filippov 2017-10-27 08:49:29 UTC
We have the flaky problem in when using NuGet API it's problem happened only Linux OS:

Failed to download package 'Microsoft.Extensions.Caching.SqlServer.2.0.0' from 'https://api.nuget.org/v3-flatcontainer/microsoft.extensions.caching.sqlserver/2.0.0/microsoft.extensions.caching.sqlserver.2.0.0.nupkg'.
An error occurred while sending the request
  Error: SecureChannelFailure (The authentication or decryption has failed.)
  The authentication or decryption has failed.
  Error while sending TLS Alert (Fatal:InternalError): System.IO.IOException: Unable to write data to the transport connection: Cannot access a disposed object.
  Object name: 'System.Net.Sockets.Socket'.. ---> System.ObjectDisposedException: Cannot access a disposed object.
  Object name: 'System.Net.Sockets.Socket'.
    at System.Net.Sockets.Socket.ThrowIfDisposedAndClosed () [0x0001b] in <53e34a2ab1804f7fa3447cf99d35bb55>:0 
    at System.Net.Sockets.Socket.BeginSend (System.Byte[] buffer, System.Int32 offset, System.Int32 size, System.Net.Sockets.SocketFlags socketFlags, System.Net.Sockets.SocketError& errorCode, System.AsyncCallback callback, System.Object state) [0x00000] in <53e34a2ab1804f7fa3447cf99d35bb55>:0 
    at System.Net.Sockets.Socket.BeginSend (System.Byte[] buffer, System.Int32 offset, System.Int32 size, System.Net.Sockets.SocketFlags socketFlags, System.AsyncCallback callback, System.Object state) [0x00000] in <53e34a2ab1804f7fa3447cf99d35bb55>:0 
    at System.Net.Sockets.NetworkStream.BeginWrite (System.Byte[] buffer, System.Int32 offset, System.Int32 size, System.AsyncCallback callback, System.Object state) [0x0009b] in <53e34a2ab1804f7fa3447cf99d35bb55>:0 
     --- End of inner exception stack trace ---
    at System.Net.Sockets.NetworkStream.BeginWrite (System.Byte[] buffer, System.Int32 offset, System.Int32 size, System.AsyncCallback callback, System.Object state) [0x000e6] in <53e34a2ab1804f7fa3447cf99d35bb55>:0 
    at Mono.Security.Protocol.Tls.RecordProtocol.BeginSendRecord (Mono.Security.Protocol.Tls.ContentType contentType, System.Byte[] recordData, System.AsyncCallback callback, System.Object state) [0x00023] in <d8d3d829356d4fba871dd40905a9b7de>:0 
    at Mono.Security.Protocol.Tls.RecordProtocol.BeginSendRecord (Mono.Security.Protocol.Tls.Handshake.HandshakeType handshakeType, System.AsyncCallback callback, System.Object state) [0x00024] in <d8d3d829356d4fba871dd40905a9b7de>:0 
    at Mono.Security.Protocol.Tls.SslClientStream.BeginNegotiateHandshake (System.AsyncCallback callback, System.Object state) [0x00049] in <d8d3d829356d4fba871dd40905a9b7de>:0 
    at Mono.Security.Protocol.Tls.SslStreamBase.BeginNegotiateHandshake (Mono.Security.Protocol.Tls.SslStreamBase+InternalAsyncResult asyncResult) [0x0001e] in <d8d3d829356d4fba871dd40905a9b7de>:0 
  Unable to write data to the transport connection: Cannot access a disposed object.
  Object name: 'System.Net.Sockets.Socket'..
  Cannot access a disposed object.
  Object name: 'System.Net.Sockets.Socket'.
Comment 1 Martin Baulig 2017-12-11 20:15:59 UTC
Can someone please triage against the new web stack?
Comment 2 Martin Baulig 2017-12-11 20:16:07 UTC
Can someone please triage against the new web stack?