Conversation

Notices

1. Embed this notice
   Jan Wildeboer 😷:krulorange: (jwildeboer@social.wildeboer.net)'s status on Sunday, 19-Jan-2025 23:09:50 JST Jan Wildeboer 😷:krulorange:

   • Ricky Mondello

   @rmondello First: collect some facts.

   - Does dns work? simply ping your hostname from am machine that is tethered to your mobile device and see if it gets the correct IP address back
   - Try a trace to see if it is a connectivity problem and where the problem starts (not perfectly reliable, but helps a lot) tracert IP-ADDRESS
   - Make sure there are no other firewalls or "security" software packages involved on either your machine or the mobile device

   With that you should know more.

   • Embed this notice
     Erik van Straten (erikvanstraten@infosec.exchange)'s status on Monday, 20-Jan-2025 01:38:10 JST Erik van Straten

     in reply to

     • Ricky Mondello

     In a post that disappeared, @jwildeboer wrote:

     "@rmondello I do note that when I open mondello.com in my browser, I get a placeholder page that is http only, no https. This would be a reason that it *seems* that it is unreachable, because many browsers nowadays refuse to open sites without https."

     Unfortunately, that is *not* true. Browsers unnecessarily make the internet LESS SAFE. IT'S CRAZY!

     *Some* browsers will try https first when you type http:⧸⧸mondello.com (use // instead of ⧸⧸ I used to prevent Mastodon from showing http://). So far, so good.

     However, if an AitM (Attacker in the Middle, such as on public WiFi) blocks traffic from your browser to TCP port 443 (https) on the server, the browser will *silently* try port 80 (http). Pwned.

     This may happen in practice, for example on airports (https://www.bleepingcomputer.com/news/security/australian-charged-for-evil-twin-wifi-attack-on-plane/).

     Except for iOS and iPadOS, most browsers have an "https only" setting that is *OFF* by default, while it's name is misleading.

     *On* means that you can still use http, but you'll have to manually agree (you can still access the http devices on your local network, or on the internet. But you will be WARNED).

     However, Chrome appears to remember exceptions FOR EVER (I had to delete all browser data to make the last screenshot below. However, that also clears the browser's HSTS database).

     On iOS/iPadOS, from Safari, Edge, Firefox and Chrome, only Chrome has this option. So only Chrome provides *some* protection. People do not type "https://" in front of domain names, and most QR-codes I check are insecure.

     To test: open http://http.badssl.com. Instead of immediately seeing a (red) webpage, your browser should protect you by asking whether you want to use an http-connection.

     Alternative test-site (non-compliant with the Dutch law):
     http://gemeente.amsterdam
     (Gemeente translates to municipality).

     (Exactly that is why I wrote this, in Dutch: https://infosec.exchange/@ErikvanStraten/113855174617111536 earlier this afternoon).

     Note: Firefox on Android seems to forget "http allowed" exceptions when the browser is fully closed (good).

     @rmondello

     #httpsOnly #HSTS #httpsvshttp #iOS #iPadOS #Safari #Firefox #Edge #Chrome #Insecure #Infosec

   • Embed this notice
     Jan Wildeboer 😷:krulorange: (jwildeboer@social.wildeboer.net)'s status on Monday, 20-Jan-2025 01:38:10 JST Jan Wildeboer 😷:krulorange:

     in reply to

     • Ricky Mondello
     • Erik van Straten

     @ErikvanStraten @rmondello The reason I deleted it is that I used the wrong domain name. mondello.com where it should have been rmondelo
     lo.com. You saving copy paste from toots I deleted is a bit creepy, TBH.