![]() It is a risk you have to decide if you are willing to take. Just like the original script, it is code you may not understand, and you should be cautious when running it. You can keep an eye out for updates to the uninstall.sh script, and run it when it's ready.īe aware that the uninstall script may break something else, especially if you have made other changes since installing the software originally. It appears that the uninstall script doesn't do everything yet (it will possibly still leave some things behind), but the plan seems to be that it will be fixed soon. It appears that the github that the installer pulled install files from comes with an uninstaller. A shell script somebody has on their homepage? Not so much, you may want to check that one a lil more carefully. ![]() There's also a sliding scale of trust: popular apt packages are installed all day every day by people all over the world and problems are usually quickly discovered. Note as I said in a comment on the other answer this is not fundamentally different from proprietary OSes: all of the same caveats apply and it's much harder (by design) to just re-install the OS over and over. If you are doing this on a bare-metal server, be prepared to reinstall from scratch. Use virtual machines, clone from known good states before running potentially destructive commands, and be ready to rollback. You will likely never be able to reverse an action like that. Directories can be created, configuration files edited. Code from the internet can be downloaded and executed. If you run it without sudo privs there are certain things it can't do, but it can still do a lot and if you run it with sudo all bets are off.įiles can be permanently deleted. What you do need to do is understand what happens (or can happen) when you run a script or a program that modifies your system like apt: AnythingĪnything can happen. While I broadly agree with Nmath's answer, reading every single line of every single script or digging deep into every single package you apt install (don't forget the transitive deps!) isn't practical for most of us. Nobody should ever blindly run a script without being able to read and understand exactly what the script does- this applies to veteran Linux users just as much as it applies to people who are using Linux for the first time. ![]() ![]() Also, if you don't even know what the script does, you have no idea what you just did to your computer- which is the exact situation you find yourself in right now. Blindly executing code opens you up to possibly malicious actions. Running scripts or commands without knowing what they do is horribly careless. If this were a simple script that only performed one or two actions, you could break it down and possibly undo these actions.īut in this case, this script executed dozens (hundreds?) of operations.Īs a side note, I feel the publisher of this script did you a huge disservice by claiming that this script is "secure" and "great for people who are new to Linux". A bash script is simply a list of instructions and commands that run in your terminal. The instructions on the script tell you to start with an operating system that is freshly installed, so if you want to go back to the point before you ran this script, you should reinstall the operating system.Īs others have mentioned in comments, you can't uninstall a bash script.
0 Comments
Leave a Reply. |