From: samba-bugs@samba.org
To: cifs-qa@samba.org
Subject: [Bug 14713] SMBv3 negotiation fails with a Solaris server
Date: Sun, 20 Feb 2022 19:07:45 +0000 [thread overview]
Message-ID: <bug-14713-10630-jr8d9dN2Dp@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 #39 from Richard Flint <richard.flint@gmail.com> ---
Appreciate it has been sometime since this was updated but I just wanted to
update this for completeness. I have tested this on Fedora 35
(5.16.9-200.fc35.x86_64) and can confirm successful negotiation of 3.0 3.0.2
and 3.1.1 with Solaris 11.4 servers both with and without encryption (as
enabled by the seal parameter).
E.g. the following is successful:
//myserver/myshare/myfolder /mnt/myserver/myfolder cifs
noauto,nounix,vers=3.1.1,seal,noserverino,ro,_netdev,noexec,nosuid,perm,nodev,iocharset=utf8,cache=strict,sec=ntlmv2,credentials=/root/password,port=445,context="system_u:object_r:myapp_content_t:s0",forceuid,forcegid,file_mode=0440,dir_mode=0550,uid=1000,gid=1001
0 0
Though noisy. E.g.:
[Sat Feb 19 08:34:30 2022] CIFS: decode_ntlmssp_challenge: authentication has
been weakened as server does not support key exchange
[Sat Feb 19 08:34:30 2022] CIFS: VFS: \\myserver\myshare error -9 on ioctl to
get interface list
[Sat Feb 19 08:34:30 2022] CIFS: VFS: \\myserver\IPC$ smb2_get_dfs_refer: ioctl
error: rc=-19
Intriguingly, despite specifying nounix in the mount, Wireshark shows we are
still sending SMB2_POSIX_EXTENSIONS_CAPABILITY in the Negotiate Protocol
Request - I'm not clear if that is the desired behaviour.
The issue is still reproducible on the latest CentOS 8 Stream release, but that
it works on Fedora 35 makes we wonder if an issue was fixed in the meantime
that never got back-ported to CentOS 8. If that's true, then this isn't really
a fault in the CIFSVFS product itself I think - or maybe it isn't anymore.
--
You are receiving this mail because:
You are the QA Contact for the bug.
next prev parent reply other threads:[~2022-02-20 19:07 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
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 [this message]
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-jr8d9dN2Dp@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.