Firefox on Debian stable is so old that websites yell at you to upgrade to a newer browser. And last time I tried installing Debian testing (or was it debian unstable?), the installer shat itself trying to make the bootloader. After I got it to boot, apt refused to work because of a missing symlink to busybox. Why on earth do they even need busybox if the base install already comes with full gnu coreutils? I remember Debian as the distro that Just Wroks™, when did it all go so wrong? Is anyone else here having similar issues, or am I doing something wrong?

  • 9488fcea02a9@sh.itjust.works
    link
    fedilink
    arrow-up
    60
    arrow-down
    1
    ·
    6 days ago

    My bank used to complain that my browser was out of date. I wrote an email to customer service explaining to them that:

    A) debian’s “out of date” browser actually includes all up to date security patches. B) simply reading the browser agent isnt really security. I had simply been spoofing my browser agent to get around their silly browser “security” policy

    They removed the browser check 2 weeks later. Not sure if it was because of me

    • efstajas@lemmy.world
      link
      fedilink
      arrow-up
      22
      arrow-down
      1
      ·
      6 days ago

      simply reading the browser agent isnt really security

      It’s not for their security, but for that of genuinely clueless people that are just running an actually outdated browser that might have known and exploitable security flaws.

      • LeFantome@programming.dev
        link
        fedilink
        arrow-up
        7
        arrow-down
        1
        ·
        6 days ago

        It is not about security at all. They do not want to test or support old browsers. So, they set a minimum version and tell you that you need to upgrade to that.

        If they only support one browser, it is going to be Chrome. Chrome has more zero-day vulnerabilities than any other project I can think of. It is not about security.

        • efstajas@lemmy.world
          link
          fedilink
          arrow-up
          3
          ·
          edit-2
          5 days ago

          How do you know this? Of course there are lots of reasons for why they’d want to enforce minimum browser versions. But security might very well be one of them. Especially if you’re a bank you probably feel bad about sending session tokens to a browser that potentially has known security vulnerabilities.

          And sure, the user agent isn’t a sure way to tell whether a browser is outdated, but in 95% of cases it’s good enough, and people that know enough to understand the block shouldn’t apply to them can bypass it easily anyway.

        • SpaceCowboy@lemmy.ca
          link
          fedilink
          arrow-up
          3
          ·
          6 days ago

          Yeah if it were about security they’d check the version of HTTPS, SSL, TLS and all that stuff.

          • efstajas@lemmy.world
            link
            fedilink
            arrow-up
            2
            ·
            edit-2
            5 days ago

            Doing that would tell you nothing about whether the browser might have un-patched, known vulnerabilities elsewhere.

  • Siegfried@lemmy.world
    link
    fedilink
    arrow-up
    36
    arrow-down
    1
    ·
    7 days ago

    Ehm… im using debian stable, no website is telling me to update Firefox (I’m on deb 10, 11 and 12 in different PCs).

    Deb 12, my home computer, is on unstable and running smoothly.

    Debian isn’t “just works” but “it’s a freaking rock” + “open source hardcore philosophy”.

    Maybe I got lucky?

  • LeFantome@programming.dev
    link
    fedilink
    arrow-up
    13
    arrow-down
    1
    ·
    6 days ago

    As everybody else has said, Debian is working as intended. To respond to the actual post though, Debian is working exactly as it always has.

    If you think Debian used to be good, you must really love it now. It is better than ever.

    Unlike in the past, the primary drawback of Debian Stable ( old package versions ) has multiple viable solutions. Other have rightly pointed out things like the Mozilla APT package and Flatpaks. Great solutions.

    My favourite solution is to install Arch via Distrobox. You can then get all the stability of Debian everywhere you need it and, anytime you need additional packages or newer packages, you can install them in the Arch distrobox. Firefox is a prime candidate. You are not going to get newer packages or a greater section than via he Arch repos / AUR ( queue Nix rebuttals ).

    • DefederateLemmyMl@feddit.nl
      link
      fedilink
      English
      arrow-up
      9
      ·
      6 days ago

      Yeah and Flatpaks also exist.

      Flatpaks are probably the best generic solution for using an LTS release like Debian Stable on a desktop system. You get the best of both worlds: up to date desktop packages and a stable base.

  • umbraroze@lemmy.world
    link
    fedilink
    arrow-up
    15
    ·
    6 days ago

    Debian’s Firefox is Firefox ESR, or Extended Support Release. It’s behind the bleeding edge, but gets security updates.

    If you want the bleeding edge Firefox, you can add Mozilla’s own APT repository and install it. Doesn’t even conflict with Debian (firefox-esr vs firefox, it even uses a separate user profile by default). Instructions are on the Firefox download page somewhere.

  • Samsy@lemmy.ml
    link
    fedilink
    arrow-up
    10
    ·
    6 days ago

    I manage over 40 Debian clients in production use. All are managed with ansible. It’s the easiest time in my sysadmin time ever.

    My own systems are fedora and Debian unstable. Why? Because I test upcoming changes and features. And think how it would be if all 40 clients run on unstable or fedora, every day updates of 20-60 packages for nothing the user would care about.

    Debian stable is my hero.

  • flop_leash_973@lemmy.world
    link
    fedilink
    arrow-up
    20
    arrow-down
    2
    ·
    7 days ago

    These days I care a lot less that a package is outdated than I do it being unstable personally. If security concerns are getting patched and it is still doing what I want it to do, I couldn’t care less about UI elements getting moved around just to make some PM happy.

    • nexussapphire@lemm.ee
      link
      fedilink
      English
      arrow-up
      3
      arrow-down
      1
      ·
      7 days ago

      Why does the installer still explode sometimes when I use it on my computers. I use it on my mother’s computer or our movie server and it works fine.

      Maybe it just eats shit when it sees a btrfs partition or something. Nothing against Debian but I tried to install Debian testing weekly and it just refused to install on my system 76 laptop. After flashing arch on my USB drive to wipe the disk I just said fuck it and installed arch on my laptop again. I haven’t had any issues with arch since I’ve installed it on my desktop five years ago. If arch blows up on my laptop I’ll try Debian again.

  • iopq@lemmy.world
    link
    fedilink
    arrow-up
    7
    arrow-down
    2
    ·
    6 days ago

    What’s why we have NixOS. The unstable channel is more stable than most other distros and when it’s not, you just roll back

  • Possibly linux@lemmy.zip
    link
    fedilink
    English
    arrow-up
    11
    ·
    edit-2
    7 days ago

    TL;DR

    You want Debian stable with either back ports or containers. On desktop flatpak is your friend. Also do not add extra repos.

    Honestly there is little reason to not use flatpak for web browsers. If you want packages from Fedora or other distros you can use Distrobox with podman as the back end.

      • debil@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        7 days ago

        The fix comes to sid first. (Not counting experimental.) The right way to do it is to run mixed testing/unstable with apt-pinning so that nothing gets pulled from unstable unless spcifically requested.

        That said, stable with Firefox from Mozilla’s site and Neovim built from sources and gpack’d into deb package runs perfectly fine with much less hassle.

  • rc__buggy@sh.itjust.works
    link
    fedilink
    arrow-up
    7
    arrow-down
    1
    ·
    edit-2
    7 days ago

    Huh? Install testing or sid?

    The Debian way is to install stable then change your sources.list to either testing or unstable.

    I call shenanigans.

    edit: what version was Stable using before 11Jun? 'cause it’s 115.12.0esr-1 right now.