You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 :)
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 :)
The text was updated successfully, but these errors were encountered:
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 incryptngc.dll
or you found this mentioned in some documentation? Or maybe you contacted Microsoft about it?Would appreciate for any answer :)
The text was updated successfully, but these errors were encountered: