Penguins survive weaponised contagion

[serenacat 83]

http://www.reuters.com/article/us-britain-security-hospitals-idUSKBN18820S

https://krebsonsecurity.com/tag/wanna-decryptor/

https://technet.microsoft.com/en-us/library/security/ms17-010.aspx

Linux sysadms get to the pub on a Friday afternoon, and go home for the weekend.

 

No Windows here

[OmniNegro 155]

Thanks again Linux. Being immune to this bullshit is such a blessing. Wonder why this is such a clusterfuck? How did M$ fix this? Lets see...

 

https://technet.microsoft.com/en-us/library/security/ms17-010.aspx

 

And what does the "fix" of disabling SMB do? Lets see again...

 

https://support.microsoft.com/en-us/help/2696547/how-to-enable-and-disable-smbv1,-smbv2,-and-smbv3-in-windows-vista,-windows-server-2008,-windows-7,-windows-server-2008-r2,-windows-8,-and-windows-server-2012

 

In Windows 7 and Windows Server 2008 R2, disabling SMBv2 deactivates the following functionality:

• Request compounding - allows for sending multiple SMB 2 requests as a single network request
• Larger reads and writes - better use of faster networks
• Caching of folder and file properties - clients keep local copies of folders and files
• Durable handles - allow for connection to transparently reconnect to the server if there is a temporary disconnection
• Improved message signing - HMAC SHA-256 replaces MD5 as hashing algorithm
• Improved scalability for file sharing - number of users, shares, and open files per server greatly increased
• Support for symbolic links
• Client oplock leasing model - limits the data transferred between the client and server, improving performance on high-latency networks and increasing SMB server scalability
• Large MTU support - for full use of 10-gigabye (GB) Ethernet
• Improved energy efficiency - clients that have open files to a server can sleep

In Windows 8, Windows 8.1, Windows 10, Windows Server 2012, and Windows Server 2016, disabling SMBv3 deactivates the following functionality (and also the SMBv2 functionality that's described in the previous list):

• Transparent Failover - clients reconnect without interruption to cluster nodes during maintenance or failover
• Scale Out – concurrent access to shared data on all file cluster nodes 
• Multichannel - aggregation of network bandwidth and fault tolerance if multiple paths are available between client and server
• SMB Direct – adds RDMA networking support for very high performance, with low latency and low CPU utilization
• Encryption – Provides end-to-end encryption and protects from eavesdropping on untrustworthy networks
• Directory Leasing - Improves application response times in branch offices through caching
• Performance Optimizations - optimizations for small random read/write I/O

 

Yep. Basically half the networking fails to work. Symlinks die, instead of using HMAC SHA 256, you will be stuck with MD5 again at best, and plenty more bullshit. And on top of that, if you have a really fast connection, even locally, well, it will just plainly not work due to MTU being back to the 1500 cap from decades ago. Thanks M$...

[Guest]

 

Slowly transitioning...

[zhang888 1066]

Exposing dangerous services to the internet is a risky thing. Not only on Windows.

Lots of old *nix platforms were also included in that leak, although not that common these days, but it's not an OS specific issue.

Most of IoT devices are on Linux these days and are still getting hacked when they are poorly isolated.