![]() No effort was made to obfuscate any of the information in these screenshots.The network traces captured for this post were generated with Windows Server 2016 running on AWS.If you are having trouble following, please see this post. Likewise, I skip most of the introductory material in this post and jump straight to what is needed in order to understand the network traces.See this post for more information about the processing done by each Kerberos actor. I skip most of the details of what each actor is doing and instead focus on the messages exchanged by the protocol here.See this for a detailed description of Windows user login. Here we are only interested in the pure-Kerberos details. ![]() Some of it involves proprietary details beyond the scope of the Kerberos 5 protocol that we do not care about in this post.
0 Comments
Leave a Reply. |