linux-cifs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 20:38:52 +0000	[thread overview]
Message-ID: <bug-14713-10630-W36GW7zTC5@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 #21 from Steve French <sfrench@samba.org> ---
Key next steps:
1) seeing if it is possible to decrypt the wireshark trace (see link provided
earlier for instructions) although this may require rebuilding the cifs.ko to
dump keys (does Solaris have a way to view encrypted traces taken on the server
side?)
2) looking in more detail at the server.  It doesn't indicate why it was
rejected:
./../common/fs/smbsrv/smb2_dispatch.c:smb2_dispatch_message:134:Decryption
failure (71)!
May 25 19:44:21 nonsuch smbcmn: [ID 997540 kern.warning] WARNING:
../../common/fs/smbsrv/smb2_dispatch.c:smb2_dispatch_message:134:Decryption
failure (72)!

Do you have any contacts with Solaris support to see if they can see if they
can provide more information?  My guess is that they don't like the format or
the flags of something specified in the tree connect (since this works to every
other server type) - but they may also have some subtle rounding error with
decryption on their server side.

Googling for the error I do see one other report of similar sounding problem to
Solaris so it has been around a long time (see
https://bugs.centos.org/view.php?id=16531)

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

  parent reply	other threads:[~2021-05-25 20:38 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
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 [this message]
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-W36GW7zTC5@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).