feat(protocols): add ForcAD HTTP protocol support#189
Open
SimoneErrigo wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a dedicated HTTP submission protocol for the ForcAD Attack-Defense CTF (https://github.com/pomo-mondreganto/ForcAD), in
cookiefarm/pkg/protocols/forcad_http.go.The existing
cc_httpprotocol doesn't work correctly against ForcAD: it relies astatusfield in the checker's JSON response ("ACCEPTED","DENIED", …), ForcAD's HTTP receiver doesn't send one.ForcAD's
PUT /flagsendpoint replies with a JSON array of objects shaped like:[{"msg": "[] ", "flag": ""}]
There is no explicit status field, the verdict is only encoded in the readable
msg. As a result, withcc_httpthe flag status was never updated.Tested manually against a running ForcAD instance:
cc_httpleft the statuses unchanged