Enabling SMB signing for SMB service instances

Products

• VMware Tanzu Application Service

Issue/Introduction

This KB article goes over the steps to enable SMB signing using the SMB Volume service. By default, this capability is not available for any TAS versions that are using smb-volume release 3.17.0 or lower. Support for SMB signing is only included in smb-volume release version 3.18.0 or above.

Because there is no support for the sec parameter to enable SMB signing, we will encounter this issue below if we try to pass in the sec parameter when binding an app to an existing SMB volume service: 

failed: bind could not be completed: Service broker error: - Not allowed options: sec

smb-volume-release only supports SMB versions 1.0, 2.0, 2.1, 3.0, 3.1.1, however SMB version 3.2 is unsupported at this time.

TAS versions with smb-volume-release 3.18.0 or above should be included in the following future releases:

• TPCF 10.0.3
• TAS 4.0.33
• TAS 6.0.13

Environment

TAS version 4.0.33+

TAS version 6.0.13+

TPCF version 10.0.3+

Resolution

Workaround: Upgrade TAS / TPCF to one of these versions that has smb-volume-release 3.18.0 included natively. As of January 31st 2025, these versions of TAS have yet to be released: 

• TPCF 10.0.3
• TAS 4.0.33
• TAS 6.0.13