We did it!<\/p>\n\n\n\n
Well, maybe not what you think we mean by \u201cit.<\/em>\u201d The final project is still on our distant horizon, but we\u2019re now one step closer, because we finally presented our preliminary design report to our liaison engineer at Raytheon! It was extremely well-received and we got some solid positive feedback, which we\u2019ll look into here. <\/p>\n\n\n\n Firstly, we gained some further insight as to what happens in a typical CTF when Raytheon hosts one. Apparently, some of the challenges can be \u201cbrute-forced.\u201d That is, on occasion contestants will try a long list of answers hoping that eventually one of them will work. This doesn\u2019t really support anyone\u2019s learning, so the idea came up that we should have a way of catching someone doing this. Also, the way things currently are, if someone enters a long list of random characters, but the correct answer is within those characters, they will get credit for solving the challenge. We want to prevent this from happening so nobody can just dump a dictionary on each question to pick up easy points. <\/p>\n\n\n\n We were able to ask our sponsor who the CTF is truly intended to be used by. Turns out, it\u2019s for pretty much anyone who signs up! Apparently it isn\u2019t used as a strict Q&A tool; it\u2019s more of a capstone event covering specific content from their course\u2019s curriculum. While the idea of making the CTF be a running system which teaches students as they use it was brought up and piqued their interest, we\u2019ll likely be sticking with the platform as a capstone assessment so we can focus our efforts on other foundational changes. Most often, there are 4 teams of about 3 people each, and never more than 13 teams at once. The fact that teams can work together and students can teach each other is one of the most valuable aspects of the system and we intend to maintain that, if not improve upon it.<\/p>\n\n\n\n This process also brought some new ideas and topics to the table. All-in-all, the ball is rolling on this project and Pythax is eagerly looking forward to being yet another step closer to our final project.<\/p>\n","protected":false},"excerpt":{"rendered":" We did it! Well, maybe not what you think we mean by \u201cit.\u201d The final project is still on our distant horizon, but we\u2019re now one step closer, because we finally presented our preliminary design report to our liaison engineer… Read More<\/a><\/p>\n","protected":false},"author":66,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-372","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.ippd.ufl.edu\/blogs\/team07\/wp-json\/wp\/v2\/posts\/372"}],"collection":[{"href":"https:\/\/www.ippd.ufl.edu\/blogs\/team07\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.ippd.ufl.edu\/blogs\/team07\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.ippd.ufl.edu\/blogs\/team07\/wp-json\/wp\/v2\/users\/66"}],"replies":[{"embeddable":true,"href":"https:\/\/www.ippd.ufl.edu\/blogs\/team07\/wp-json\/wp\/v2\/comments?post=372"}],"version-history":[{"count":1,"href":"https:\/\/www.ippd.ufl.edu\/blogs\/team07\/wp-json\/wp\/v2\/posts\/372\/revisions"}],"predecessor-version":[{"id":374,"href":"https:\/\/www.ippd.ufl.edu\/blogs\/team07\/wp-json\/wp\/v2\/posts\/372\/revisions\/374"}],"wp:attachment":[{"href":"https:\/\/www.ippd.ufl.edu\/blogs\/team07\/wp-json\/wp\/v2\/media?parent=372"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.ippd.ufl.edu\/blogs\/team07\/wp-json\/wp\/v2\/categories?post=372"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.ippd.ufl.edu\/blogs\/team07\/wp-json\/wp\/v2\/tags?post=372"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}