On Tuesday, July 12, 2022 2:45:09 AM CEST Jeff McCashland (He/him) wrote:
> [Subject and SR ID updated]
>
> Hi Andreas,
Hi Jeff,
> We have created a new SR 2207110040008832 to track this new investigation. I
> will analyze the traces and let you know what I find.
thank you very much. What do
[Subject and SR ID updated]
Hi Andreas,
We have created a new SR 2207110040008832 to track this new investigation. I
will analyze the traces and let you know what I find.
Best regards,
Jeff McCashland (He/him) | Senior Escalation Engineer | Microsoft Protocol Open
Specifications Team
Phone:
[Subject and SR ID updated]
Hi Andreas,
I was able to download the new traces, thank you! We have created SR
2207060040005870 to track this new issue.
I will analyze the traces and let you know what I find.
Best regards,
Jeff McCashland (He/him) | Senior Escalation Engineer | Microsoft
On Wednesday, June 22, 2022 8:09:34 PM CEST Jeff McCashland (He/him) wrote:
> Hi Andreas,
Hi Jeff,
> I will research your question and see what we can come up with for test
> data.
thank you very much. Looking forward to hear from you :-)
Andreas
> Best regards,
> Jeff McCashland
Hi Andreas,
I will research your question and see what we can come up with for test data.
Best regards,
Jeff McCashland (He/him) | Senior Escalation Engineer | Microsoft Protocol Open
Specifications Team
Phone: +1 (425) 703-8300 x38300 | Hours: 9am-5pm | Time zone: (UTC-08:00)
Pacific Time
Hi Andreas:
Thanks for contacting Microsoft. I have created a case to track this issue. A
member of the open specifications team will be in touch soon.
Regards,
Obaid Farooqi
Escalation Engineer | Microsoft
-Original Message-
From: Andreas Schneider
Sent: Tuesday, June 21, 2022 8:00
Hello Dochelp,
I'm trying to implement support for AEAD-AES-256-CBC-HMAC-SHA512 from [MS-
SAMR] 3.2.2.4 AES Cipher Usage.
This is not really easy as there are some details unclear. I would love to
write a unit test for AEAD-AES-256-CBC-HMAC-SHA512.
Could you please provide hexdump of the
