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

[Question] From where NgcCacheType comes from #112

Open
APshenkin opened this issue Oct 9, 2024 · 0 comments
Open

[Question] From where NgcCacheType comes from #112

APshenkin opened this issue Oct 9, 2024 · 0 comments

Comments

@APshenkin
Copy link

Hi

First, thank you for this great repo, that shows how to use Windows Hello via nCrypt API instead of KeyCredentialManager.

This is really useful and more powerful than abilities that KeyCredentialManager provides.

I'm currently trying to implement support of Windows Hello in my project that is using golang and I wanted to use your approach. However my main consern, that this way is not documented in any way by Microsoft. Especially this option NgcCacheType can be found only in your plugin :)

I actually asked this question on Microsoft Q&A site, but not sure that will get some answer https://learn.microsoft.com/en-us/answers/questions/2100690/undocumented-usage-of-ncrypt-with-microsoft-passpo

Therefore wanted to ask, how did you discovered this NgcCacheType option? Was it just guess based on strings in cryptngc.dll or you found this mentioned in some documentation? Or maybe you contacted Microsoft about it?

Would appreciate for any answer :)

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

1 participant