Challenge: post code that causes the most damage to a Windows or Linux machine. Bonus points if it destroys hardware

Challenge: post code that causes the most damage to a Windows or Linux machine. Bonus points if it destroys hardware

Other urls found in this thread:

phoronix.com/scan.php?page=news_item&px=UEFI-rm-root-directory
openwall.com/lists/oss-security/2015/01/27/9
linfo.org/int_0x80.html
linfo.org/system_call_number.html
twitter.com/AnonBabble

rm -rf /*
it can brick your system if you use systemd.

Just use a hammer.

Any good asm source code on a row hammer?

Preferably for Linux.

>row hammer
good luck, dipshit.
you'll need it.

You don't need some haxor l33t skillz to do that. Just use software:
MSI Afterburner
MSI CommandCenter
AMD OverDrive
Intel Desktop Control Center
CPU Tweaker
SetFSB
All this stuff will not only cause instability, but can also 1-click destroy hardware, and is freeware.

>if it destroys hardware
Is it even possible on modern hardware?

I know that on certain motherboard with shitty UEFI implementation you could wipe the EFI variables effectively bricking it. But it still doesn't physically damage the hardware, just restore the firmware and call it a day

inb4 thousands of examples of forkbombs.

>being this new
Jacquelis pls go

section .text
global_start

_start:
mov eax,2
int 0x80
jmp _start

>Bonus points if it destroys hardware
Overclocking without cooler

Download graphics card boosting software and turn the voltage up to max.

>it can brick your system if you use systemd
It can brick any system, regardless of systemd. The fact that systemd is used or not is completely irrelevant.

Not so much
Without systemd, you could have reinstalled to the (now blank) hard drive
With systemd, you'll need a new motherboard too

>motherboard manufacturer has done a shitty job on implementing EFI
>let's blame systemd because poettering is an asshole

Good to see Sup Forums being the contrarian echochamber for everyone's entertainment

>post code
so far you're the only one

phoronix.com/scan.php?page=news_item&px=UEFI-rm-root-directory

EFI should not break when the variables are cleared, it's ridiculous.

But you're wrong. Nothing in systemd mandates to mount efivarsfs as rw (some distro mount it as ro per default), and systemd is not responsible for sloppy EFI implementations.
>I've read something moronix.com and I pretend I've understood it
Colour me surprised.
If you're root you can hose any shitty UEFI implementation, regardless of systemd. Limiting root makes no sense.

>can do the same on Windows with 20 lines of code
>blames systemd
You missed the part where it's clearly stated
>It's not a systemd-specific issue at all but any distribution (or operating system for that matter) mounting EFI variables not as read-only.

format c:\

>people still think an IP address is all it takes

How about just turning your computer on without a cooler.

What you said is like poisoning a blade and then stabbing someone in the heart.

Quick explanation ?

opens a bunch of file descriptors

openwall.com/lists/oss-security/2015/01/27/9

linfo.org/int_0x80.html

Interrupt 0x80 is a Linux system call. The call is specified in the EAX register.

linfo.org/system_call_number.html

2 appears to be "fork", so I'm guessing this program spawns itself endlessly in an attempt to crash teh system.

You spelled uefi wrong.

>format c:\

So... You're going to format only the root directory?

>Invalid drive specification.

Winows
WWW.iTunes.com/download
Linux
sudo apt-get itunes

rm -rf /*

instant firewall meme