[DiscordArchive] apparently auth is complaining about the password, maybe just updating that could work?
[DiscordArchive] apparently auth is complaining about the password, maybe just updating that could work?
Archived author: ChrisFredriksson • Posted: 2024-01-20T15:08:24.689000+00:00
Original source
maybe.. removing a module changes the "base" of how the salt/verifier looks like
Archived author: Kitzunu • Posted: 2024-01-20T15:08:31.179000+00:00
Original source
nono
Archived author: Kitzunu • Posted: 2024-01-20T15:08:37.025000+00:00
Original source
they are always calculated the exact same way
Archived author: ChrisFredriksson • Posted: 2024-01-20T15:08:41.521000+00:00
Original source
ok
Archived author: Kitzunu • Posted: 2024-01-20T15:08:55.992000+00:00
Original source
my only guess is that something got corrupted when you moved HW
Archived author: ChrisFredriksson • Posted: 2024-01-20T15:09:02.699000+00:00
Original source
I'm just thinking that it takes like an MD5 on the complete bin file and uses that, you know what I mean?
Archived author: ChrisFredriksson • Posted: 2024-01-20T15:09:10.268000+00:00
Original source
yeah probably
ASSWORD")`, substituting the user's username and password converted to uppercase.Archived author: Kitzunu • Posted: 2024-01-20T15:09:38.711000+00:00
Original source
### salt
salt is a cryptographically random 32-byte value.
### verifier
verifier is derived from salt, as well as the user's username (all uppercase) and their password (all uppercase).
To obtain the verifier you need to calculate:
1. Calculate `h1 = SHA1("USERNAME
ASSWORD")`, substituting the user's username and password converted to uppercase.
2. Calculate `h2 = SHA1(salt || h1)`, where || is concatenation (the . operator in PHP).
**NOTE:** Both `salt` and `h1` are binary, not hexadecimal strings!
3. Treat `h2` as an integer in little-endian order (the first byte is the least significant).
4. Calculate `(g ^ h2) % N`.
**NOTE:** `g` and `N` are parameters, which are fixed in the WoW implementation.
`g = 7`
`N = 0x894B645E89E1535BBDAD5B8B290650530801B18EBFBF5E8FAB3C82872A3E9BB7`
5. Convert the result back to a byte array in little-endian order.
Archived author: Kitzunu • Posted: 2024-01-20T15:09:43.861000+00:00
Original source
that is how it is calculated
Archived author: ChrisFredriksson • Posted: 2024-01-20T15:10:07.207000+00:00
Original source
yeah I read that a moment ago