From: Pavel Shilovsky <piastryyy@gmail.com>
To: Aurelien Aptel <aaptel@suse.com>
Cc: linux-cifs <linux-cifs@vger.kernel.org>
Subject: Re: [PATCH 1/2] smbinfo.rst: document new `keys` command
Date: Thu, 12 Dec 2019 16:25:23 -0800 [thread overview]
Message-ID: <CAKywueRyhs86UfqaXf5ByYLYAB6RxWM5GZSidkgC-2cXhKenOw@mail.gmail.com> (raw)
In-Reply-To: <20191014170625.21643-1-aaptel@suse.com>
пн, 14 окт. 2019 г. в 10:06, Aurelien Aptel <aaptel@suse.com>:
>
> Signed-off-by: Aurelien Aptel <aaptel@suse.com>
> ---
> smbinfo.rst | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/smbinfo.rst b/smbinfo.rst
> index c8f76e6..7413849 100644
> --- a/smbinfo.rst
> +++ b/smbinfo.rst
> @@ -90,6 +90,10 @@ COMMAND
> - File types
> - File flags
>
> +`keys`: Dump session id, encryption keys and decryption keys so that
> +the SMB3 traffic of this mount can be decryped e.g. via wireshark
> +(requires root).
> +
> *****
> NOTES
> *****
> --
> 2.16.4
>
Merged, thanks.
--
Best regards,
Pavel Shilovsky
prev parent reply other threads:[~2019-12-13 0:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-14 17:06 [PATCH 1/2] smbinfo.rst: document new `keys` command Aurelien Aptel
2019-12-13 0:25 ` Pavel Shilovsky [this message]
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=CAKywueRyhs86UfqaXf5ByYLYAB6RxWM5GZSidkgC-2cXhKenOw@mail.gmail.com \
--to=piastryyy@gmail.com \
--cc=aaptel@suse.com \
--cc=linux-cifs@vger.kernel.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).