SMB 2.1: Does not support file or packet encryption. Traffic can be signed to verify integrity, but the payload remains readable on the wire if intercepted.
It uses older signing algorithms and is vulnerable to certain man-in-the-middle (MitM) or relay techniques.
It’s also limited to standard TCP port 445 and lacks advanced multichannel or failover capabilities.
Older deployments and default configurations historically allowed unauthenticated guest or null sessions, letting unauthorized network actors read or copy shared data without credentials.
If an attacker compromises a single endpoint on an internal network, SMB 2.1 (running over TCP port 445) is frequently leveraged for lateral movement, credential dumping, and scanning shared administrative/IPC paths.
The list goes on for version 2.1 vulnerabilities, it is much older having been released in 2008. Even SMB version 3.x is a decade old now, but is far more robust, reliable and secure than version 2. Having worked with networking for 30 years I’ve come to appreciate the need for keeping things secure and up to date, and would greatly appreciate being able to keep my network as secure as possible.
Your screenshot shows an SMB error, not SFTP: the NAS refuses access to the SMB share. Disable SMB in the app settings if you only want SFTP, or check the share name and user rights.
The app currently supports SMB 2.0.2/2.1 only. SMB3 needs a different library; I’ll look into it, but this has proven to be extremely difficult in the past. Meanwhile SFTP or WebDAV is a secure alternative.
Thank you kindly good sir Will do, and I’ll let you know soon as I’ve had chance to test it properly. I am mahoosively appreciative for you doing this so promptly, respect
I have tested setting up the SMB connection to my NAS, and the test passed and I was able to save the settings successfully. I then did a test export for last month from a single app. Then on a computer I browsed to the share, successfully unzipped the export, and imported one of the CSV files in to a spreadsheet Many thumbs up as far as I am concerned, it’s working absolutely brilliantly… outstanding good sir
Indeed, although I can say for sure that mine has connected with SMB version 3.0 or higher (as my NAS doesn’t accept connections with earlier versions). I can not tell which version 3.x variant it is using from the logs of this app. And there is no information on whether it tries the highest versions first and then falls back to attempting earlier versions if that fails.
A bit more detail in the connection logs would be nice, and could help greatly if you have problems getting it to connect at any point.
I have no personal experience with other NAS brands, so I don’t know .
Also, on a Synology NAS you cannot set the minimum SMB level to v3 via the user interface. Only v2 and v1. Based on their knowledge base there is apparently a link between v2 and v3, resulting in v2 to be the minimum. Though apparently you can set a v3 minimum by modifying certain samba config files via the CLI. Not sure whether that would cause issues due to the indicated link.
Having the high security settings enabled on my NAS restricts the minimum SMB version to 3.0, and it works great. Lesser version SMB clients are rejected, but all my Raspberry Pi’s, Homey, Laptop, and Android tablet connect with their different flavours of SMB 3.x.x just fine.
VLC running on my iPhone got the boot for trying to use older versions of SMB, and this is the second Homey app to have a similar problem. Both of which now work great using SMB 3 to connect to my NAS. So unless Synology have done something unusual with their SMB implementation, I can’t see a good reason it wouldn’t work.
And it’s not just security. SMB 3.x.x also has better performance with the ability to use multi-channel. And it’s meant to have better reliability and robustness than it’s predecessors.
I am not debating whether or not SMB3 is the preferred option, which it obviously is . I was just saying that on a Synology NAS the choices that you have in the user interface regarding the SMB version are limited.
I was only trying too say I can’t see any reason why the CLI config option would fail to work… unless Synology have done something funky with their SMB implementation.
Apologies… but it was kinda relevant to how the discussion started, about the limited logging information the app provides about the SMB version used and the connection progress.
Thanks for looking into it and pointing that out. My NAS uses SMB 3 exclusively so that’s why I switched to SFTP. I just checked and for some reason (probably me not paying attention) the SMB configuration was still active. Unchecked and saved and sftp immediately started working.
I see you now support SMB v3, so I’ll check if that works too, but as long as I get my data out I’m happy.