mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: mixalhs <mike.michalo@gmail.com>
To: linkinjeon@kernel.org, stfrench@microsoft.com
Cc: icb@fastmail.org, senozhatsky@chromium.org, tom@talpey.com,
	chenxiaosong@chenxiaosong.com, ematsumiya@suse.de,
	lsahlber@redhat.com, hyc.lee@gmail.com,
	linux-cifs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/6] ksmbd: verify session setup requests before signing with their key
Date: Wed, 11 Nov 2026 01:17:24 +0700	[thread overview]
Message-ID: <C5746055-5C40-4335-9A30-5522244EBA55@gmail.com> (raw)
In-Reply-To: <20261110165834.28162-1-mike.michalo@gmail.com>

Sashiko’s review has already pointed out some real bugs that will require a V5

I will fix them and send it, will spend extra time verifying everything but if there 
Is any feedback for this version I would appreciate it.

Thanks, 

Michails

      parent reply	other threads:[~2026-11-10 18:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-10 16:58 Michail Andreas Michalopoulos
2026-11-10 16:58 ` [PATCH v4 1/6] ksmbd: verify the signature of session binding requests Michail Andreas Michalopoulos
2026-11-10 16:58 ` [PATCH v4 2/6] ksmbd: sign with the negotiated SMB 3.1.1 signing algorithm Michail Andreas Michalopoulos
2026-11-10 19:30   ` Ian Bridges
2026-11-10 16:58 ` [PATCH v4 3/6] ksmbd: use the channel signing key for session setup on a bound channel Michail Andreas Michalopoulos
2026-11-10 16:58 ` [PATCH v4 4/6] ksmbd: check a request before signing STATUS_NETWORK_SESSION_EXPIRED Michail Andreas Michalopoulos
2026-11-10 16:58 ` [PATCH v4 5/6] ksmbd: use the current command's header for signing in a compound Michail Andreas Michalopoulos
2026-11-10 16:58 ` [PATCH v4 6/6] ksmbd: consume the sequence number of a request on a failed session Michail Andreas Michalopoulos
2026-11-10 18:17 ` mixalhs [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=C5746055-5C40-4335-9A30-5522244EBA55@gmail.com \
    --to=mike.michalo@gmail.com \
    --cc=chenxiaosong@chenxiaosong.com \
    --cc=ematsumiya@suse.de \
    --cc=hyc.lee@gmail.com \
    --cc=icb@fastmail.org \
    --cc=linkinjeon@kernel.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lsahlber@redhat.com \
    --cc=senozhatsky@chromium.org \
    --cc=stfrench@microsoft.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
all inboxes | Powered by JetHome®