Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

KVN is always 0 #539

Open
karman-docker opened this issue Jan 23, 2024 · 2 comments
Open

KVN is always 0 #539

karman-docker opened this issue Jan 23, 2024 · 2 comments

Comments

@karman-docker
Copy link

karman-docker commented Jan 23, 2024

Same as issue #456.

My keytab file has non-zero knv. I can see that using klist tool or on the AD itself.

But when I load the keytab file using the APIs of this library from keytab.String() I can see that knv is always 0.

This is causing client login fail, as kvns don't match.

@Denis-shl
Copy link

Hello, tell me, does kvno overflow the int data type?

@karman-docker
Copy link
Author

Hi @Denis-shl if you are asking me, in my case the KVNO that I see on the AD server and using klist tool was single digit number (I think it was 3 or 4), but when stringify my keytab file using keytab.String() from this package, I see kano is zero.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants