Exactly. IBM's position is that the NetServer adheres to the official standard. That's of little consequence to the end-users when MS doesn't.
-----Original Message-----
From: Rob Berendt [mailto:rob@xxxxxxxxx]
Sent: Wednesday, June 28, 2017 2:25 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: Netserver SMB V1 and recommendations against ransomware
I'm using SMB 2 on IBM i and have no plans to disable it.
IBM is stuck in a "measuring contest" with Microsoft and doesn't realize that IBM is flashing their squirt gun against MS's fire hose when it comes to file systems support.
So far we've realized that IBM plans on losing this battle so we've been migrating as much off of IBM i file support on to Windows based servers as soon as we can.
Anyone who blames the attacker on why their system is open to a Denial Of Service attack instead of hardening against it has no concept of computers and is in the wrong business.
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: Arco Simonse <arco400@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 06/28/2017 02:56 PM
Subject: Netserver SMB V1 and recommendations against ransomware
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
Hi all,
Several security companies and experts recommend to disable SMB V1 in
addition to the security update MS17-010 for windows (which should have
been applied months ago).
For example:
https://success.trendmicro.com/solution/1117665
https://www.symantec.com/connect/articles/petya-ransomware-next-global-threat
I'm investigating on disabling SMB V1 (both server and client component)
on
my Windows machines, and how that would affect connections with the IFS /
Netserver on the IBM i.
Regarding disabling SMB V1 and enabling SMB V2 on the i, there is a known
problem with SMB V2 between the i and MS windows: Microsoft Windows
Explorer is ignoring a STATUS_NOT_SUPPORTED response that is returned to
it
from the IBM i server on a Change Notify request.
see
http://www-01.ibm.com/support/docview.wss?uid=nas8N1021348
Both IBM and Microsoft seem not willing or able to solve this.
Any thougths of the group?
Best regards,
-Arco
midrange.com
