Twitter | Pretraživanje | |
📔 Michael Grafnetter
If you deployed Windows Hello for Business, you should definitely read Microsoft's Security Advisory ADV190026. And I am not saying it just because I reported that issue and had a talk about it at Black Hat Europe. 😉
Reply Retweet Označi sa "sviđa mi se" More
Jaromir Kaspar 9. pro
Odgovor korisniku/ci @MGrafnetter
how do I find that my TPM is vulnerable? is there some xml/json with list of versions and models? if I understand correctly, correct way is to flash new firmware, wipe and initialize TPM and reissue WHfB identity?
Reply Retweet Označi sa "sviđa mi se"
📔 Michael Grafnetter 9. pro
Odgovor korisniku/ci @jaromirkaspar
Additionally, you have to manually delete those vulnerable public keys from AD, which is not obvious at all. There is a script for local checking of vulnerable TPMs, or you can check event logs, see There is also an undocumented ADFS key auditing option.
Reply Retweet Označi sa "sviđa mi se"