Helper Script – central auto-script.sh that automates most settings (kernel parameters, MAC, Whonix gateways, Kicksecure, RAM Pool, Amnesic Tmpfs, Live Mode, destruction tools, LUKS hardening)
Features:
One‑click copy for every command
Dark / light modes
Progress bar
Responsive design (works on desktop, tablet, phone)
Warning: This guide is for advanced users. Some procedures (especially destruction tools in Tab 7) can cause permanent data loss. Always take full backups before applying any settings.
I don’t have a problem with new members (or anonymous accounts) creating community guides. See High quality guides for some discussion about their quality.
Regardless of the topic, there is no user label you can blindly rely on, because users’ criteria and standards can vary. When it comes to security issues in particular, you won’t be satisfied unless you understand what you’re doing. (Leaving aside the illusion of security by shifting trust.)
It would be better to replace most of the script with native Salt formulas, so you can easily declare what state you want your VMs to be and makes the entire repository maintainable for one person.
What you said is correct. I used some things from artificial intelligence, mostly summaries from websites. As you know, AI cannot create such a file from scratch. Likewise, I didn’t document anything except after testing it out.
Also, all the translation was done using artificial intelligence because my native language is Arabic.
You are correct. This is for an intermediate level at the very least, and I had an explanation but I didn’t publish it because it was in my native language, Arabic, and the Arabic community is not interested in these things.
The script does not make services virtual by default except after the user’s consent. Likewise, everything in it I tested several times before documenting.
Regarding the template names, I thought about making it choose the latest template, but since new templates will come out after about a year, I will update them as soon as they are released, or I will make it choose them automatically. As for kernelopts, you are correct, and there are many of them, but they are for those who want them. Regarding template installation, I mentioned the templates that exist by default. As for the destruction feature, it is for emergencies and is derived from ‘buskill’ with some improvements. The live mode is taken from this community, and I only removed zram. Many thanks to you.
If you have any feedback, please write it, I would be very grateful to you.
Note: I am not an expert, I’m an intermediate user. This guide was originally written for a friend of mine, and then I decided to translate it and publish it.
For your information, this guide took nearly four months of my time. As for summarizing from websites, I did it first to learn. And I don’t think the site would forbid, for example, a user from using AI to design HTML
There are some good things in it I can see already. It just makes it easier for collaboration, help, fine tuning etc otherwise we can just comment here which makes it difficult.
Sorry but I’m now very suspicious about potential AI contributions. Some parts (i.e. updating templates) are very generic and don’t follow the official way so I thought it was generated. It turns out you spent some time on this, sorry for my wrong assumptions.
Don’t apologize, honestly. Artificial intelligence is exhausting and sometimes hallucinates. I was trying to find the error that AI causes in HTML design, and I would spend hours just to figure out where it made a mistake. Sometimes it even tells you that updating dom0 requires using ‘sudo apt update’. The original purpose of AI is just to be an assistant.
