I want to setup a bunch of laptops to be web kiosks, I’ll organize my wants into a list so that it’s easier to skim:

  • Open a version of Firefox with the normal ui, tabs and all.
  • Automatically enters a session with no user input on reboot
  • Doesn’t allow doing anything but interacting with Firefox (kinda obvious, kiosk and all)
  • Auto-login
  • Automatic updates, with them being applied on restart
  • Firefox settings reset on reboot

Nice to haves:

  • nice Plymouth screen to hide the scary code on startup.
  • completely block any attempts to change configuration on Firefox
  • ad-block
  • easy deployment to a bunch of machines.

If these sound like pretty strict requirements, they are, I’m doing this to attempt to get an internship by making my school’s web kiosk laptops not suck (they currently run a janky install of Ubuntu 18.04)

Any help would be greatly appreciated, and I’d be glad to add more information.

  • solrize@lemmy.world
    92·
    28 days ago

    There’s no way to srsly prevent a full-bloat browser from messing with its environment. Make a static VM image and reboot it at the beginning of every session.

    • rudyharrelson@lemmy.radio
      2·
      28 days ago

      There’s no way to srsly prevent a full-bloat browser from messing with its environment.

      Can you elaborate on this? I’m curious as to what manner a browser like Firefox could be exploited in order to affect its environment outside of something like a sandbox escape.

      • solrize@lemmy.world
        42·
        28 days ago

        Tools:preferences, about:config, file downloads, form prefills, remember password, etc. yes you can try to lock everything but it’s too easy to miss something. And then there are outright RCEs. There’s just too much attack surface.

        • markstos@lemmy.world
          21·
          28 days ago

          I agree. Flatpak could be used to further lockdown what Firefox can do, but it has so much features and complexity that I also expect it to be difficult to successfully lockdown.

          I would either start with a product that explicitly has just the features a web-kiosk needs or use something based on ChromeOS, which explicitly has a set of enterprise policies that are there to allow admins to lock down a fleet of Chromebooks as they need.

          This is based on the security principle that a system is far more secure if you explicitly allow what you need vs trying to explicitly block or disable all the things you don’t want.

          Over time, the features you need to allow your web kiosk needs maybe somewhat static and in your control, while all the features you need to disable in Firefox could be constantly evolving and put of your control if you are keeping Firefox up to date.