Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

leadeater

Moderator
  • Content Count

    18,691
  • Joined

  • Last visited

Awards

About leadeater

  • Title
    Fanatic
  • Birthday Sep 23, 1987

Profile Information

  • Location
    New Zealand
  • Gender
    Male
  • Occupation
    Systems Engineer | IT

System

  • CPU
    Intel i7 4930K
  • Motherboard
    Asus Rampage IV Black Edition
  • RAM
    16GB G.Skill TridentX F3-2400C10-4GTX
  • GPU
    Dual Asus R9-290X
  • Case
    LD PC-V8
  • Storage
    4 512GB Samsung 850 Pro & 2 512GB Samsung 840 Pro & 1 256GB Samsung 840 Pro
  • PSU
    EVGA Supernova NEX 1500 Classified
  • Display(s)
    Dell U3014 30"
  • Cooling
    Custom EKWB, 3x 480 RAD everything cooled inc ram (why not?)
  • Keyboard
    Razor Black Window Ultimate BF4
  • Mouse
    Mad Catz R.A.T. 5
  • Sound
    Custom build speakers, home theater sound
  • Operating System
    Windows 10

Recent Profile Visitors

26,275 profile views
  1. Not too sure why I only thought of it now but I suspect Windows licenses will now be activated against TPM IDs and not GUIDs and more strictly enforced for that matter too.
  2. For a lot of people that play a lot of online games and very much enjoy that you'll likely find a lot of support for this kind of thing. I stopped playing FPS online because of cheating and I will not be alone in that either. But I'm not strictly in support of just TPM hardware based bans (I'm not convinced something like this isn't easy to bypass, vTPM and GPU passthrough to VM for example), I would prefer a way that actually prevents tampering and cheating (only when online play) but I'm not sure TPM can help with that but maybe AMD PSP and Intel TXT/SGX could or those with TPM could.
  3. Don't forget the Samsung & AMD graphics IP deal as well, makes it even more possible to create actually strong SoCs if you're allowed to use the more/most graphics completive technology for integrated graphics.
  4. heh not allowed to use them anymore lol Might have gotten a little telling off last BOINC Pent
  5. Create all the legally correct amount of accounts they should have been using of course
  6. @StDragonAlso Microsoft's documentation on Hello is terrible, all links to how it works even from standard Hello take you to Hello for Business documentation with foot notes saying what isn't supported for standard Hello. Take about 1 or 2 links off your original stating point to be reading not quite applicable information.
  7. There's a difference because Hello for Business uses an external authentication provider and the TPM is used to ensure the trust between those. For biometrics the encrypted user representation is stored in a TEE (AMD PSP or Intel TXT/SGX) and the TPM is used to develop a trust between the biometric device and the system. How and if all these things are used differ based on the implementation, you can use Windows Hello (with or without Business) or use different method (often these ones are FIPS certified)
  8. Some features require external services though, so not every capability has a current use case for a home user. But a good step to improving things like this is for them to get used, poked, abused, broken etc etc. If it's not used it's unlikely to get better.
  9. Well I don't think it's so much of case of it being so great or not, other than disk encryption I don't think it's all that useful and disk encryption has it's own pitfalls anyway. But there's a lot of software use cases that can use TPM that currently do not, or don't actively unless it's enabled and functioning. TPM functions can be brought in to any password manager and MFA process but since the active enabled TPM status is rather low it's not used and that even after Windows 10 made it a requirements for Windows 10 branding after 2016. Microsoft Outlook is an example that uses
  10. It has usage, just things you don't use or want to use or don't hold much value for. HDD encryption keys SSL certs Biometric data Cryptographic key generation Probably more I've missed, not bothered to included Hyper-V and Defender usages of them because I know you don't care about them nor think they are useful. Anyway TPM is not a black box It's as black box as one's willingness to read the standards for it.
  11. Well Windows has a long history of things not being well supported or adopted until they become a requirement. Current and future usage of TPM might have become more popular in like 10 years, and that's maybe, also by that time TPM will probably be obsolete as well.
  12. Well how many run VMs? If you have Windows Pro then you'll be unaffected as it supports Hyper-V with vTPM.
  13. VM's use a virtual TPM and is unique per VM, they don't have access to the TPM firmware or physical TPM if you have one. Most will only have firmware TPM btw.
×