New issue
Advanced search Search tips

Issue 848075 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: May 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug
Proj-Servicification

Blocked on:
issue 844187
Blocking:
issue 721401



Sign in to add a comment

Migrate remoting/signaling/xmpp_signal_strategy.cc to network service

Project Member Reported by xunji...@chromium.org, May 30 2018 
remoting/signaling/xmpp_signal_strategy.cc currently uses both ProxyResolvingClientSocket and net::SSLClientSocket.

It needs to be ported to network service's mojo sockets.

Comment 1 by xunji...@chromium.org, May 31 2018 

xmpp_signal_strategy.cc is used for setting up an ICE connection between the client and the host for Chrome Remote Desktop. 

It has three modes:
- TlsMode::NO_TLS           // Just establish a TCP connection
- TlsMode::WITH_HANDSHAKE   // TCP + a custom handshake + regular TLS handshake
- TlsMode::WITHOUT_HANDSHAKE: // TCP + regular TLS handshake.

Converting xmpp_signal_strategy requires non-trivial amount of work.

Comment 2 by jamiewa...@chromium.org, May 31 2018

Status: Untriaged (was: Available)

Comment 3 by xunji...@chromium.org, May 31 2018

Status: WontFix (was: Untriaged)
Based on the context on  Issue 848079 , chromoting won't be affected by the s13n effort.
►

Sign in to add a comment