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

Might wanna change this before the tourny #56

Open
landeholt opened this issue Apr 29, 2021 · 1 comment
Open

Might wanna change this before the tourny #56

landeholt opened this issue Apr 29, 2021 · 1 comment

Comments

@landeholt
Copy link

landeholt commented Apr 29, 2021

Hi cygni / maintainers of paintbot!

I am currently just going through the source code in order to automate some parts of my training model for my bot and I stumble upon how you have implemented authorization. Cool I first thought, I can use it to get the token to authorize some websocket calls. But then out of curiosity, I tried the usercredentials on the live website aswell, and yeah.. Bad news. I got authorized.

Skärmavbild 2021-04-29 kl  18 53 20

I hope this can be changed before the tournament starts, because this will break the fairness of the game, if someone outside of the organizers gets hold on an auth-token.

Map<String, String> users = new HashMap<String, String>() {{
put("emil", "lime");
put("chen", "nehc");
put("johannes", "sennahoj");
}};

Just change the usercredentials for the live server.

Thanks for hosting this, and I hope I will get a seat.

I am currently the 1st on the waiting list (Accordingly to Josefina, A.)

@juiceit
Copy link
Contributor

juiceit commented May 1, 2021

Hi! I understand your concern, and thanks for raising possible security issues. This is not as bad as it may seem, though. The only thing you can do as a signed-in user is administer a tournament. Someone could start the tournament before everyone has joined or change the game settings before we start, but that's just rude behaviour that we don't expect from our participants. And we would just need to start over again to undo it.

With that being said, you're completely right that we should have this fixed. Authorisation just hasn't been a priority for us :)

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