Wago Fkem - WeakAuras/Addons Repository

[Descentralizado]

Originally Posted by Mitsuya

Any updates for MerfinUi?

Mine is now updated for Cata

[dextroza]

Originally Posted by 911sky

Mine is now updated for Cata

any updates for Classic? : )

[Mitsuya]

Originally Posted by 911sky

Mine is now updated for Cata

The addon folder and the WA list are updated but the installer that has the updated profiles for the addons isn't.

[demonday]

Fojji AQ40 Raiding WA Pack just released. Can we get it by any chance?

ps: omg! its done! thx guys!

[testingstuf]

is it possible to get the Merfin class UI WA updated ?

[vxvxd]

can we get a update on merfins classic aura packs? pls and ty

[boumeurAX]

I give you some WA, Elvui profil from n@0wUI .

[swemosw]

is it possible to get the Fojji class UI WA updated ?

[demonday]

hey guys! i have an issue: when i install both sod and classic Fojji's class wa my castbar on sod realm disappeared. Even if classic wa's is not loaded.
Do you have smth like that?

[SimonSays1043]

If anyone needs a key generated for NAG, send me a DM with the first portion of your battle.net ID and I will respond with a key. (The key is based on the first portion of your battle.net).

I spent some time over the Christmas break to figure out how the keys were generated, it only took a day or two. I've provided the html to ShadowLin so that he can update his site with the key generator should he want to.

[ShadowLin21]

Originally Posted by SimonSays1043

If anyone needs a key generated for NAG, send me a DM with the first portion of your battle.net ID and I will respond with a key. (The key is based on the first portion of your battle.net).

I spent some time over the Christmas break to figure out how the keys were generated, it only took a day or two. I've provided the html to ShadowLin so that he can update his site with the key generator should he want to.

I added your generator, but are you certain it works? I find it quite strange that the output is nondeterministic. I will do a double check when I get back from holidays, but good work

[shyvana1]

Originally Posted by ShadowLin21

I added your generator, but are you certain it works? I find it quite strange that the output is nondeterministic. I will do a double check when I get back from holidays, but good work

Yeah doesn't seem to work with any btag I used

[SimonSays1043]

Originally Posted by ShadowLin21

I added your generator, but are you certain it works? I find it quite strange that the output is nondeterministic. I will do a double check when I get back from holidays, but good work

So the key is encoded twice with base64. When you decode it first, its compromised of multiple keys for each subscription that you've selected (base NAG sub, rogue, paladin, etc). When you decode each one of the the keys, they are broken into 4 components. xx=xxxxx=xxxxxx=xxxxxx

The first component is the subscription ID. So like if you chose rogue, DK, paladin etc.

The second component (which took me a while to understand), is a hex hash.

The third component is the UNIX time of when the subscription will expire. I just hardcoded this value to be like 10 years.

And the fourth component is a random 16 digit alphanumeric string.

-----

The hex hash, is actually computed from the first portion of your battle.net ID followed by the fourth component, the 16 digit alphanumeric key. The function ns.validatekey in Utils.lua, checks to ensure if part4 matches the hash in part2.

The longest part, was figuring out how part 4 was generated, and then realizing it was just randomly generated.

From there, its just a matter of putting it all back together. Hope that makes sense.

I suspect the addon developer will change how keys are generated going forward, but whatever. They're already violating EULA, so it's fair game.

EDIT:

Huh, noticed the key generated wasn't providing the correct key in the first upload I sent you. Sent you an updated file, tested it this time, seems to work on my end now.

[ShadowLin21]

Originally Posted by SimonSays1043

So the key is encoded twice with base64. When you decode it first, its compromised of multiple keys for each subscription that you've selected (base NAG sub, rogue, paladin, etc). When you decode each one of the the keys, they are broken into 4 components. xx=xxxxx=xxxxxx=xxxxxx

The first component is the subscription ID. So like if you chose rogue, DK, paladin etc.

The second component (which took me a while to understand), is a hex hash.

The third component is the UNIX time of when the subscription will expire. I just hardcoded this value to be like 10 years.

And the fourth component is a random 16 digit alphanumeric string.

-----

The hex hash, is actually computed from the first portion of your battle.net ID followed by the fourth component, the 16 digit alphanumeric key. The function ns.validatekey in Utils.lua, checks to ensure if part4 matches the hash in part2.

The longest part, was figuring out how part 4 was generated, and then realizing it was just randomly generated.

From there, its just a matter of putting it all back together. Hope that makes sense.

I suspect the addon developer will change how keys are generated going forward, but whatever. They're already violating EULA, so it's fair game.

It is a strange one, with how nondeterministic it is. But even if they change it, they'll get tired of it after a few times getting past it.

[SimonSays1043]

Originally Posted by ShadowLin21

It is a strange one, with how nondeterministic it is. But even if they change it, they'll get tired of it after a few times getting past it.

I've sent you an updated file of the generator, as the key's being generated were not working on your site. Sorry, should have tested thoroughly before sending it to you.

Tested the update, keys appear to be working now.