https://bugzilla.samba.org/show_bug.cgi?id=14713 --- Comment #24 from Steve French <sfrench@xxxxxxxxx> --- The reason that it is of some value is that if wireshark can decrypt it and shows no errors (ie decrypt the first encrypted frame, the SMB3.1.1 tree connect request) then it is even more likely a server bug ... (perhaps some strange case where they expect a padded response that has a length divisible by 8 or some such bug) if you have access to the source RPM then rebuilding it might only take a few minutes (you could e.g. just remove the 2 ifdef CONFIG_CIFS_DEBUG_DUMP_KEYS in fs/cifs/smb2transport.c e.g. remove the ifdef and endif here (and the one before that in the same file) #ifdef CONFIG_CIFS_DEBUG_DUMP_KEYS cifs_dbg(VFS, "%s: dumping generated AES session keys\n", __func__); /* * The session id is opaque in terms of endianness, so we can't * print it as a long long. we dump it as we got it on the wire */ cifs_dbg(VFS, "Session Id %*ph\n", (int)sizeof(ses->Suid), &ses->Suid); cifs_dbg(VFS, "Cipher type %d\n", server->cipher_type); cifs_dbg(VFS, "Session Key %*ph\n", SMB2_NTLMV2_SESSKEY_SIZE, ses->auth_key.response); cifs_dbg(VFS, "Signing Key %*ph\n", SMB3_SIGN_KEY_SIZE, ses->smb3signingkey); if ((server->cipher_type == SMB2_ENCRYPTION_AES256_CCM) || (server->cipher_type == SMB2_ENCRYPTION_AES256_GCM)) { cifs_dbg(VFS, "ServerIn Key %*ph\n", SMB3_GCM256_CRYPTKEY_SIZE, ses->smb3encryptionkey); cifs_dbg(VFS, "ServerOut Key %*ph\n", SMB3_GCM256_CRYPTKEY_SIZE, ses->smb3decryptionkey); } else { cifs_dbg(VFS, "ServerIn Key %*ph\n", SMB3_GCM128_CRYPTKEY_SIZE, ses->smb3encryptionkey); cifs_dbg(VFS, "ServerOut Key %*ph\n", SMB3_GCM128_CRYPTKEY_SIZE, ses->smb3decryptionkey); } #endif -- You are receiving this mail because: You are the QA Contact for the bug.
