Currently we do not support SSL session caching and so generate a bogus peer identity in TransportLayerPeerName
Is this still relevant, and if so, what are next steps and priority? Thanks
backlog: --- → parking-lot
OS: Mac OS X → All
QA Contact: jsmith
Hardware: x86 → All
Whiteboard: [WebRTC], [blocking-webrtc-]
It's still relevant but very low priority now that we have bundle.
You need to log in before you can comment on or make changes to this bug.