Time of death: 4:22 PM UTC September 26th

Notes, please read:

For those of you who don't know, HWID was the holy grail for Windows activation, letting you generate licenses straight from Microsoft licensing servers, being registered as fully legitimate in microsofts servers and letting you keep the activation permanently, even after windows reinstalls being completely undetectable and with nothing on your system being modified. If you're still using outdated activation methods and you missed out on this, I'm sorry

Existing HWID licenses are left unaffected. Only new requests are blocked, no licenses were revoked.

By the way, MAS still works and is the best option for Windows/Office activation. For permanent Office activation use it's Ohook method (supports subscription products such as 365 as well) and KMS38 for Windows

ALL OTHER ACTIVATION METHODS ARE STILL WORKING, ONLY METHOD AFFECTED IS HWID.

All HWID activators are affected, not only MAS

Around that time, Microsoft servers unexpectedly started blocking the licensing requests HWID activation method sends to Microsoft. This was a slow rollout that spanned over a few hours, at the moment the exploit is completely dead. The best options for Windows activation now is KMS38 or vlmcsd.

Patching this would boost illegal key reselling websites which causes more harm to Microsoft than HWID exploit. We can only wonder why they patched this.

{"code":"BadRequest","data":[],"details":[],"innererror":{"code":"PermanentTSLRejection","data":[],"details":[{"code":"113","message":"avsErrorCode","target":null}],"message":"The Purchase Service rejected the provided TSL; the client should destroy the TSL.","source":"PurchaseFD"},"message":"The calling client sent a bad request to the service.","source":"PurchaseFD"}

TLS=Temporary Signed License=The tickets HWID activation sends. Microsoft servers are now just responding with "kill it."

Transferring existing HWID licenses to other computers using Microsoft account is broken too.

  • Draghetta@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    16
    ·
    1 year ago

    The whole red hat thing (you mean the centos drama?) has no implications whatsoever on fedora, fyi. If you liked it feel free to go back to it.

    • OverfedRaccoon 🦝@lemm.ee
      link
      fedilink
      English
      arrow-up
      3
      ·
      edit-2
      1 year ago

      Cool deal. Thanks. It was just a convenient time, as I got a new SSD. So I could either clone the old drive or try something new, so I just decided to give Tumbleweed an honest go. I ended up liking it. But Fedora was truly the OS that finally got me to stop hopping every so often. I'd definitely be down to revisit at some point.

    • CeeBee@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      you mean the centos drama?

      I think they mean the recent issue with RHEL source code being closed up. It's more of a principle thing for most people.

      • Draghetta@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        2
        arrow-down
        1
        ·
        1 year ago

        That is not a thing. No part of rhel is closed up: subscribers can still download the source rpms, and the sources themselves are still the same as upstream. Every change they make to the sources is still pushed upstream for everybody to use.

        What is broken is automated rebuilds, and if people have a principle problem because they think libre stuff should necessarily be gratis I think they have the wrong principles.

        Regardless of that, the rage bait narrative that red hat is “closing down sources” is that, rage bait.