From: samba-bugs@samba.org
To: cifs-qa@samba.org
Subject: [Bug 14713] SMBv3 negotiation fails with a Solaris server
Date: Tue, 25 May 2021 19:03:09 +0000 [thread overview]
Message-ID: <bug-14713-10630-KXEmdYSK05@https.bugzilla.samba.org/> (raw)
In-Reply-To: <bug-14713-10630@https.bugzilla.samba.org/>
https://bugzilla.samba.org/show_bug.cgi?id=14713
--- Comment #10 from Steve French <sfrench@samba.org> ---
Since the Solaris server logs:
May 24 23:09:46 nonsuch smbcmn: [ID 997540 kern.warning] WARNING:
../../common/fs/smbsrv/smb2_dispatch.c:smb2_dispatch_message:134:Decryption
failure (71)!
are you sure that you mounted without encryption (ie did not specify "seal=" on
mount)?
If this connection is defaulting to encryption whether or not the client
specifies it on mount, that implies that the server is configured with
encryption as required ... which is odd - because the server allowed vers=2.1
(which is not encrypted, encryption was added in the SMB3 and later versions of
the protocol and not supported with SMB2.1) but fails with vers=3.0 or 3.1.1
(smb3.1.1 is the typical default) which presumably means the server is
negotiating with encryption required (but only for a subset of dialects).
Strange server configuration.
Can you send or attach the vers=3.1.1 (or default with no vers= specified)
wireshark trace so we can see what crypto algorithm the server is defaulting to
(even if we can't see the keys - we can see how it is trying to encrypt/decrypt
if smb3.1.1 is used instead of smb3.0)
--
You are receiving this mail because:
You are the QA Contact for the bug.
next prev parent reply other threads:[~2021-05-25 19:03 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-14713-10630@https.bugzilla.samba.org/>
2021-05-25 14:14 ` [Bug 14713] SMBv3 negotiation fails with a Solaris server samba-bugs
2021-05-25 18:19 ` samba-bugs
2021-05-25 18:26 ` samba-bugs
2021-05-25 18:51 ` samba-bugs
2021-05-25 19:03 ` samba-bugs [this message]
2021-05-25 19:09 ` samba-bugs
2021-05-25 19:09 ` samba-bugs
2021-05-25 19:13 ` samba-bugs
2021-05-25 19:19 ` samba-bugs
2021-05-25 19:27 ` samba-bugs
2021-05-25 19:37 ` samba-bugs
2021-05-25 19:42 ` samba-bugs
2021-05-25 19:43 ` samba-bugs
2021-05-25 19:47 ` samba-bugs
2021-05-25 20:31 ` samba-bugs
2021-05-25 20:38 ` samba-bugs
2021-05-25 20:55 ` samba-bugs
2021-05-25 21:40 ` samba-bugs
2021-05-25 22:33 ` samba-bugs
2021-05-26 8:57 ` samba-bugs
2021-05-26 9:00 ` samba-bugs
2021-05-26 9:47 ` samba-bugs
2021-05-26 15:36 ` samba-bugs
2021-05-26 18:59 ` samba-bugs
2021-05-26 21:51 ` samba-bugs
2021-05-26 21:54 ` samba-bugs
2021-05-26 22:09 ` samba-bugs
2021-05-26 22:26 ` samba-bugs
2021-05-26 22:39 ` samba-bugs
2021-05-27 17:33 ` samba-bugs
2021-05-30 13:51 ` samba-bugs
2021-06-04 6:42 ` samba-bugs
2021-06-04 10:17 ` samba-bugs
2022-02-20 19:07 ` samba-bugs
2022-05-11 18:46 ` samba-bugs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-14713-10630-KXEmdYSK05@https.bugzilla.samba.org/ \
--to=samba-bugs@samba.org \
--cc=cifs-qa@samba.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.