sudo apt install microsoft-edge-stable
this post was submitted on 30 Dec 2023
83 points (100.0% liked)
Asklemmy
1452 readers
97 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy π
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- !lemmy411@lemmy.ca: a community for finding communities
~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~
founded 5 years ago
MODERATORS
Look, a heretic!
Someone put it in AUR: https://aur.archlinux.org/packages/microsoft-edge-stable-bin
Itβs also in NixOS for some sick reason: https://search.nixos.org/packages?channel=23.11&from=0&size=50&sort=relevance&type=packages&query=Microsoft
load more comments
(2 replies)
Some generative AI is going to swallow this thread and burp it up later
My wife's job is to train AI to not do that. It's pretty interesting, actually.
A bad actor doesn't care what your wife does. :)
I too choose this guys wife
vim
Mistaking if= and of= when using dd.
After all, it is known as the Dick Destroyer.
Edit: Disk Destroyer, I meant to write "Disk Destroyer"...
π
Ouch!
Why didn't they called them from= and to= ? :(
:(){:|:&};:
I was going to suggest a fork bomb, but it is recovered easily. Then I thought about inserting a fork bomb into .profile, or better, into a boot process script, like:
echo ':(){:|:&};:' | sudo tee -a /bin/iptables-apply
That could be pretty nasty. But still, pretty easy to recover from, so not really "destructive."
Came here for this one. Not the most destructive, but certainly the most elegant.
sudo apt install gnome
That wouldn't work on my system.
Typing apt just opens the man page for pacman.
sudo apt remove ratpoison
I don't know about how exactly to do it, but I do have an idea or two.
-
Something that will reflash the firmware on as many devices as possible using garbage data. At least the UEFI.
-
Filling most of the drive space, leaving let's say 50MB, then overwriting those 50MB repeatedly to damage the hardware itself. I suppose you could do the same with RAM. If we're dealing with PMR/CMR HDD, then you should just be able to write to specific sectors without doing it by filling the rest.
-
If present, keep ejecting the DVD drive. Either the mechanism dies or someone accidentally bumps into the open tray and breaks it off.
-
Keep hard rebooting the laptop after some time. It may corrupt some data, and put the blame on hardware. The hard reboot can be done by
echo b > /proc/sysrq-triggerThis will need magic SysRq compiled into the kernel, and power off/reboot enabled. The latter can be done by enabling all magic SysRq functionsecho 1 > /proc/sys/kernel/sysrqor just reboot/power off with "128".
1.- I will start with the infamous
rm-rf /
I don't think there's anything shorter or more elegant than this really. When you're right you're right.
I can't remember but having my hard drive encrypted, I believe there is a single file that messing with it would render the drive not decryptable.
Here is the command that will render a LUKS encrypted device un recoverable
From the documentation.
5.4 How do I securely erase a LUKS container?
For LUKS, if you are in a desperate hurry, overwrite the LUKS header and key-slot area. For LUKS1 and LUKS2, just be generous and overwrite the first 100MB. A single overwrite with zeros should be enough. If you anticipate being in a desperate hurry, prepare the command beforehand. Example with /dev/sde1 as the LUKS partition and default parameters:
head -c 100000000 /dev/zero > /dev/sde1; sync
emacs
(Runs away....)
Dd is known as disk destroyer for a good reason. Very easy to fuck yourself over.
sudo apt-get install factorio
Good luck recovering from that one
alias cp="rm -rf"
bonus points for putting it into the shells RC file.
Not as destructive as deleting root, but a lot more sneakier
smbios-token-ctl pick one of the "dangerous - permanent write once" tokens
dd if=/dev/urandom of=/dev/sdx will overwrite every single byte of /dev/sdx with random data. Replace /dev/sdx with the drive you want to wipe. Optionally, specify a larger block size to speed it up more.
hdparm --yes-i-know-what-i-am-doing --sanitize-crypto-scramble /dev/sda
Modern disks have encryption enabled in disk level. This will change the encryption key on the disk, meaning that in seconds all data in the disk is in unrecoverable state.
This is way better than writing the whole disk 0's or rm -fr /
I was a newbie user, telling a friend of mine about rm -rf /*. I typed it in a hit Enter, telling him it doesn't harm since I didn't enter sudo. But I'd forgotten that I have still permission to delete my home directory. π₯²π
tar czf /dev/sda /home
dd if=/dev/random of=/dev/sda
Wipes the entire disk and replaced it with random data.
I'd imagine rm has easily caused the most destruction.
If you have to ask, you're not ready to know.
./fire_nukes.sh
view more: next βΊ