/cyb/ - cyberpunk and cybersecurity

this is what you get for windows soykaffery. the victims should just pay the ransom out of shame.

>>348
It's unfortunate, but it's unfortunate that the state chooses to use and endorse closed-source software. That's incompatible with being a transparent state.

>>350
>>351
>>352
As if this wouldn't have happened if Ganoo/Linux was on most computers instead of Windows.

>>353
It might have, but it would be far rarer and easier to fix. We're not just fanbois, there's solid logic behind the wonders of open sauce.

>>355
This ransomware only spread because fucking idiot admins were running dangerously out of date client/server OS's, had neglected doing any updates on the machines running current OS's, and exposed protocols to the internet that should never, EVER leave a LAN.

Even if Linux was the norm and Windows the exception these Sysadmin sins would have still lead these enterprises to being compromised.

In the same dumps that yielded DoublePulsar and EternalBlue (the NSA sploits that resulted in WannaCry) we also received sploits for Linux that target older kernel versions and critical services.

In my work I still see relatively modern CentOS boxes get rootkitted because their admins either left weak creds or left software out of date.

Be glad that Windows exists, that most enterprises use it and that malware authors can't be bothered targeting Linux… Most of the time.

A laymans explaination about the inner details of Wannacry, very interesting read.
>http://blog.talosintelligence.com/2017/05/wannacry.html#more

Also who do you think is behind these attacks? Some news outlets say that parts of the Wannacry code has similarities with previous attempts done by NorthK, and thus this was the doing of nork hackers, but who knows right?

>>353
>>355
>wouldn't have happened if Ganoo/Linux was on most computers
From what I hear, lots of hospital equipment are built on os'es that can't be updated regularly or have software that was specifically made with a certain os in mind. So even if new equipment were built atop linux, frequent security updates might be hard.

>>361

Remember when grub was compromised by hitting backspace 28 times?

>>365
Yeap.

Also, remember Heartbleed?

There are still servers out there vulnerable to it.

>>365

That GRUB vulnerability required the attacker to have physical access to the computer. If they've already got that, and if there's no full-disk encryption (which is a fully-effective defence against that bug) then it's game over anyway.

No-one caught that bug because no-one is dumb enough to think that GRUB passwords are any sort of defence.

>>379
Still a good example how FOSS software doesn't have perfect security. We've had our fair share of silly vulnerabilities, although I'm not comfortable saying whether the Linux ecosystem or the Windows ecosystem had more.

But that's not the main takeaway from this story. The main takeaway is that you need to be vigilant, stay on top of things (i.e. having offline backups) and keep your system up-to-date and patched.

>>350
I've been reading Stallman's biography. Really interesting.

It's free on the Oreilly website. It's called Free as in Freedom: Richard Stallmans Crusade for Free Software.

>>351
Got so bad even Windows had to patch earlier versions, despite saying they were not going to.

>>363
Thanks for Sharing. Although, I think security updates would be much easier managed under Linux than Windows.

>>380
I agree with you, but I'd put it this way: there are no best security practices and safe solutions, you need constant attention and constant thought put into security for it to last.
It's hard to stop at this point, but saying anything particular after that sentence makes the statement less true.