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

Doesn't support printf #121

Open
l0b0 opened this issue Feb 20, 2017 · 7 comments
Open

Doesn't support printf #121

l0b0 opened this issue Feb 20, 2017 · 7 comments

Comments

@l0b0
Copy link

l0b0 commented Feb 20, 2017

My entire session:

bash(0)> printf 'hello world'
Unknown Error :(
bash(☠️)> wat
Unknown Error :(
@jarv
Copy link
Owner

jarv commented Feb 20, 2017

Hm, I don't see this. I assume you are seeing this consistently and that it never worked for you?
What browser are you using? Any chance you have a adblocker or browser extension enabled?

bash(0)> printf 'hello world'
hello world
# 👍 👍 👍  Correct!
# You have a new challenge!
# Print the current working directory.
# 
bash(0)> wat
wat: command not found
bash(127)>  

@l0b0
Copy link
Author

l0b0 commented Feb 20, 2017

Yes, I have a bunch of extensions enabled, including an ad blocker.

@jarv
Copy link
Owner

jarv commented Feb 20, 2017

Hm, that could be the reason why. If you can try temporarily disabling them and trying again it would help to narrow down the problem. There are no ads and no external javascript on cmdchallenge.com if that makes you feel better about disabling them.

@l0b0
Copy link
Author

l0b0 commented Feb 20, 2017

I see in uMatrix that it does do an XHR to an "execute-api" host on AWS. Looks like that is how commands are evaluated, so it needs to be enabled. Unfortunately it doesn't show up in uMatrix until you send off a request.

@jarv
Copy link
Owner

jarv commented Feb 20, 2017

Yeah this is the likely culprit, it makes a cross-origin xhr cors request when you submit.

@l0b0 l0b0 closed this as completed Feb 20, 2017
@l0b0 l0b0 reopened this Feb 20, 2017
@l0b0
Copy link
Author

l0b0 commented Feb 20, 2017

Accidentally closed it. Do you think changing the error message to include more information if it can't reach the execute-api host would work?

@jarv
Copy link
Owner

jarv commented Feb 20, 2017

Yes the error reporting is terrible here, I will try to improve it.

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

No branches or pull requests

2 participants