[Dnssec-trigger] dnssec-trigger at Hotel hotspot in Vienna

Carsten Strotmann (private) carsten at strotmann.de
Tue Sep 20 19:56:27 UTC 2011

Hash: SHA1

On 9/20/11 8:41 PM, Paul Wouters wrote:
> On Tue, 20 Sep 2011, Carsten Strotmann (private) wrote:
>> Not sure how this can be solved, maybe by having DNSSEC-trigger
>> to test a well known webpage of port 80 to detect a captive
>> portal. MacOS X 10.7 now also has an automatic captive portal
>> detection (ported from iOS). Not sure if there are APIs available
>> to use the function.
> I think it is :)
> http://www.apple.com/library/test/success.html
> The real question is should dnssec-trigger get involved here or
> not. Ideally, the OS or browser is going to do the portal
> detection.
> dnssec-trigger could decide to reprobe every 5 seconds if it sees 
> this "portal" indicator? eg remain more aggressive while on a
> suspected landing page that hopefully soon will open up auth DNS.
> Paul

dnssec-trigger thinks it succeeds, effectively disabling MacOS X
portal detection, so if dnssec-trigger is executed before the portal
detection, the system fails. Sometimes dnssec-trigger is running after
the portal-detection, then it works.

- -- Carsten
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/


More information about the dnssec-trigger mailing list