Recently i built my new file server running on TrueNAS, SMB server serves flawlessly every device and different software clients in my household. Except that Infuse wasn’t happy and server logs revealed that Infuse is still using SMB protocol 3.0.2 and tried to negotiate encryption algorithm AES-128-CCM on a media share that does not require encryption. I only had encryption set to ‘desired’ globally on SMB server. Even in same iphone, i had Apple’s Files app, VLC, nPlayer connected just fine.
I had to adjust SMB server settings to make Infuse happy. At this point SMB protocol version 3.1.1 (SMB3_11) is 9 years old, with this version AES-128-CCM and AES-128-CMAC is no longer suggested as default algorithms for encryption and signing. Is there any particular reason to stay with 3.0.2? For compatibility purpose, 3.1.1 client can still connect to legacy SMB servers that doesn’t upgrade to 3.1.1.
Thanks for considering.
(Edit: i’m running latest version of Infuse Pro on latest versions of iOS and ipadOS)
Currently, the SMB implementation in Infuse negotiates 3.0.2 dialect and doesn’t yet support 3.1.1. This is something that we would like to add but it’s a huge amount of work.
The SMB 3.0.2 dialect supports 128-bit encryption and 1 signing algorithm, whereas 3.1.1 supports 128 & 256-bit encryption algorithms, multiple signing algorithms, and all permutations of both.
The latest macOS Sonoma release supports SMB 3.1.1 dialect when acting as a client, but the macOS SMB server component only accepts 3.0.2 dialect as the maximum version. A 3.1.1 client can still connect to “legacy SMB servers” but that wouldn’t be via the 3.1.1 dialect, as it’s not backward compatible. The client would need to support both 3.0.2 and 3.1.1 dialects.
Regarding negotiating encryption, Infuse advertises that encryption is supported but it’s up to the server whether or not it responds to enable it or not. We don’t require that encryption is enabled, as it adds an overhead to packet processing (which can lead to performance issues when streaming larger files such as videos). Some versions of Windows servers will fail if they are configured with encryption or signing enabled (but not required), and a client claims to not support it.
Overall, there aren’t immediate plans to implement the 3.1.1 dialect, but we have been working on adding support for IAKerberos authentication, as some servers have blocked NTLMv2.
I hope this message finds you well. I am writing to bring to your attention an issue with SMB protocol compatibility in Infuse.
I recently set up an SMB share on a Linux server, which is configured to use SMB 3.1.1 for enhanced security and performance. The setup works flawlessly across multiple devices and applications, including iPad, iPhone, and Windows 11, as well as apps like nPlayer and Fileball. However, Infuse is unable to access the SMB share.
After extensive troubleshooting, I have concluded that the issue lies with Infuse’s lack of support for the SMB 3.1.1 protocol. Downgrading the SMB protocol to a lower version resolves the issue, but this compromises the security and performance benefits offered by SMB 3.1.1.
Given the importance of modern protocol support for secure and efficient media streaming, I kindly request that Infuse add support for SMB 3.1.1 in a future update. While I understand that the performance benefits of newer SMB versions may not always be immediately evident, their role in maintaining compatibility and security standards is critical.
Thank you for your consideration and for creating such a fantastic media player. I look forward to your response and hope to see this improvement implemented soon.
So today infuse is working with Synology NAS on SMB2.
It will be interesting to see what will change when infuse runs on 3.1.1.
What about FTP/WebDAV protocols? does infuse work with current versions from Synology NAS ?
Yes, I know that they are all working now. But I thought of something else. Maybe when connected to SMB 3.1.1., the freezes will disappear during rewind and pause? Maybe that’s the problem today?
When approximately will it be possible to test the beta version with SMB 3.1.1. ?
