linux-cifs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hyunchul Lee <hyc.lee@gmail.com>
To: "Aurélien Aptel" <aaptel@suse.com>
Cc: Steve French <sfrench@samba.org>,
	David Howells <dhowells@redhat.com>,
	kernel-team@lge.com, Namjae Jeon <linkinjeon@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-cifs <linux-cifs@vger.kernel.org>,
	samba-technical@lists.samba.org
Subject: Re: [PATCH v2] cifs: decoding negTokenInit with generic ASN1 decoder
Date: Sat, 22 May 2021 23:17:31 +0900	[thread overview]
Message-ID: <CANFS6bb4AsWjkGCo+pKni_QSCF8M6vFvNiLs--K+2v=zOJ5T_A@mail.gmail.com> (raw)
In-Reply-To: <87o8d4qxyi.fsf@suse.com>

Hi Aurélien,

2021년 5월 21일 (금) 오후 5:43, Aurélien Aptel <aaptel@suse.com>님이 작성:
>
> Hi Hyunchul,
>
> The existence of multiple ASN1 decoder has been a regular complaint,
> this looks nice. Have you tested it against any servers?
>

Yes, I have tested this patch against Windows 10, Samba 4.11.6, and cifsd.
If you have trouble,  you need to rebuild the kernel due to rebuilding
the OID registry.

> I think we need to make sure it works with Windows Server (including
> increased ones with the increased security flag, Steve do you remember
> the name of that flag?) and Samba at least.
>

If you let me know the option, I will try.

> There is the SDC EMEA plugfest coming up, might be a good time to try it
> out against other vendors as well.
>

Yes, but I am not gonna to attend the plugfest because of personal reasons.
Is there any other way to test this against other vendors?

Thanks,
Hyunchul

> 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)
>

  reply	other threads:[~2021-05-22 14:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-21  2:00 [PATCH v2] cifs: decoding negTokenInit with generic ASN1 decoder Hyunchul Lee
2021-05-21  8:43 ` Aurélien Aptel
2021-05-22 14:17   ` Hyunchul Lee [this message]
2021-05-23  2:36   ` Steve French
2021-05-22 20:12 ` kernel test robot
2021-05-22 21:47 ` kernel test robot

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='CANFS6bb4AsWjkGCo+pKni_QSCF8M6vFvNiLs--K+2v=zOJ5T_A@mail.gmail.com' \
    --to=hyc.lee@gmail.com \
    --cc=aaptel@suse.com \
    --cc=dhowells@redhat.com \
    --cc=kernel-team@lge.com \
    --cc=linkinjeon@kernel.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=samba-technical@lists.samba.org \
    --cc=sfrench@samba.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).