From: "Aurélien Aptel" <aaptel@suse.com>
To: Stefan Metzmacher <metze@samba.org>,
Steve French <smfrench@gmail.com>,
CIFS <linux-cifs@vger.kernel.org>
Cc: samba-technical <samba-technical@lists.samba.org>
Subject: Re: [PATCH][SMB3.1.1] Add defines for new signing context
Date: Mon, 12 Oct 2020 11:50:24 +0200 [thread overview]
Message-ID: <87r1q3hixr.fsf@suse.com> (raw)
In-Reply-To: <bd8f21ed-5fd4-0974-f15a-16d2f3ee607f@samba.org>
Patch LGTM
Reviewed-by: Aurelien Aptel <aaptel@suse.com>
Stefan Metzmacher via samba-technical <samba-technical@lists.samba.org>
> This isn't in MS-SMB2 yet.
>
> Is this AES_128?
This is returned in latest Windows Server Insider builds but it's not
documented yet.
https://www.microsoft.com/en-us/software-download/windowsinsiderpreviewserver
I've asked dochelp about it during the SDC plugfest and they gave me
this:
The new ContextType is:
SMB2_SIGNING_CAPABILITIES 0x0008
The Data field contains a list of signing algorithms.
• It adds a new negotiate context, which enables SMB to decouple signing algorithms from dialects. E.g. if both client and server supports it, a session may use HMAC-SHA256 with SMB 3.1.1.
• It adds the AES-GMAC algorithm.
SigningAlgorithmCount (2 bytes): Count of signing algorithms
SigningAlgorithms (variable): An array of SigningAlgorithmCount 16-bit integer IDs specifying the supported signing algorithms.
The following IDs are assigned:
0 = HMAC-SHA256
1 = AES-CMAC
2 = AES-GMAC
I've been CCed in a Microsoft email thread later on and it seems to be
unclear why this was missed/wasn't documented. Maybe this is subject to
change so take with a grain of salt.
Cheers,
--
Aurélien Aptel / SUSE Labs Samba Team
GPG: 1839 CB5F 9F5B FB9B AA97 8C99 03C8 A49B 521B D5D3
SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nürnberg, DE
GF: Felix Imendörffer, Mary Higgins, Sri Rasiah HRB 247165 (AG München)
next prev parent reply other threads:[~2020-10-12 9:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-11 1:25 [PATCH][SMB3.1.1] Add defines for new signing context Steve French
2020-10-12 8:55 ` Stefan Metzmacher
2020-10-12 9:50 ` Aurélien Aptel [this message]
2020-10-15 18:15 ` Tom Talpey
2020-10-16 4:50 ` Steve French
2020-10-16 5:49 ` Steve French
2020-10-16 6:11 ` ronnie sahlberg
2020-10-16 14:27 ` Tom Talpey
2020-11-10 8:42 ` Stefan Metzmacher
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=87r1q3hixr.fsf@suse.com \
--to=aaptel@suse.com \
--cc=linux-cifs@vger.kernel.org \
--cc=metze@samba.org \
--cc=samba-technical@lists.samba.org \
--cc=smfrench@gmail.com \
/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.