ezekiel.incorrigible
Dabbler
- Joined
- Aug 10, 2018
- Messages
- 46
Hi all,
Our office has a printer/scanner that scans to a shared SMB folder (FreeNAS 11.1) over the LAN. The scanner only operates at SMBv1 and the FreeNAS box also has SMB shares for each working group. I had to manually enable SMBv1 to get the scan-to-folder function to work.
I'm not sure how SMB protocol works and if I have introduced a gaping vulnerability hole? Do the FreeNAS/Windows shares operate at the highest protocol version of SMB that they both know? Or does having a single SMBv1 connection drag everything else down? Is an SMBv1 connection between FreeNAS and a printer (which I think has linux based firmware?) introducing vulnerability?
This is pretty adamant that I'm doing the wrong thing and need to throw out the printer?
https://www.ixsystems.com/blog/library/do-not-use-smb1/
Our office has a printer/scanner that scans to a shared SMB folder (FreeNAS 11.1) over the LAN. The scanner only operates at SMBv1 and the FreeNAS box also has SMB shares for each working group. I had to manually enable SMBv1 to get the scan-to-folder function to work.
I'm not sure how SMB protocol works and if I have introduced a gaping vulnerability hole? Do the FreeNAS/Windows shares operate at the highest protocol version of SMB that they both know? Or does having a single SMBv1 connection drag everything else down? Is an SMBv1 connection between FreeNAS and a printer (which I think has linux based firmware?) introducing vulnerability?
This is pretty adamant that I'm doing the wrong thing and need to throw out the printer?
https://www.ixsystems.com/blog/library/do-not-use-smb1/