From: samba-bugs@samba.org
To: cifs-qa@samba.org
Subject: [Bug 14509] Interworking Problem OpenVMS Samba Server 4.6.5 with Linux Samba Client 4.7.6
Date: Wed, 23 Sep 2020 07:28:29 +0000 [thread overview]
Message-ID: <bug-14509-10630-Um9Ihjr35k@https.bugzilla.samba.org/> (raw)
In-Reply-To: <bug-14509-10630@https.bugzilla.samba.org/>
https://bugzilla.samba.org/show_bug.cgi?id=14509
--- Comment #9 from John Dite <john.dite@compinia.de> ---
It's not a 100% clear for me.
If "filename MUST be at least one character but no more than 255 characters in
length" why does it not lead to a protocol violation on the part of the Linux
Client SMB state M/C. I don't see that in my Wireshark trace.
--
You are receiving this mail because:
You are the QA Contact for the bug.
next prev parent reply other threads:[~2020-09-23 7:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-14509-10630@https.bugzilla.samba.org/>
2020-09-22 14:45 ` [Bug 14509] Interworking Problem OpenVMS Samba Server 4.6.5 with Linux Samba Client 4.7.6 samba-bugs
2020-09-22 15:02 ` samba-bugs
2020-09-22 15:02 ` samba-bugs
2020-09-22 21:26 ` samba-bugs
2020-09-22 21:53 ` samba-bugs
2020-09-22 23:07 ` samba-bugs
2020-09-22 23:09 ` samba-bugs
2020-09-23 7:28 ` samba-bugs [this message]
2020-10-01 10:03 ` 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-14509-10630-Um9Ihjr35k@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.