From: Wang Zhaolong <wangzhaolong3@outlook.com>
To: Ralph Boehme <slow@samba.org>,
Stefan Metzmacher <metze@samba.org>,
Namjae Jeon <linkinjeon@kernel.org>,
Jan Koester <jan.koester@gmx.net>
Cc: linux-cifs@vger.kernel.org,
Sergey Senozhatsky <senozhatsky@chromium.org>,
samba-technical@lists.samba.org, linux-kernel@vger.kernel.org,
Tom Talpey <tom@talpey.com>, Wang Zhaolong <wangzhaolong@fygo.io>,
ChenXiaoSong <chenxiaosong@chenxiaosong.com>,
wang zhaolong <wangzhaolong@fnnas.com>
Subject: Re: [PATCH 0/2] ksmbd: NTLM pass-through to a domain controller
Date: Tue, 20 Oct 2026 23:51:59 +0800 [thread overview]
Message-ID: <TYZPR02MB6959812BFC392957EDDA8C67E6672@TYZPR02MB6959.apcprd02.prod.outlook.com> (raw)
In-Reply-To: <9b5b0f6c-9105-4e30-8608-6f222b0e2a6e@samba.org>
Hi Ralph,
> may I ask: why? What's the benefit over using something mature and Open Source that already does all that and more?
>
> Just curious. :)
>
> Cheers!
> -slow
Fair question! :)
When I first had this idea, integration between ksmbd and Samba's AD services
was still fairly limited, so I started thinking about a more tightly
integrated solution for ksmbd-based NAS systems.
It's great to see the community making progress on this, including Jan's
recent patches. I'm happy to see that happening.
At the same time, I'd still like to try something different: a small,
Rust-based AD DC built with ksmbd in mind. I don't know yet whether it'll offer
any real advantages over Samba, but I think it's worth exploring.
Cheers,
Wang Zhaolong
next prev parent reply other threads:[~2026-10-20 15:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-18 17:53 Jan Koester
2026-10-18 17:53 ` [PATCH 1/2] ksmbd: pass through NTLM authentication " Jan Koester
2026-10-19 1:48 ` Namjae Jeon
2026-10-18 17:53 ` [PATCH 2/2] ksmbd: put the workgroup into the NTLMSSP target info's domain names Jan Koester
2026-10-19 2:00 ` Namjae Jeon
2026-10-19 1:31 ` [PATCH 0/2] ksmbd: NTLM pass-through to a domain controller Namjae Jeon
2026-10-19 10:43 ` Stefan Metzmacher
2026-10-19 13:02 ` Namjae Jeon
2026-10-20 13:54 ` Wang Zhaolong
2026-10-20 14:24 ` Ralph Boehme
2026-10-20 15:51 ` Wang Zhaolong [this message]
2026-10-21 8:56 ` Namjae Jeon
2026-10-20 19:40 ` ronnie sahlberg
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=TYZPR02MB6959812BFC392957EDDA8C67E6672@TYZPR02MB6959.apcprd02.prod.outlook.com \
--to=wangzhaolong3@outlook.com \
--cc=chenxiaosong@chenxiaosong.com \
--cc=jan.koester@gmx.net \
--cc=linkinjeon@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=metze@samba.org \
--cc=samba-technical@lists.samba.org \
--cc=senozhatsky@chromium.org \
--cc=slow@samba.org \
--cc=tom@talpey.com \
--cc=wangzhaolong@fnnas.com \
--cc=wangzhaolong@fygo.io \
/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®