search

shellphish / ictf-framework

The iCTF Framework, presented by Shellphish!
Other
331 stars 86 forks source link

Potential scoring flaw #12

Closed BloodLustr closed 9 years ago

BloodLustr commented 10 years ago

If a team turns their services off, they are not penalized.

adamdoupe commented 10 years ago

This is a good point. We need some way to include SLA in the score. We'll need to update both the database service and the scoreboard (we should show raw score and SLA). @invernizzi @zardus Thoughts?

invernizzi commented 10 years ago

No problem as far as the dashboard is concerned. What will the score formula be? We could eventually let the organizers set the weight of the SLA and attack score

adamdoupe commented 10 years ago

Having the organizers choose would be pretty cool (I think it'd be sweet to have something like "Advanced Settings" in the CTF-creation stuff). For now, why don't we do the classic score = raw_score * SLA?

I think we'll change the API endpoint /scores so that it returns for each team_id: {"score": int, "sla": int (0-100 percentage), "raw_score"}

What do you think @invernizzi ?

invernizzi commented 10 years ago

Sure, go ahead.

Luca

On Thu, Aug 21, 2014 at 9:35 AM, Adam Doupe notifications@github.com wrote:

Having the organizers choose would be pretty cool (I think it'd be sweet to have something like "Advanced Settings" in the CTF-creation stuff). For now, why don't we do the classic score = raw_score * SLA?

I think we'll change the API endpoint /scores so that it returns for each team_id: {"score": int, "sla": int (0-100 percentage), "raw_score"}

What do you think @invernizzi https://github.com/invernizzi ?

— Reply to this email directly or view it on GitHub https://github.com/ucsb-seclab/ictf-framework/issues/12#issuecomment-52946289 .

adamdoupe commented 9 years ago

I created a branch to work on this issue, because it requires corporation from @invernizzi to change the scoreboard.

I pushed the necessary changes to the database service.