Windows 10: Third party Kerberos Realms, and PAC-validation

For years we have helped customers manage Windows Server, that log on via third party kerberos MIT-realm, but with the updates and PAC-validatoin requirements all interoperability with such realms seems broken. We help with both FreeIPA deployments that do indeed add ms-pac attributes to the tickets, and barebone MIT-deploymnets, that dosen't. Is there no longer any way to handle trust, or logon i such enviroments, se for example this link for the basic strategy: https://blog.dan.drown.org/kerberos-for-windows-without-ad/Any tips or pointers are deeply appreciated.With FreeIPA deployments tr

:)

 

Check for Valid Kerberos Ticket

Hello everyone,

I'm looking to be able to generate a command klist to check and see if a kerberos ticket is valid.

If the ticket is valid return 1 if a ticket is invalid return something a 0.

We are moving from Linux to Windows for this process but I have yet to find any documentation regarding how you would do this.

I would believe that a sample or model would be everywhere.

Regardless does anyone have some suggestions on getting this accomplished.

Regards,

Jonathan

 

Good LAN party games?

Most of my suggestions have already been listed.

However, I found Swat4 to actually be a pretty fun LAN game, especially at smaller LAN parties.

 

Lock Screen user incorrect in cross-realm AD

Hi,

While testing win10 on our AD we experience a strange and very annoying regression.

Our AD REALM is in a bidirectionnal approbation with a MIT Kerberos Realm, and our users only have passwords on the MIT Realm, which are linked to the AD account.

Previously (WinxP / Win7) this wasn't a problem at all, now with win10 when user initially log-in everything is fine, but if/when the session is locked, the lock screen wrongly use the AD User Account to try to unlock the session.

We have to use the "Other User" link and manually re-enter the MIT Realm...

Isn't there another solution ? is it known ?