Kicksecure How to test an OS

Kicksecure ™

Download

On Computer USB Installation Intel / AMD64 ARM64 Raspberry Pi PPC64 Windows (VM) Mac Linux (VM) VirtualBox (VM) Qubes (VM) KVM (VM) Debian morph to Kicksecure More options Source Code

About

Overview Features Why Open Source? Project Activities Contributors Mission & Vision

Docs

Documentation FAQ Troubleshooting

Community

Forums Forum Best Practices Contribute

Support

Self Support First Policy Search Engines, Docs and AI Support (Limited) Reporting Bugs Contact (Restricted)

Tools Upload file Special pages Recent changes Print Version Page meta What links here Related changes Page information

Page Read Edit History Move Protection Unwatch Watch Delete Purge

User Preferences Watchlist Contributions Logout Create account Login

Donate

Testing OS installation and Post Installation

Overview

Testing the operating system after the first release cycle (for testers) is an important phase in development that every project producing complex software must go through. The testing phase contains a lot of steps that vary and depend on the project being tested.

Testing the operating system before installation

Supported Installation Medium

For Whonix and Kicksecure, we have:

Libvirt

KVM: .libvirt image installation for KVM (GNU/Linux only; preferably tested on a Debian host and another common host used by users running the latest or near-latest KVM version, such as Arch, Fedora, or NixOS.. etc).

OVA

VirtualBox: .ova image installation for VirtualBox (priority for Windows users running the latest Windows version and the latest VirtualBox version; then GNU/Linux users running the latest VirtualBox version, e.g. from the VirtualBox repository on Debian or similar case).

Qubes

• Qubes: From Qubes repository for both KS and Whonix.

ISO

.iso installation should be tested on all supported hypervisors, as it can produce unexpected results e.g a completely black screen when booting the .iso for installation inside Qubes HVM due to a resolution issue .

Before and During Installation

• Download URLs are all functional with proper speed

• Validate checksum and signature verification (including the website instructions for verification).

• Follow the website instructions for the installation (if updated and available to the current version being tested) to check whether everything works the same or needs updating to report later.

• Booting time is normal.

• Legacy VS UEFI boot for the OS.

• Secure Boot and TPM (if supported/used).

For ISO specific

• No errors, failures, warnings, or unexpected behavior during ISO boot; if any occur, verify whether they are normal/expected.
• Boot into live mode.
  • If live mode boots as expected, check:
    • Internet connectivity (Static/Manual and DHCP, Wire/Wireless).
    • Browser functionality.
    • OS can read external flash/hard drives.
    • Sound/audio, mic and camera are working.
    • Any other expected tools are installed and functional (text editor, office suite, etc).
• Boot into installation mode.
  • If installation mode boots as expected, check:
    • Changing language (all expected options are displayed and functional).
    • Changing region/location (all expected options are displayed and functional).
    • Changing/adding keyboard layouts (all expected options are displayed and functional).
    • Changing number and date format (all expected options are displayed and functional).
    • Partitioning is functional (automatic/default and manual).
    • Encryption is functional (note: also installing without encryption).
    • Other options, if available, such as file system types e.g ext4, Btrfs..etc.
• Check that the installation process is smooth (expected time, errors..).

For hypervisor-specific images

• The default/expected settings for the virtual machine inside the hypervisor are correct after import.

Post Installation

• Encryption is functional (.iso specific).
• No errors, failures, warnings, or unexpected behavior during ISO boot; if any occur, verify whether they are normal/expected.
• Make sure to:
  • Boot into every available boot menu option (live, user/admin, persistent, etc).
  • Test any keys indicated for specific functionality (e.g GRUB options).
  • Confirm all expected packages/apps are present and functional.
• The update and upgrade process works (with the expected repositories).
• No unusual messages are recorded in journalctl from boot time until the OS finishes loading.
• All project changes pushed to the OS are functional (e.g X app should not display Y message when opened).
• OS can read external flash/hard drives.
• Taking snapshots and rolling back to a previous one is functional (if supported).
• Check that the default open ports match the firewall rules and listening services.
• Sound/audio, mic and camera are working.
• Internet connectivity (Static/Manual and DHCP, Wire/Wireless).

For hypervisor specific

• Make sure to check (according to the wiki instructions):
  • Shared folder is functional.
  • GPU passthrough is functional.

Footnotes

Kicksecure A secure by default operating system with the latest security research in place.

Dark mode

Follow us on social media

Supported by Power Up Privacy

Kicksecure is proudly supported until 2026 by Power Up Privacy, a privacy advocacy group that seeks to supercharge privacy projects with resources so they can complete their mission of making our world a better place. (Strictly subject to our sponsorship policy.)

At Kicksecure we value freedom and trust, supporting Open Source and Freedom Software

By using this website, you acknowledge you have read, understood, and agree to be bound by these agreements: Terms of Service, Privacy Policy, Cookie Policy, E-Sign Consent, DMCA, Imprint 2012- 2026 ENCRYPTED SUPPORT LLC

Your support makes
all the difference!

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 13 year success story and maybe DONATE!