South Korean Company Nayana to Pay $1 million in Bitcoin After

>>61014951
This is what you get for not keeping software up to date.
Even on Linux.

why dont they just guess each number and letter
combination until they get the key

No one has ever claimed GNU/Linux is immune to malware. It is less likely to suffer from it when used as a home PC OS, but servers and corporate applications are prime targets for malware regardless of operating system.

Funnily enough, this wasn't even GNU/Linux's fault. Nayana was running MULTIPLE things that were TEN YEARS out of date. If they had updated even one time in the last 10 years this could have been avoided.

>>61014951
Oh but WannaCry is fine even though it's literally the exact same story? HAHAHAHAHAHA

Must sting twice as bad, knowing that the ransomers are most likely North Korean.

>"NAYANA's website runs on Linux kernel 2.6.24.2, which was compiled back in 2008. [...] Additionally, NAYANA's website uses Apache version 1.3.36 and PHP version 5.1.4, both of which were released back in 2006. Apache vulnerabilities and PHP exploits are well-known;[...]. The version of Apache NAYANA used is run as a user of nobody(uid=99), which indicates that a local exploit may have also been used in the attack."

This is where they went wrong. Make sure you're keeping your software up-to-date.

>>61016583

Up to date Windows also wasn't affected by Wannacry, dumbass freetard.

File: fedora-no-viruses-650.png (122KB, 640x324px) Image search: [Google]

122KB, 640x324px

>>61016525
>No one has ever claimed GNU/Linux is immune to malware.

>>61016583
>2008

idiots

>>61016615
that's if you keep your system up to date, which isn't the same story with windows

>>61016609
>Up to date Windows also wasn't affected by Wannacry

that has nothing to do with what he said.

The longer your software is out of date, the higher the chance of running into an exploit.

>>61016609
There is a bit of a difference between computers that were two months out of date and 10 years of out date dumbass microshill.

>>61016410
because electricity would cost more than the ransom dummy
did you ever consider how expensive it is to let a bunch of servers bruteforce such a thing for several millennia?

>>61016615
What you expect of a shit called fedora

>>61016609
You have to reboot to update windows

"Nothing will happpen we dont need updates"
kek

File: ubuntu-1604-thumb.jpg (20KB, 470x245px) Image search: [Google]

20KB, 470x245px

This would have most likely never have happened if only they went with Ubuntu Server LTS.

>>61016660
YOU DONT HAVE TO BE SO HURTFUL
Actually if it was aes 256 there would not be enough time left in the universe to do it

>>61016615
Well, if you gib dem monies to Redhat/Suse/Canonical/etc. they can ensure for you... hehehe :^)

>>61016694

>t.canotlodder

File: 1496289619483.jpg (38KB, 800x715px) Image search: [Google]

38KB, 800x715px

>>61016583
>2.6.24.2

>tfw literally just updated from 4.11.3 to 4.11.6
>Took LITERALLY less than 2 minutes including the reboot
What the fuck is wrong with these people, its not even hard to do for fucks sake.

>>61016615
Ubuntu!=fedora

>g-g-guys they j-just had to u-update
>typical thread on /g/
>FUG UPDATIN I DO THAT SHIT MANUALLY HEH I NEVER REBOOT HEH UPDATING BREAKS SHIT HEH
wowza!

This is why you run sudo apt-get update && sudo apt-get dist-upgrade every single goddamn day.

>>61017377
>rebooting after kernel's patches

File: 1449787969871.png (231KB, 391x311px) Image search: [Google]

231KB, 391x311px

>>61017776
>being at computers

>>61016713
>le AES256 fallacy
Yes it would, because at some point in the future hardware would evolve enough to make it a trivial task. Let's say taht you bruteforce it for 3000 years, and then a new technology is invented that allows you to crack it in mere weeks, Then what faggot? What you said couldn't be more wrong.

>>61017744
>wowzeengha!

>>61019004
At best AES256's strength can be reduced to the equivalent of AES128 with quantum computing. You aint going to be cracking it.

>>61019176
>AES256 is gonna be uncrackable until the end of the universe
AHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHA I wonder what life is like when you're this fucking stupid AHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHA

>>61016713
...And then quantum computers come out and Rijndael is kill

>>61017744
If you use ksplice you don't need to reboot

>>61016609
The difference is that you can't update windows.
No, seriously, you literally can't update it, the update service is fucking broken.

>>61019635
Rijndael with 128 bit keys is already kill.

>>61020407
>tfw had to clean reinstall half of my Windows systems when WannaCry hit since WU stopped working IN MARCH
for fucks sake, I'm leaving all the Windows systems disconnected from the internet

>>61020428
I use GNU/Linux on all of my systems except one laptop that I use for gaymes that do not work on wine. Windows is quite painful to use in general.
In order to upgrade that computer I had to use http://download.wsusoffline.net/ (it's FOSS)

>>61020457
>In order to upgrade that computer I had to use http://download.wsusoffline.net/ (it's FOSS)
I know it, it has saved a lot of my machines from clean reinstalls
Still, having to deal with dozens of workarounds for such essential feature it's pure bullshit
Right now W10 has broken a lot of CAD tools for no fucking reason, it has been 3 months like this with no response from MS and most fixes being voodoo magic which might or might not work
I can't wait to ditch anything that doesn't run on GNU/Linux

>>61020505
Have you tried wine? I heard that it was easier to make some applications work with wine than with W10.

Question, can they get in from ANY piece of outdated software? Lets say I'm running Gimp version 2.1, will I get BTFO?

Those linux servers were running software that hadn't been updated in 11 years.

File: 1490541342964.png (7KB, 112x112px)

7KB, 112x112px

>>61014951
>NAYANA's website runs on Linux kernel 2.6.24.2, which was compiled back in 2008.
>U-uh... Our deprecated linux server were exploited... I guess Linux is not that secure after all...

>>61020549
GIMP does not open any TCP connections to my knowledge which means that you should be protected from external threats. However if it has a vulnerability concerning the parsing of an image format and you open an image that makes use of that image format and the vulnerability then you are fucked.

>>61020549
If it has open ports, likely.
GIMP doesn't listen on ports though- remote access is through programs that are actively listening for outside contact.

File: 1498085474470.png (2KB, 255x191px)

2KB, 255x191px

>>61020570
>>61020591
Not him but how about an old game with multiplayer? For example baldur's gate II or alpha centauri

>>61020569
You're already going to have Winlets and Macfags saying HURR REMEMBER THAT TIME LINUX GOT RANSOMWARE

>>61020624
Assuming that it's vulnerable then you are fucked.

>>61016536
>WannaCry is fine
Trillions threads on /g/ is not fine at all

>>61014951
Does it specifically avoid encrypting Firefox or something?