Retired
Find a way to cheat the Codewars testing system (retired)
15tianshuo
Loading description...
Puzzles
Security
Bugs
This comment has been reported as {{ abuseKindText }}.
Show
This comment has been hidden. You can view it now .
This comment can not be viewed.
- |
- Reply
- Edit
- View Solution
- Expand 1 Reply Expand {{ comments?.length }} replies
- Collapse
- Spoiler
- Remove
- Remove comment & replies
- Report
{{ fetchSolutionsError }}
-
-
Your rendered github-flavored markdown will appear here.
-
Label this discussion...
-
No Label
Keep the comment unlabeled if none of the below applies.
-
Issue
Use the issue label when reporting problems with the kata.
Be sure to explain the problem clearly and include the steps to reproduce. -
Suggestion
Use the suggestion label if you have feedback on how this kata can be improved.
-
Question
Use the question label if you have questions and/or need help solving the kata.
Don't forget to mention the language you're using, and mark as having spoiler if you include your solution.
-
No Label
- Cancel
Commenting is not allowed on this discussion
You cannot view this solution
There is no solution to show
Please sign in or sign up to leave a comment.
Retiring this kata since we don't try to stop cheaters, we just detect them and deduct honor. Fixing the JS framework to be uncheatable is too much of a cat and mouse game, magnified by having to do it for multiple languages.
This kata just stole 9 honor points from me.
/!\ Oh oh ! /!\
@jhoffner & other admins you SHOULD look at the solutions of this kata : http://www.codewars.com/kata/find-a-way-to-cheat-the-codewars-testing-system/solutions/javascript
Yup. Every Javascript kata can be broken by returning early. I haven't even checked to see if it's possible in other languages.
We stopped trying to handle cheating within the actual frameworks because it was an endless cat and mouse game. To handle it in all languages in all cases was just too much, so instead we have a system where after you submit your code (as a defered process) we check to see if code that should fail passes. In this case we dock you the points and honor earned. The first few occurances of cheat detection are done this way as good faith, after 3 occurences we start to penalize your score beyond taking away your earned points.
Since we let the first few cases slide, its probably ok to leave this kata up, but its never going to get approved. I will update the kata description to reflect this information.
@jhoffner Actually, by using the
vmmodule in node.js things would be much better! It really sandboxes the user code.This comment has been hidden.
There are so many issues into
cw-2.js! I really enjoyed this kata!Very funny kata.
I don't know if I should consider it ready or not, since the solutions will surely be broken very soon. :-)