Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

biligrab's appkey is blocked again. #28

Open
persmule opened this issue Apr 25, 2016 · 8 comments
Open

biligrab's appkey is blocked again. #28

persmule opened this issue Apr 25, 2016 · 8 comments

Comments

@persmule
Copy link

DEBUG:root:{"code":-1,"error":"app has been blocked."}
DEBUG:root:Bilibili API: {"code":-1,"error":"app has been blocked."}

@cnbeining
Copy link
Owner

shoot。

@cnbeining
Copy link
Owner

Should be fixed...

@persmule
Copy link
Author

It seems bilidan utilizes some form of obscuration.

@cnbeining
Copy link
Owner

Not really, and I am not really fond of that.

Since we can get the key from a sh*tload of sources, it makes no sense to hide anything within this project: just pointless.

@m13253
Copy link
Contributor

m13253 commented Apr 26, 2016

Perhaps we can parse the files on a server? That will not expose our appkeys.

Just a hint: The official Bilibili mobile app uses different keys for request and signing. The latter was calculated from the current date and time. And the signing algorithm is different from what is documented.

@cnbeining
Copy link
Owner

As discussed with soimort, I do not want to run any server-side stuff to
make anything running.

For now I am using their own key pair. And for now I am not very interested
in changing the whole algorithm- let's wait and see.

2016年4月25日星期一,Star Brilliant notifications@github.com 写道:

Perhaps we can parse the files on a server? That will not expose our
appkeys.

Just a hint: The official Bilibili mobile app uses different keys for
request and signing. The latter was calculated from the current date and
time. And the signing algorithm is different from what is documented.


You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#28 (comment)

@arition
Copy link
Contributor

arition commented May 20, 2016

I cannot fetch the video now.
Seems that they have changed the sign algorithm?

DEBUG: [2422130]
INFO:root:You are downloading all the parts in this video...
DEBUG:root:BiliURL: https://api.bilibili.com/view?appkey=c1b107428d337928&id=2422130&type=xml
INFO:root:Fetching api to read video info...
DEBUG:root:{"code":-3,"message":"API sign invalid","ts":1463717923}
DEBUG:root:Bilibili API: {"code":-3,"message":"API sign invalid","ts":1463717923}

@cnbeining
Copy link
Owner

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants