Skip to content

Conversation

@taylor-b
Copy link
Contributor

@taylor-b taylor-b commented Nov 4, 2016

The incorrect statement is "Applications can avoid exposing IP
addresses... by not signalling non-relay ICE candidates."

However, simply not signaling candidates is not enough to prevent IP
addresses from leaking. These candidates will still be gathered and used
to form candidate pairs, which means connectivity checks will be sent
leaking the server reflexive address for every network interface.

The incorrect statement is "Applications can avoid exposing IP
addresses... by not signalling non-relay ICE candidates."

However, simply not signaling candidates is not enough to prevent IP
addresses from leaking. These candidates will still be gathered and used
to form candidate pairs, which means connectivity checks will be sent
leaking the server reflexive address for every network interface.
@aboba
Copy link
Contributor

aboba commented Nov 4, 2016

LGTM.

@aboba
Copy link
Contributor

aboba commented Nov 7, 2016

@dontcallmedom This tiny PR is failing due to a failure in travis-ci due to yarn not being installed:
cd node_modules/highlight.js/ && yarn && node ./tools/build.js -n xml javascript css http markdown xquery && cd ../../

@dontcallmedom
Copy link
Member

@aboba indeed, that's due to a recent change in respec :( I suggest ignoring Travis CI errors while we figure this out

@vivienlacourba could you look into this? I think the best option at this point is to force our CI infrastructure to the last version of ReSpec not using yarn (until travis-ci/apt-source-safelist#322 gets deployed)

@alvestrand alvestrand merged commit 8f7f3e5 into w3c:master Nov 10, 2016
@vivienlacourba
Copy link
Member

@aboba @dontcallmedom this issue has been fixed in #935

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants