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

client secret #9

Closed
pxue opened this issue Jul 14, 2016 · 4 comments
Closed

client secret #9

pxue opened this issue Jul 14, 2016 · 4 comments

Comments

@pxue
Copy link

pxue commented Jul 14, 2016

https://github.com/tejado/pokemongo-api-demo/blob/master/main.py#L138

you should parameterize this. worst case I can hijack everyone who's using this' session.

you should capture the initial oauth exchange from your app to niantic.

@tejado
Copy link
Owner

tejado commented Jul 15, 2016

Like this? :) d0642a9

@ghost
Copy link

ghost commented Jul 15, 2016

Client secret authorizes the client/software to use the api to create access tokens. Everyone using the pokemon go app has the same key. No need to parameterize it. There is no way you can hijack anyone's session using this.

@tejado
Copy link
Owner

tejado commented Jul 15, 2016

Yes, I thought the same. But wasn't sure anymore due to different opinions and also pxue comment.
Thanks!

@pxue
Copy link
Author

pxue commented Jul 15, 2016

@WieZ you're right that client secret is an authorization method, and right about everyone uses the same key. however, in normal circumstances the client secret is server side and hidden from the users, never in the client. For example, github its self says client secret should never be shared and RFC6819 touches very briefly about the dangers of exposed client secret.

Either way, this is a demo, just wanted to let people know :)

@tejado tejado closed this as completed Jul 16, 2016
dmadisetti pushed a commit to CyberSecurityUSC/pgoapi that referenced this issue Aug 7, 2016
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

2 participants