Hello Jo, Have you used the new IDL file from the updated MS-NRPC specification? Please feel free to collect the data and upload it to the workspace shared with you.
Regards, Sreekanth Nadendla Microsoft Windows Open Specifications ________________________________ From: Jo Sutton <jsut...@samba.org> Sent: Friday, July 19, 2024 12:31 AM To: Sreekanth Nadendla <srena...@microsoft.com>; cifs-protocol@lists.samba.org <cifs-protocol@lists.samba.org> Cc: Microsoft Support <supportm...@microsoft.com> Subject: [EXTERNAL] Re: [cifs-protocol] [MS-APDS] NETLOGON_TICKET_LOGON_INFO message - TrackingID#2405210040011397 Hi Sreekanth, Thank you for your helpful response! It seems I still haven’t got it quite right, as Windows responds with RPC_NT_BAD_STUB_DATA when I send the NetlogonTicketLogonInformation message. May I upload more traces next week so I can find out where I’ve gone wrong? Cheers, Jo (she/her) On 19/07/24 6:40 am, Sreekanth Nadendla wrote: > Hello Jo, please review the latest copy of [MS-NRPC]. It has the > updated IDL definitions as well. As of now, [MS-APDS] is still being > updated. The following information should be helpful in the meantime. > > MS-APDS Section 3.2.5.1 shows messagetype field should be set to > 0x00000026. The actual design did not introduce such message type. We > are using a new logonlevel i.e. NETLOGON_LEVEL of > NetlogonTicketLogonInformation and a new validationLevel i.e. > NETLOGON_VALIDATION of NetlogonValidationTicketLogon. > > 1. > From MS-APDS Section 3.2.5.1, we see the > NETLOGON_TICKET_LOGON_INFO is layered on top of generic pass > through structure however MS-NRPC section 2.2.1.4.6 defines > TicketLogon as a new NETLOGON_LEVEL struct which refers > to NETLOGON_TICKET_LOGON_INFO. > The NETLOGON_TICKET_LOGON_INFO message does not utilize > Generic Passthrough as described in MS-APDS 3.2.5.1. Instead, you > will be using /LogonLevel/ parameter 8 > (_NetlogonTicketLogonInformation > > <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flearn.microsoft.com%2Fen-us%2Fopenspecs%2Fwindows_protocols%2Fms-nrpc%2F8c7808e5-4e5c-420e-9c90-47286da2218f&data=05%7C02%7Csrenaden%40microsoft.com%7C2515a7bc13144af3cc4508dca7abc215%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638569603359118378%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=%2FtE6Ss0vWtLxTmXsBSe5ohH1goBxxe2Y3V0B0sw6Grk%3D&reserved=0>_<https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-nrpc/8c7808e5-4e5c-420e-9c90-47286da2218f>) > 1. > > 2. > Generic Passthrough returns > NETLOGON_VALIDATION_GENERIC_INFO2. But the new TicketLogon will > return NETLOGON_VALIDATION_TICKET_LOGON. > 1. > As NETLOGON_TICKET_LOGON_INFO message does not actually utilize > Generic Passthrough, you will use /ValidationLevel/ parameter is > 7 (_NetLogonValidationTicketLogon > > <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flearn.microsoft.com%2Fen-us%2Fopenspecs%2Fwindows_protocols%2Fms-nrpc%2F95154ae4-d305-43e5-82e4-d5353e0f117c&data=05%7C02%7Csrenaden%40microsoft.com%7C2515a7bc13144af3cc4508dca7abc215%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638569603359128324%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=HEAC75E4vE%2FFZ1zNL%2FybUhn2cuJWnBwK7kF5eCiJ5fA%3D&reserved=0>_<https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-nrpc/95154ae4-d305-43e5-82e4-d5353e0f117c>), > 1. > > 2. > > You can find a list of applicable Windows OS versions that have this > security update from the following link (click the “More…” link below > the title) > > 3. > > _https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Ftopic%2Fkb5037754-how-to-manage-pac-validation-changes-related-to-cve-2024-26248-and-cve-2024-29056-6e661d4f-799a-4217-b948-be0a1943fef1&data=05%7C02%7Csrenaden%40microsoft.com%7C2515a7bc13144af3cc4508dca7abc215%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638569603359131478%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=lGbdEN3ijr6GYYLFlXxh59zHmrZX4EPcCxraajgVBmY%3D&reserved=0 > > <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Ftopic%2Fkb5037754-how-to-manage-pac-validation-changes-related-to-cve-2024-26248-and-cve-2024-29056-6e661d4f-799a-4217-b948-be0a1943fef1&data=05%7C02%7Csrenaden%40microsoft.com%7C2515a7bc13144af3cc4508dca7abc215%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638569603359134592%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=Xzicp6rrAiWgKaKG78mgejCwXErzG%2BktBsTJBGvPAtQ%3D&reserved=0<https://support.microsoft.com/en-us/topic/kb5037754-how-to-manage-pac-validation-changes-related-to-cve-2024-26248-and-cve-2024-29056-6e661d4f-799a-4217-b948-be0a1943fef1>>_ > > This list does not include Server 2025, but it also contains this > update. > > > Please let me know if you have additional questions. > > Regards, > > Sreekanth Nadendla > > Microsoft Windows Open Specifications > > > ------------------------------------------------------------------------ > *From:* Jo Sutton <jsut...@samba.org> > *Sent:* Tuesday, July 16, 2024 12:33 AM > *To:* Sreekanth Nadendla <srena...@microsoft.com>; > cifs-protocol@lists.samba.org <cifs-protocol@lists.samba.org> > *Cc:* Microsoft Support <supportm...@microsoft.com> > *Subject:* Re: [cifs-protocol] [EXTERNAL] Re: [MS-APDS] > NETLOGON_TICKET_LOGON_INFO message - TrackingID#2405210040011397 > For completeness’ sake, I ran the same procedure against a Windows > Server 2022 host, and got exactly the same STATUS_INVALID_PARAMETER > error. For MessageType I tried both 0x00000003 and 0x00000026 (and many > other values, for good measure). > > Cheers, > Jo (she/her) > > On 10/07/24 2:08 pm, Jo Sutton via cifs-protocol wrote: > > Hi Sreekanth, > > > > I’m afraid that using 0x03 for the message type still gets me > > STATUS_INVALID_PARAMETER codes. > > > > 0x03 is the message type corresponding to KERB_VERIFY_PAC_REQUEST, which > > is used for the older method of PAC verification. But the message I’m > > attempting to send is NETLOGON_TICKET_LOGON_INFO ([MS-APDS] 2.2.2.1), > > which includes the entire Kerberos ticket and is used in the newer > > method of PAC verification. > > > > What do I need to do to get Windows Server 2019 to accept a > > NETLOGON_TICKET_LOGON_INFO message? I don’t see any information > > indicating that Windows Server 2019 doesn’t support such messages. > > > > Cheers, > > Jo (she/her) > > > > On 10/07/24 7:12 am, Sreekanth Nadendla wrote: > >> Hello Jo, can you change the message type from 0x00000026 ( byte > >> sequence seen as 26 00 00 00 below) to 0x00000003 (to indicate > >> message type of KerbVerifyPacMessage) and try this again ? > >> > >> 0:002> db ProtocolSubmitBuffer L0x5e0 > >> > >> 00000218`69819c80 26 00 00 00 00 00 11 00-21 00 31 00 c0 05 00 00 > >> &.......!.1..... > >> 00000218`69819c90 00 00 02 00 00 00 00 00-00 00 00 00 c0 05 00 00 > >> ................ > >> 00000218`69819ca0 61 82 05 bc 30 82 05 b8-a0 03 02 01 05 a1 0d 1b > >> a...0........... > >> .. ..... .. ..... .. ..... > >> .. ..... .. ..... .. ..... > >> .. ..... .. ..... .. ..... > >> 00000218`6981a250 85 1d 35 87 38 7d b1 5b-52 c0 c3 e4 30 c8 77 7d > >> ..5.8}.[R...0.w} > >> > >> Regards, > >> > >> Sreekanth Nadendla > >> > >> Microsoft Windows Open Specifications > >> > >> > >> ------------------------------------------------------------------------ > >> *From:* Jo Sutton <jsut...@samba.org> > >> *Sent:* Tuesday, July 2, 2024 6:23 PM > >> *To:* Sreekanth Nadendla <srena...@microsoft.com>; > >> cifs-protocol@lists.samba.org <cifs-protocol@lists.samba.org> > >> *Cc:* Microsoft Support <supportm...@microsoft.com> > >> *Subject:* [EXTERNAL] Re: [cifs-protocol] [MS-APDS] > >> NETLOGON_TICKET_LOGON_INFO message - TrackingID#2405210040011397 > >> Thank you, Sreekanth. I’ve uploaded a trace and network capture of a > >> call to NetrLogonSamLogonEx() attempting to validate a service ticket. > >> > >> Cheers, > >> Jo (she/her) > >> > >> On 3/07/24 2:02 am, Sreekanth Nadendla wrote: > >> > Hello Jo, you may have gotten an invitation to upload files by now. > >> > Please check your e-mail folders and let me know otherwise. > >> > > >> > Regards, > >> > > >> > Sreekanth Nadendla > >> > > >> > Microsoft Windows Open Specifications > >> > > >> > > >> ------------------------------------------------------------------------ > >> > *From:* Jo Sutton <jsut...@samba.org> > >> > *Sent:* Monday, July 1, 2024 10:01 PM > >> > *To:* Sreekanth Nadendla <srena...@microsoft.com>; > >> > cifs-protocol@lists.samba.org <cifs-protocol@lists.samba.org> > >> > *Cc:* Microsoft Support <supportm...@microsoft.com> > >> > *Subject:* [EXTERNAL] Re: [cifs-protocol] [MS-APDS] > >> > NETLOGON_TICKET_LOGON_INFO message - TrackingID#2405210040011397 > >> > On second thoughts, I’d rather not send traces via unencrypted email. > >> > Can you provide somewhere for me to upload them? > >> > > >> > Cheers, > >> > Jo (she/her) > >> > > >> > On 2/07/24 1:57 pm, Jo Sutton via cifs-protocol wrote: > >> >> [moving back to cifs-protocol] > >> >> > >> >> Hi Sreekanth, > >> >> > >> >> Call me Jo :) > >> >> > >> >> As I can’t seem to upload the traces via the link you sent me, > >> I’ll try > >> >> to email them to you directly. > >> >> > >> >> The reason for asking about NETLOGON_TICKET_LOGON_INFO is that we’re > >> >> looking to address > >> > https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugzilla.samba.org%2Fshow_bug.cgi%3Fid%3D15249&data=05%7C02%7Csrenaden%40microsoft.com%7C2515a7bc13144af3cc4508dca7abc215%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638569603359137640%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=7XY3SGgdQpHefyyQ%2F9Ty2l0sjhU9spfRNiJXzdurNdU%3D&reserved=0<https://bugzilla.samba.org/show_bug.cgi?id=15249> > > <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugzilla.samba.org%2Fshow_bug.cgi%3Fid%3D15249&data=05%7C02%7Csrenaden%40microsoft.com%7C2515a7bc13144af3cc4508dca7abc215%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638569603359140497%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=P7Er2U7F%2FiCKPw%2B6F4JlERaJeZe038mtuGXjjVFmh9s%3D&reserved=0<https://bugzilla.samba.org/show_bug.cgi?id=15249>> > > <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugzilla.samba.org%2Fshow_bug.cgi%3Fid%3D15249&data=05%7C02%7Csrenaden%40microsoft.com%7C2515a7bc13144af3cc4508dca7abc215%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638569603359143252%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=hAveIaSvu7oBnJbP6ZaYUJSkaRDT9fPlNxevg7YyXPs%3D&reserved=0 > > <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugzilla.samba.org%2Fshow_bug.cgi%3Fid%3D15249&data=05%7C02%7Csrenaden%40microsoft.com%7C2515a7bc13144af3cc4508dca7abc215%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638569603359146018%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=yk%2BHKoqtQ%2FIj9gDibqKzOJ72O1mCxvMFSl%2BYAAmhv24%3D&reserved=0<https://bugzilla.samba.org/show_bug.cgi?id=15249>>> > > <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugzilla.samba.org%2Fshow_bug.cgi%3Fid%3D15249&data=05%7C02%7Csrenaden%40microsoft.com%7C2515a7bc13144af3cc4508dca7abc215%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638569603359148736%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=XJlJJhKHczhzw5c%2BvtFBIaDQCTnNscJXtCA2TPUPC%2Fk%3D&reserved=0 > > <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugzilla.samba.org%2Fshow_bug.cgi%3Fid%3D15249&data=05%7C02%7Csrenaden%40microsoft.com%7C2515a7bc13144af3cc4508dca7abc215%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638569603359151445%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=WHzdEQPRmyxUB6aQjv9Qj4LPu1uwlW47hjC7SiCCohE%3D&reserved=0 > > <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugzilla.samba.org%2Fshow_bug.cgi%3Fid%3D15249&data=05%7C02%7Csrenaden%40microsoft.com%7C2515a7bc13144af3cc4508dca7abc215%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638569603359154173%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=3GWeALNrJs73UjUgcBMjrRxdME4SoGlf%2FNsDrgjArDo%3D&reserved=0<https://bugzilla.samba.org/show_bug.cgi?id=15249>>>>. > >> >> > >> >> Cheers, > >> >> Jo (she/her) > >> >> > >> >> On 14/06/24 3:39 am, Sreekanth Nadendla wrote: > >> >>> Hello Joseph, I've sent you instructions to download time travel > >> trace > >> >>> tool to collect traces for lass process earlier. But we were > >> informed > >> >>> by Andrew Bartlet that the reason why you've raised the login issue > >> >>> with [MS-APDS] NETLOGON_TICKET_LOGON_INFO is that you are > looking to > >> >>> resolve a privilege escalation problem via enforcement of PAC > >> >>> verification. I could not see how these two issues are connected > >> >>> hence I'm unable to continue the investigation on my own (while you > >> >>> are away dealing with a personal issue). > >> >>> Please let us know whenever you are ready and we will gather the > >> >>> details, data to investigate the issue you are experiencing. > >> >>> > >> >>> Regards, > >> >>> > >> >>> Sreekanth Nadendla > >> >>> > >> >>> Microsoft Windows Open Specifications > >> >>> > >> >>> > >> >>> > >> >>> > >> >>> > >> >>> > >> >>> From: Jo Sutton <jsut...@samba.org> > >> >>> > >> >>> Sent: Monday, May 20, 2024 9:49 PM > >> >>> To: cifs-protocol@lists.samba.org <cifs-protocol@lists.samba.org>; > >> >>> Interoperability Documentation Help <doch...@microsoft.com> > >> >>> Subject: [EXTERNAL] [MS-APDS] NETLOGON_TICKET_LOGON_INFO message > >> >>> [Some people who received this message don't often get email from > >> >>> jsut...@samba.org. Learn why this is important at > >> >>> https://aka.ms/LearnAboutSenderIdentification > <https://aka.ms/LearnAboutSenderIdentification> > >> <https://aka.ms/LearnAboutSenderIdentification > <https://aka.ms/LearnAboutSenderIdentification>> > >> > <https://aka.ms/LearnAboutSenderIdentification > >> <https://aka.ms/LearnAboutSenderIdentification > <https://aka.ms/LearnAboutSenderIdentification>>> ] > >> >>> > >> >>> Hi dochelp, > >> >>> > >> >>> I’m trying to follow [MS-APDS] 2.2.2.1, “NETLOGON_TICKET_LOGON_INFO > >> >>> Message”, in order to create a NETLOGON_TICKET_LOGON_INFO message > >> that > >> >>> will be accepted by Windows Server 2019. However, in my attempts > >> so far, > >> >>> all I’ve got is STATUS_INVALID_PARAMETER codes from > >> NetrLogonSamLogonEx. > >> >>> > >> >>> Although [MS-APDS] doesn’t mention it, I assume > >> >>> NETLOGON_TICKET_LOGON_INFO should contain an unsigned 32‐bit > >> MessageType > >> >>> field, set to 0x00000026, that indicates the message is a > >> >>> NETLOGON_TICKET_LOGON_INFO message. Other than that, I’m not sure > >> what > >> >>> I’m doing wrong. Are the ticket fields arrays, are depicted in the > >> >>> diagram, or pointers, as claimed in the documentation? > >> >>> > >> >>> I can provide traces showing the problem if you would like. > >> >>> > >> >>> Cheers, > >> >>> Jo (she/her) > >> >> > >> >> > >> >> _______________________________________________ > >> >> cifs-protocol mailing list > >> >> cifs-protocol@lists.samba.org > >> >> > >> > https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.samba.org%2Fmailman%2Flistinfo%2Fcifs-protocol&data=05%7C02%7Csrenaden%40microsoft.com%7C2515a7bc13144af3cc4508dca7abc215%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638569603359156944%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=EhQT6jFY2Y2nkBHHgbv2sgAAUWswrKJYJEsm9%2B%2BboQA%3D&reserved=0<https://lists.samba.org/mailman/listinfo/cifs-protocol> > > <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.samba.org%2Fmailman%2Flistinfo%2Fcifs-protocol&data=05%7C02%7Csrenaden%40microsoft.com%7C2515a7bc13144af3cc4508dca7abc215%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638569603359159676%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=oyfphvgOYrP1048%2BcS7DSkPNMsu%2Fv9JTsMEcaRQax%2FA%3D&reserved=0<https://lists.samba.org/mailman/listinfo/cifs-protocol>> > > <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.samba.org%2Fmailman%2Flistinfo%2Fcifs-protocol&data=05%7C02%7Csrenaden%40microsoft.com%7C2515a7bc13144af3cc4508dca7abc215%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638569603359162377%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=ljYl8cnegs5RL6G5o3elasICBHIzibyS%2Buv%2FPlMR4sQ%3D&reserved=0 > > <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.samba.org%2Fmailman%2Flistinfo%2Fcifs-protocol&data=05%7C02%7Csrenaden%40microsoft.com%7C2515a7bc13144af3cc4508dca7abc215%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638569603359165080%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=ntn5nGpX2Pdtm9giZ0xVnIwtiSmtz4w8W9tAhxpqLe0%3D&reserved=0<https://lists.samba.org/mailman/listinfo/cifs-protocol>>> > > <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.samba.org%2Fmailman%2Flistinfo%2Fcifs-protocol&data=05%7C02%7Csrenaden%40microsoft.com%7C2515a7bc13144af3cc4508dca7abc215%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638569603359167775%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=JO3PzGktUxz5h7W7NGS1FV17CQPLiM38S09ND2yq%2Bw0%3D&reserved=0 > > <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.samba.org%2Fmailman%2Flistinfo%2Fcifs-protocol&data=05%7C02%7Csrenaden%40microsoft.com%7C2515a7bc13144af3cc4508dca7abc215%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638569603359170469%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=rB0WKynZuip6%2F5qd6EgAmclKRc7YFLzaOuc%2FBYFn65o%3D&reserved=0 > > <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.samba.org%2Fmailman%2Flistinfo%2Fcifs-protocol&data=05%7C02%7Csrenaden%40microsoft.com%7C2515a7bc13144af3cc4508dca7abc215%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638569603359173145%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=YzKMSnMPfSK27kJKsxxzBtOEJRvd1zbxbJL%2BJWzKpmU%3D&reserved=0<https://lists.samba.org/mailman/listinfo/cifs-protocol>>>> > > > > > > _______________________________________________ > > cifs-protocol mailing list > > cifs-protocol@lists.samba.org > > > https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.samba.org%2Fmailman%2Flistinfo%2Fcifs-protocol&data=05%7C02%7Csrenaden%40microsoft.com%7C2515a7bc13144af3cc4508dca7abc215%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638569603359175873%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=DWb6euDhkPfO8oFFd0QVF8nwfJ%2BqM%2FAn3iuy3MyqkLM%3D&reserved=0<https://lists.samba.org/mailman/listinfo/cifs-protocol> > > <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.samba.org%2Fmailman%2Flistinfo%2Fcifs-protocol&data=05%7C02%7Csrenaden%40microsoft.com%7C2515a7bc13144af3cc4508dca7abc215%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638569603359178593%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=slAyU44l1mxExOPPD0fHFxX3%2FMxehVZFC%2F62ee9%2BRAE%3D&reserved=0<https://lists.samba.org/mailman/listinfo/cifs-protocol>>
_______________________________________________ cifs-protocol mailing list cifs-protocol@lists.samba.org https://lists.samba.org/mailman/listinfo/cifs-protocol
