Firefox

From Kicksecure
Jump to navigation Jump to search
Mozilla Firefox logo

Using Firefox in Kicksecure.

Kicksecure is not officially associated with Mozilla Firefox. See Disclaimer.

Stable Version[edit]

Firefox Extended Support Release (ESR) is installed by default in Kicksecure. It is installed from Debian packages sources.

Other Versions[edit]

Rapid Release[edit]

For information on how to get the rapid release version of Firefox, please press Expand on the right.

Disclaimer[edit]

There are two different entities.

  • A) Mozilla: Developer of the Mozilla Firefox browser. Versus,
  • B) Kicksecure: An independent Linux distribution.

Kicksecure is not officially associated with Mozilla Firefox. The Mozilla Firefox logo is trademarked by Mozilla.

Why this disclaimer? See Firefox Potential Legal Risk.

Related[edit]

Footnotes[edit]

  1. Kicksecure:
    • system-wide (requires administrative ("root") rights) (compatible with noexec): Click = Copy Copied to clipboard! flatpak install flathub {{{package}}}
    • per-user (no administrative rights required) (probably not compatible with noexec): Click = Copy Copied to clipboard! flatpak --user install flathub {{{package}}}
    What is better? System-wide or per-user?
    • <>usability:</> Flathub is enabled by default system-wide but not per-user.archive.org iconarchive.today icon
    • multi-user: On a multi-user system (probably if multiple human users use the same computer, which is rare nowadays), system-wide might be preferable as this saves disk space.
    • At preset: Does not make any difference.
    • Future-proof: Per-user might be more future-proof. It would be compatible with future Kicksecure security improvements user-sysmaint-split. However, noexec for the home folder is to be considered later, at which point this documentation needs to be updated once that has been implemented.
  2. Kicksecure-Qubes Template: flatpak cannot be used with the --user option. This is because in case of using a Qubes Template, the flatpak needs to be installed system-wide into the /var/lib/flatpak folder. This is due to Qubes Persistence. If the --user option was used, the flatpak would only be available in the Template's home folder but not in any App Qube based on that Template, because App Qubes have their own independent home folder.
  3. Kicksecure-Qubes App Qube: flatpak should be used with the --user option. This is because in case of using an App Qube, the flatpak needs to be installed per-user only into the ~/.local/share/flatpak folder and not system-wide. This is due to Qubes Persistence. If the --user option was not used, the flatpak would only be available in the App Qube's non-persistent /var/lib/flatpak folder located in the root image.

We believe security software like Kicksecure needs to remain Open Source and independent. Would you help sustain and grow the project? Learn more about our 12 year success story and maybe DONATE!