Custom Linux or Tails

Technical Specification: Custom "Amnesic" Linux Build / Tails Modification

1. Goal

Assemble or modify a Linux distribution (either a custom live ISO based on Debian/Ubuntu or a modification of Tails) that:

• Contains Firefox browser with update capability;

• Supports USB Bluetooth adapter (specify the exact model — see suggested clarifications);

• Supports sound (sound drivers, working via ALSA/PulseAudio);

• After any reboot, completely “forgets” user data (caches, temporary files, downloads, etc.), but retains the installed browser and drivers (these components remain operational without reinstallation).

2. Overall system behavior

• The system should boot as live (from flash drive/USB) and operate in “safe”/ephemeral mode.

• By default all user data (caches, downloaded files, sessions, temporary directories) is lost upon reboot/shutdown.

• Exceptions for preservation: Firefox profile (if needed), installed drivers (Bluetooth, audio) — they should be “permanently” embedded in the image or in a separate storage that does not reset.

3. Functional requirements

3.1. Browser

• Firefox is installed and runs “out of the box”.

• Firefox updates should be possible:

  • Either through Mozilla’s built-in update mechanism (preferably), or through the distribution’s package manager.

  • The mechanism should work in live mode (for example, updates are written to the persistence space without disrupting “amnesia”).

3.2. Bluetooth

• Support for a specific USB Bluetooth adapter (specify model; if unknown — implement a simple addition mechanism via VID:PID).

• Necessary firmware and kernel modules are installed and working.

• A utility for managing the adapter (e.g., bluetoothctl) is available.

• Device connection/scanning is tested manually.

3.3. Sound

• Standard audio drivers (ALSA) work, and if needed, user-level via PulseAudio or PipeWire.

• Ability to play sound from the browser (test via any site with audio).

• Basic diagnostic utilities are installed and working (aplay, arecord, pavucontrol for PulseAudio).

3.4. Amnesia / “Cleaning”

• All temporary and user data (except permitted saved components) are deleted upon reboot.

  • /tmp, caches (if not part of the saved Firefox profile), session logs, temporary files are created in tmpfs

  • Explicitly specify: upon shutdown/reboot, no user traces should remain on disk/flash except the permitted ones.

• Optional: add “one-time mode” — manually reset everything on startup, including configuration changes, except the built-in ones.

3.5. Memory (Persistence)

• Implement a selective persistence mechanism: only save

  • Firefox (or its profile/settings, if needed)

  • Drivers (Bluetooth, sound)

• All other data is reset.

• The persistent storage should be encrypted (if possible) or at least isolated from the rest to prevent “leakage” into shared memory.

4. Non-functional requirements

• The image must be bootable from USB (ISO or hybrid, ready for writing with dd/Rufus).

• Minimal dependencies to maintain lightness and quick startup behavior.

• Compatibility with modern hardware (preferably x86_64).

• Security: there should be no “default” open services with insecure configurations.

• Document how to update Firefox and, if necessary, drivers in this system.

5. Updates

• Implement a mechanism for updating Firefox without disrupting “amnesia” behavior: updates are written to the persistent layer, other data remains ephemeral.

• Drivers — can be “embedded” in the image or in persistence; driver updates should be described in the instructions.