Re:Launch HN: Got-it (YC W19) – Bluetooth labels for trackin...
by davidlstanton on Monday December 16, 2019 @01:55PM
(#21805875)
Thanks very much for bringing this up and looking into it for us. We're on it now!
Re:Launch HN: Got-it (YC W19) – Bluetooth labels for trackin...
by davidlstanton on Monday December 16, 2019 @02:24PM
(#21806158)
I've manually flushed open dns and dig is now only reporting 35.189.102.199 any chance it's now working for you?
Re:Launch HN: Got-it (YC W19) – Bluetooth labels for trackin...
by 6wfu5c1ci1lm8 on Monday December 16, 2019 @04:29PM
(#21807417)
Nope. Still borked on OpenDNS.
Re:Launch HN: Got-it (YC W19) – Bluetooth labels for trackin...
by davidlstanton on Monday December 16, 2019 @08:20PM
(#21809539)
Looks like it's been content blocked with Open DNS on their family friendly DNS servers. I've submitted a request for it to be categorised. Previous experience is that this takes a few days.
Re:Launch HN: Got-it (YC W19) – Bluetooth labels for trackin...
by davidlstanton on Monday December 16, 2019 @07:52PM
(#21809383)
Cries... I'll dig deeper into this tomorrow. Cheers for sharing.
However, other DNS queries get pointed to 146.112.61.106 (hit-adult.opendns.com), and according to testssl.sh offers only TLS 1.2, but doesn't have server cipher order, and has an incomplete chain of trust.
The latter IP address also seems to be vulnerable to Secure Client-Initiated Renegotiation, and BEAST (CVE-2011-3389), and maybe LUCKY13 (CVE-2013-0169).