![]() A CERTUTIL check in PShell showed all of the keys in my personal store were software based and not exportable (as described here), which only confirmed the problem: Hence why I was fervently trying to enable hardware processing of keys (including for Windows Hello) through the TPM, instead of as software keys, as it would also enable hardware key storage of the Windows Hello PIN. This is an real problem (I recently discovered), as a software generated Windows Hello PIN is apparently much more vulnerable to being cracked than a hardware (TPM) one. A search on 1PW Community Forums showed this was a common issue for many trying to enable this feature, and it involved some mfgs (or users) inadvertently disabling this feature via the TPM settings, or otherwise having a TPM configuration issue. The additional option to have the TPM manage this (as a hardware generated key, vs a software key) was grayed out. I recently attempted to setup 1Password to use Windows Hello as a login controller (vs entering a PW each time) for 1PW. ![]() I have always had both MS and HP updates set to auto-install, and this hasn't presented any issues, up until now. I have a 4/2017 mfg HP Spectre x360 15" (15-bl012), which I purchased new.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |