问题原文
原帖链接 · ixe013 · CC BY-SA 3.0
I have a Kerberos problem with a Linux host connecting to a Windows KDC. I suspect that Kerberos key with the wrong version is to blame.
One way to be shure would be to delete the SPN and create it anew, but this is in a production environment and I must debug in "read-only", if you will.
How can I retreive the current Kerberos KVNO from a principal in Active Directory ?
已采纳解答
原帖链接 · Ryan Ries · CC BY-SA 4.0
I'm incredulous as to whether KVNO has anything to do with your problem, OK maybe with Linux clients, but anyway, use Wireshark/Network Monitor:
Key Version Numbers are described in MS-KILE section 3.1.5.8.
By the way, Mathias R. Jessen is correct in that in that Windows typically ignores KVNOs. But they are still implemented in an RFC-complaint way.
No, Windows does not pay attention to KVNO. It simply ignores it.
But the KVNO does have some significance in an RODC environment:
Some more info here: https://web.archive.org/web/20150204183217/http://support.microsoft.com/kb/2716037
In an environment with one or more RODCs authentication may fail when interacting with certain MIT based Kerberos devices in one of the following scenarios.
· The client is an MIT device which received a TGT from Windows KDC on RODC
· The client passes a TGT generated by Windows KDC on RODC to MIT Device which in turn uses the TGT to request a TGS on behalf of the calling user.
In both scenarios the TGT will have been issued by an RODC where the msDS-SecondaryKrbTgtNumber associated with the krbtgt account for that RODC will have a value greater than 32767.
摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。
