From: Paulo Alcantara <pc@manguebit.com>
To: "Steinbeißer, Sebastian" <Sebastian.Steinbeisser@lrz.de>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: "regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: Potential smb/dfs regression introduced in kernel 6.6
Date: Sun, 14 Jul 2024 16:12:09 -0300 [thread overview]
Message-ID: <0ff960c2bde0f213cc9b7ef98b993bfb@manguebit.com> (raw)
In-Reply-To: <5210f9e7b720dc1d150bd2ebd9f4edadf39685aa.camel@lrz.de>
Steinbeißer, Sebastian <Sebastian.Steinbeisser@lrz.de> writes:
> Is there any additional information I can provide?
Yes. Please provide again the network traces of both working and
non-working kernels along with the session keys in order to decrypt the
packets.
You can retrieve the session keys by running `smbinfo keys
/mounted/share/some/file` [1].
Make sure you can decrypt the packets with dumped keys before sending
those out.
Besides running ls, try to stat those files as well. If you can provide
network traces with smbclient(2) [2], it would be great, too.
Thanks.
[1] https://wiki.samba.org/index.php/Wireshark_Decryption#Obtaining_the_keys
[2] https://wiki.samba.org/index.php/Wireshark_Decryption#Samba_client_and_server
next prev parent reply other threads:[~2024-07-14 19:20 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-27 13:28 Potential smb/dfs regression introduced in kernel 6.6 Steinbeißer, Sebastian
2024-06-27 13:37 ` Greg KH
[not found] ` <f3a02647b6fcb27a70da4c334930ad3c@manguebit.com>
2024-06-28 8:19 ` Steinbeißer, Sebastian
2024-07-11 6:20 ` Steinbeißer, Sebastian
2024-07-11 7:27 ` gregkh
2024-07-11 15:20 ` Christian Heusel
2024-07-14 19:12 ` Paulo Alcantara [this message]
2024-07-15 5:41 ` Steinbeißer, Sebastian
2024-07-15 12:21 ` Paulo Alcantara
2024-07-15 13:26 ` Steinbeißer, Sebastian
2024-07-15 14:24 ` Paulo Alcantara
2024-07-16 6:14 ` Steinbeißer, Sebastian
2024-07-17 18:24 ` Paulo Alcantara
2024-07-17 20:03 ` Tom Talpey
2024-07-18 5:43 ` Steinbeißer, Sebastian
2024-07-25 1:28 ` Paulo Alcantara
2024-07-26 8:19 ` Steinbeißer, Sebastian
2024-07-26 18:00 ` Paulo Alcantara
2024-07-29 5:57 ` Steinbeißer, Sebastian
2024-07-29 12:34 ` Paulo Alcantara
2024-07-30 5:25 ` Steinbeißer, Sebastian
2024-07-31 2:35 ` Paulo Alcantara
2024-07-31 5:02 ` Steinbeißer, Sebastian
2024-07-31 5:07 ` Steinbeißer, Sebastian
2024-07-31 14:25 ` Paulo Alcantara
2024-08-01 13:07 ` Steinbeißer, Sebastian
2024-08-01 16:25 ` Paulo Alcantara
2024-08-01 19:02 ` Tom Talpey
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=0ff960c2bde0f213cc9b7ef98b993bfb@manguebit.com \
--to=pc@manguebit.com \
--cc=Sebastian.Steinbeisser@lrz.de \
--cc=gregkh@linuxfoundation.org \
--cc=regressions@lists.linux.dev \
/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.