currently i am trying to make sendspace api config but i face an issue with the hash password
i used md5 but it generate different password than the sendspace generate
anyone can help solve this? would appricate it
currently i am trying to make sendspace api config but i face an issue with the hash password
i used md5 but it generate different password than the sendspace generate
anyone can help solve this? would appricate it
I will Never Refuse OR Make Excuses not to message you
" Please Avoid Imposters & Scammers "
you sure it's md5?
Does it have any Salt in it?
i read it in their site it's MD5
I will Never Refuse OR Make Excuses not to message you
" Please Avoid Imposters & Scammers "
but i think there is something is strange because when i used the MD5 in openbullet
it got the password as 47c35047100c63ffcb048ee491cfee19
while the password sendspace generated come as 0b8c52aeb1d5c780eaf948da9357e223
which both different so idk what the problem :thinking:
I will Never Refuse OR Make Excuses not to message you
" Please Avoid Imposters & Scammers "
md5 the password then lowercase it then md5 the token that you got and the hashed password then lowercase that again. That's prob it.
idk i tried that and didn't work too also send to you the config so you can try too ^^
Check any public config of sendspace to check your mistake.
if i want public config i can make one easy i trying to make the api one for better cpm
also there is no public api config
I will Never Refuse OR Make Excuses not to message you
" Please Avoid Imposters & Scammers "
but there is no option in openbullet for salt o.o
It's not a problem of the OpenBullet but of the api, it hash the password before sending it.
The only way is to find the function that lets you know how the password is hashed, if it's an apk you can try to find the code that hashes the password.
Users browsing this thread: