Abuse Melding

Je hebt een klacht over de onderstaande posting:

25-05-2017, 12:19 door Anoniem

Voor alle devices waar de leverancier geen updates meer van ondersteund, maar waar je wel de smb.conf kan aanpassen: https://forums.freenas.org/index.php?threads/ugly-mitigation-for-remote-code-execution-vulnerability-in-samba.54791/ En daar staat: Tested "nt pipe support = no" on FreeNAS (smb.conf) configured as AD member server. It does not affect DCERPC over SMB2. Server stayed joined to domain. wbinfo -t succeeded. Null session connections don't work (IPC$ share). This is because the setting nukes ncacn_np support. Guest access to the server is not affected. Conclusion: it appears to be a safe parameter when Samba is configured in "standalone" and "ADS" roles, but you will lose the ability to enumerate shares on the server. You will also lose the ability to modify permissions within the share through the Windows File Explorer (because this is apparently also done over a named pipe). P.S. setting all samba shares as "read only" also mitigates the problem.

Beschrijf je klacht (Optioneel):

captcha