Skip to content
This repository has been archived by the owner on Jan 28, 2025. It is now read-only.

Decap: Probe non-existent dns names to detect portal #16

Open
kpcyrd opened this issue Jul 1, 2018 · 0 comments
Open

Decap: Probe non-existent dns names to detect portal #16

kpcyrd opened this issue Jul 1, 2018 · 0 comments

Comments

@kpcyrd
Copy link
Owner

kpcyrd commented Jul 1, 2018

I ran into a few networks that whitelist the clients3.google.com endpoint that we currently use to detect captive portals. We should evaluate if probing <18-random-characters>.com generally results in redirects as well or if the captive portals are able to detect that those records do, in fact, not exist. This might be more reliable than the current captive portal detection which has false-negatives occasionally.

@kpcyrd kpcyrd changed the title Decap: Probe non-existant dns names to detect portal Decap: Probe non-existent dns names to detect portal Jul 1, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant