Skip to content
Snippets Groups Projects
  1. Aug 27, 2019
    • Cecylia Bocovich's avatar
      Modified broker /debug page to display counts only · 00eb4aad
      Cecylia Bocovich authored
      The broker /debug page was displaying proxy IDs and roundtrip times. As
      serna pointed out in bug #31460, the proxy IDs can be used to launch a
      denial of service attack. As the metrics team pointed out on #21315, the
      round trip time average can be potentially sensitive.
      
      This change displays only proxy counts and uses ID lengths to
      distinguish between standalone proxy-go instances and browser-based
      snowflake proxies.
      00eb4aad
  2. Aug 26, 2019
  3. Aug 24, 2019
  4. Aug 19, 2019
  5. Aug 16, 2019
  6. Aug 15, 2019
  7. Aug 12, 2019
  8. Aug 08, 2019
    • Cecylia Bocovich's avatar
    • Cecylia Bocovich's avatar
      Add a timeout to check if datachannel opened · e77baabd
      Cecylia Bocovich authored
      This is similar to the deadlock bug in the proxy-go instances. If the
      proxy-pair sends an answer to the broker, it previously assumed that the
      datachannel would be opened and the pair reused only once the
      datachannel closed. However, sometimes the datachannel never opens due
      to ICE errors or a misbehaving/buggy client causing the proxy to
      infinitely loop and the proxy-pair to remain active.
      
      This commit reuses the pair.running attribute to indicate whether or not
      the datachannel has been opened and sets a timeout to close the
      proxy-pair if it has not been opened by that time.
      e77baabd
    • Cecylia Bocovich's avatar
      Reuse proxypair if sendAnswer fails · 6cc944f2
      Cecylia Bocovich authored
      Make sure to set proxypair.active to false if createAnswer or
      setLocalDescription fails. This should prevent one edge case the results
      in an infinite loop described in ticket #31100.
      6cc944f2
  9. Aug 01, 2019
  10. Jul 31, 2019
  11. Jul 27, 2019
Loading