[DiscordArchive] whats their sha_pass_hash length?
[DiscordArchive] whats their sha_pass_hash length?
Archived author: Whatifeel • Posted: 2024-06-10T09:56:29.926000+00:00
Original source
As i see
Archived author: Tea • Posted: 2024-06-10T09:56:55.161000+00:00
Original source
the code that is crashing for you is migrating old sha_pass_hash to new columns salt and verifier
Archived author: Tea • Posted: 2024-06-10T09:57:31.720000+00:00
Original source
if you just drop it then accounts that didnt get converted will not be able to log in (but i think that with lenghts like 39 they couldnt log in anyway)
Archived author: Tea • Posted: 2024-06-10T09:58:14.005000+00:00
Original source
you would only get 39 if your code tried to use 3.3.5 hash calculation AND on top of that removed a 0 at front
Archived author: Whatifeel • Posted: 2024-06-10T09:58:55.861000+00:00
Original source
So i need to change gmp as i understand
Archived author: Whatifeel • Posted: 2024-06-10T10:00:23.591000+00:00
Original source
But how then is it best to get out of this situation? Suppose I redo gmp, but bnetserver won't start. I have a small non-commercial DF server that's been running since December 2022. I don't think all players will go to restore their password just to get bnetserver up and running
Archived author: Whatifeel • Posted: 2024-06-10T10:01:14.582000+00:00
Original source
So i need just convert data with mass query update or smh like that in order to run bnetserver
Archived author: Tea • Posted: 2024-06-10T10:01:19.349000+00:00
Original source
sec
Archived author: Tea • Posted: 2024-06-10T10:02:04.141000+00:00
Original source
`SELECT id, email, LENGTH(sha_pass_hash) FROM battlenet_accounts WHERE LENGTH(sha_pass_hash) != 64 AND (salt IS null OR verifier IS NULL)`
Archived author: Tea • Posted: 2024-06-10T10:02:08.371000+00:00
Original source
those are the broken accounts