4 ms·

For those who have a switch: https://www.switchbru.com/dns/ https://www.switchbru.com/dns/ is a simple hosted DNS server that lets you browse the web. And the

For those who have a switch: https://www.switchbru.com/dns/ https://www.switchbru.com/dns/ is a simple hosted DNS server that lets you browse the web. And the web browser runs webkit! https://i.imgur.com/0h803Ux.jpg https://i.imgur.com/0h803Ux.jpg shows a Chart.JS demo running in a canvas. Unfortunately the File API does not work: https://i.imgur.com/GA5kNGp.jpg https://i.imgur.com/GA5kNGp.jpg

backpropaganda 8y ago
annddddd.... patched. Seriously, though, it's gonna be very easy for Nintendo to patch this particular DNS out. While running a browser doesn't really hurt their bottomline, a browser is typically the weakest link in any console and thus is often used to find an exploit and run homebrew. The Switch as of now doesn't have a non-intrusive exploit, but allowing arbitrary javascript could result in one.
- striking 8y ago
  This is a minor abuse of the captive portal resolution function, that opens the web browser to let the user log in to any captive portal. There's no real way to "patch" this.
  - backpropaganda 8y ago
    > There's no real way to "patch" this. Just disable custom DNS. Only allow a few whitelisted DNS that 99.9% of people are going to use anyway.
    - detaro 8y ago
      What does that gain? It prevents people from browsing the web, what's the issue with that? For exploits/jailbreaks/... it'd be easy to use a local fake captive portal, so it doesn't protect against that unless they kill that feature completely, making the device unuseable with many networks.
      - voltagex_ 8y ago
        It would also prevent people with jailbroken devices from blocking *.nintendo.com so there's that.
        krageon 8y ago
        If you own the network it's not super hard to just filter all traffic doing DNS. If you have a properly owned phone, you can probably run this over your phone hotspot and do the packet inspection that way. Then you can block all nintendo traffic, while still not having a "custom" DNS. If you really tried, you could still even have your custom DNS except it would be spoofing another server. The point is that if you own the network (and you do), then the clients are nominally at your mercy.
    - IntelMiner 8y ago
      How do you define "custom" DNS exactly?
- floatboth 8y ago
  Well, AFAIK it did result in an exploit for OS 1.x, webkit was patched in later versions. RCM mode is barely "intrusive". Just shove a paperclip into the joycon port, easy.

backpropaganda 8y ago

annddddd.... patched. Seriously, though, it's gonna be very easy for Nintendo to patch this particular DNS out. While running a browser doesn't really hurt their bottomline, a browser is typically the weakest link in any console and thus is often used to find an exploit and run homebrew. The Switch as of now doesn't have a non-intrusive exploit, but allowing arbitrary javascript could result in one.

striking 8y ago
This is a minor abuse of the captive portal resolution function, that opens the web browser to let the user log in to any captive portal. There's no real way to "patch" this.
- backpropaganda 8y ago
  > There's no real way to "patch" this. Just disable custom DNS. Only allow a few whitelisted DNS that 99.9% of people are going to use anyway.
  - detaro 8y ago
    What does that gain? It prevents people from browsing the web, what's the issue with that? For exploits/jailbreaks/... it'd be easy to use a local fake captive portal, so it doesn't protect against that unless they kill that feature completely, making the device unuseable with many networks.
    - voltagex_ 8y ago
      It would also prevent people with jailbroken devices from blocking *.nintendo.com so there's that.
      - krageon 8y ago
        If you own the network it's not super hard to just filter all traffic doing DNS. If you have a properly owned phone, you can probably run this over your phone hotspot and do the packet inspection that way. Then you can block all nintendo traffic, while still not having a "custom" DNS. If you really tried, you could still even have your custom DNS except it would be spoofing another server. The point is that if you own the network (and you do), then the clients are nominally at your mercy.
  - IntelMiner 8y ago
    How do you define "custom" DNS exactly?
floatboth 8y ago
Well, AFAIK it did result in an exploit for OS 1.x, webkit was patched in later versions. RCM mode is barely "intrusive". Just shove a paperclip into the joycon port, easy.