From: Enzo Matsumiya <ematsumiya@suse.de>
To: linux-cifs@vger.kernel.org
Cc: smfrench@gmail.com, pc@cjr.nz, ronniesahlberg@gmail.com,
nspmangalore@gmail.com, tom@talpey.com, metze@samba.org
Subject: [PATCH v4 0/8] cifs: introduce support for AES-GMAC signing
Date: Thu, 29 Sep 2022 17:36:48 -0300 [thread overview]
Message-ID: <20220929203652.13178-1-ematsumiya@suse.de> (raw)
v4:
Patches 3/8 and 6/8:
- fix checkpatch errors (thanks to Steve)
Patch 5/8:
- rename smb311_calc_signature to smb311_calc_aes_gmac, and use SMB3_AES_GCM_NONCE
instead of hardcoded '12' (suggested by metze)
- update commit message to include the reasoning to move ->calc_signature op
Patch 8/8:
- move SMB2_PADDING_BUF to smb2glob.h
- check if iov is SMB2_PADDING_BUF in the free functions where
smb2_padding was previously used (pointed out by metze)
Enzo Matsumiya (8):
smb3: rename encryption/decryption TFMs
cifs: secmech: use shash_desc directly, remove sdesc
cifs: allocate ephemeral secmechs only on demand
cifs: create sign/verify secmechs, don't leave keys in memory
cifs: introduce AES-GMAC signing support for SMB 3.1.1
cifs: deprecate 'enable_negotiate_signing' module param
cifs: show signing algorithm name in DebugData
cifs: use MAX_CIFS_SMALL_BUFFER_SIZE-8 as padding buffer
fs/cifs/cifs_debug.c | 7 +-
fs/cifs/cifsencrypt.c | 157 ++++-------
fs/cifs/cifsfs.c | 14 +-
fs/cifs/cifsglob.h | 70 +++--
fs/cifs/cifsproto.h | 5 +-
fs/cifs/link.c | 13 +-
fs/cifs/misc.c | 49 ++--
fs/cifs/sess.c | 12 -
fs/cifs/smb1ops.c | 6 +
fs/cifs/smb2glob.h | 15 ++
fs/cifs/smb2misc.c | 29 +-
fs/cifs/smb2ops.c | 102 ++-----
fs/cifs/smb2pdu.c | 77 ++++--
fs/cifs/smb2pdu.h | 2 -
fs/cifs/smb2proto.h | 13 +-
fs/cifs/smb2transport.c | 581 +++++++++++++++++++++-------------------
16 files changed, 577 insertions(+), 575 deletions(-)
--
2.35.3
next reply other threads:[~2022-09-29 20:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 20:36 Enzo Matsumiya [this message]
2022-09-29 20:36 ` [PATCH v4 1/8] smb3: rename encryption/decryption TFMs Enzo Matsumiya
2022-10-04 18:49 ` Paulo Alcantara
2022-09-29 20:36 ` [PATCH v4 2/8] cifs: secmech: use shash_desc directly, remove sdesc Enzo Matsumiya
2022-10-04 18:50 ` Paulo Alcantara
2022-10-05 8:04 ` Steve French
2022-09-29 20:36 ` [PATCH v4 4/8] cifs: create sign/verify secmechs, don't leave keys in memory Enzo Matsumiya
2022-09-29 20:36 ` [PATCH v4 7/8] cifs: show signing algorithm name in DebugData Enzo Matsumiya
2022-09-30 3:03 ` [PATCH v4 0/8] cifs: introduce support for AES-GMAC signing Steve French
2022-09-30 3:12 ` Steve French
2022-09-30 3:27 ` Enzo Matsumiya
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=20220929203652.13178-1-ematsumiya@suse.de \
--to=ematsumiya@suse.de \
--cc=linux-cifs@vger.kernel.org \
--cc=metze@samba.org \
--cc=nspmangalore@gmail.com \
--cc=pc@cjr.nz \
--cc=ronniesahlberg@gmail.com \
--cc=smfrench@gmail.com \
--cc=tom@talpey.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox