Challenge: post code that causes the most damage to a Windows or Linux machine. Bonus points if it destroys hardware
rm -rf /*
it can brick your system if you use systemd.
>>54596017
Just use a hammer.
>>54596032
Any good asm source code on a row hammer?
Preferably for Linux.
>>54596061
>row hammer
good luck, dipshit.
you'll need it.
>>54596017
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.
>>54596017
>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
>>54596017
inb4 thousands of examples of forkbombs.
>>54596162
>being this new
Jacquelis pls go
section .text
global_start
_start:
mov eax,2
int 0x80
jmp _start
>>54596017
>Bonus points if it destroys hardware
Overclocking without cooler
Download graphics card boosting software and turn the voltage up to max.
>>54596030
>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.
>>54596762
Not so much
Without systemd, you could have reinstalled to the (now blank) hard drive
With systemd, you'll need a new motherboard too
>>54596807
>motherboard manufacturer has done a shitty job on implementing EFI
>let's blame systemd because poettering is an asshole
Good to see /g/ being the contrarian echochamber for everyone's entertainment
>>54596336
>post code
so far you're the only one
>>54596858
https://www.phoronix.com/scan.php?page=news_item&px=UEFI-rm-root-directory
>>54596890
EFI should not break when the variables are cleared, it's ridiculous.
>>54596807
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.
>>54596890
>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.
>>54596890
>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.
>>54596017
format c:\
>>54596017
>people still think an IP address is all it takes
>>54596415
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.
>>54596336
Quick explanation ?
>>54599067
opens a bunch of file descriptors
http://www.openwall.com/lists/oss-security/2015/01/27/9
>>54599067
http://www.linfo.org/int_0x80.html
Interrupt 0x80 is a Linux system call. The call is specified in the EAX register.
http://www.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.
>>54596030
You spelled uefi wrong.
>>54598869
>format c:\
So... You're going to format only the root directory?
>Invalid drive specification.
>>54596017
Winows
WWW.iTunes.com/download
Linux
sudo apt-get itunes
>>54596017
rm -rf /*
instant firewall meme
