this needs to be fixed to support SMBv2/3 rapidly, inline with guidance from Microsoft for mitigation of WannaCry and future exploits against the SMBv1 protocol. https://blogs.technet.microsoft.com/msrc/2017/05/12/customer-guidance-for-wannacrypt-at...