Participation Guidelines:

• Only students currently studying in Ramaiah Institute of Technology are allowed to participate in the Bug Bounty.

• A team of 2 students is mandatory to participate in this event.

• The team members may be of different years.

• One participant can be a part of only one team.

Miscellaneous:
 

• The participating teams must be part of the Slack Channels - #announcements and #helpdek, a link to which has been shared. All communication regarding the event will be through these channel.

• Participants must use winzip/winrar to extract the files as they are password protected.

• Bug Bounty will be a three hour long event. After which the submissions will not be accepted.

• A video showing the procedure of cloning a GitHub repository will be shared by the organizers to the participants for help.

• Additionally a video/gif showing the desired bugs to be resolved in the 'Bug Bounty - Web' will also be made available to the participants so that they can stay on the right track. No video will be provided for the C-codes. Teams may read the comments in the code for guidance.

PROCEDURE

• A GitHub repository will be shared with the teams on the day of the event, consisting of separate folders for 'Bug Bounty - Web' and 'Bug Bounty - C programing language'.

• The participating teams are supposed to clone the repository and add judges as collaborators, further make it private.

• The usernames of judges to be added as contributors will be shared on the Slack Channel #announcements and any issues regarding the event will be addressed on the Slack Channel #helpdesk at any point of time.

• Each bug solved has to be committed in the repository which will be reviewed by the judges to ensure proper implementation. Failure to do so will lead to no points being awarded to the team and may also lead to disqualification (For C Bugs you have to additionally submit the KEY in the Leaderboard website).

EVALUATION

• Scoring will be done separately for Web and C-language based on its difficulty.

• The team scoring the highest points will be declared the winner. In case of tie in score, the time of committing the code to the repository will be considered.

• To view their scores, the teams can check the LEADERBOARD website, the link to which will be provided in the Slack Channel.

• Scores for Bug Bounty-C will be live whereas, scores for Bug Bounty-Web will be a mystery. You never know how your competitors are doing!

• Judgement will be final and binding. No further changes can be demanded from the participants side.

Bug Bounty - C Programing language

Procedure:

• There will be separate folders for C-Code consisting bug(s) of easy, medium and hard level.

• First question of each level will be open. Teams can choose their priority to solve easy, medium and hard bugs.

• There will be 15 questions (in total) in Bug Bounty-C. The C-Code will be residing inside a password protected zip file.

• On removing all the bugs of a code successfully, output of the C - Code will be the KEY that needs to be submitted to the Leaderboard website. If the KEY is correct  password to the zip file corresponding to the next higher level will be provided.

• On solving the bugs, the participants are required to commit their code to their own private repository. (The one that they've cloned and added DSC judges as contributors).

Bug Bounty - C Programing language

Rules:

• The bugs in the code have to be resolved. Minor changes to the code are allowed. Completely changing the logic of the code and implementing your own code is not allowed.

• Scores for easy, medium and hard questions are as follows:

Scoring criteria:

• Hard - 40 points
• Medium - 35 points
• Easy - 25 points

Bug Bounty - Web

Procedure:

• There will be separate folders for Web consisting three projects with frontend bug(s) only.

• Each bug will have certain points associated to it based on its difficulty.

• Teams can prioritize the order of projects based on their choices. Teams may also choose to resolve individual bugs in the website rather than resolving all the bugs (Solving all bugs is not required but can still be done; scoring will be done accordingly).

• On solving the bugs, the participants are required to commit their code to their own private repository. (The one that they've cloned and added judges as contributors). Additionally they must also mention the bug that they've solved in the readme file of their GitHub repo.  The judges will check the code and award points which will be updated on the leaderboard.

A video/GIF showing the required structure of the web page will be provide to avoid confusions.

Bug Bounty - Web

Rules:

• The issues in the code have to be resolved to get the desired output. Minor changes to the code base are allowed whereas changing the entire structure of the website is prohibited.

• Each bug will have certain scores associated to it based on its difficulty.

• The participants may check the Leaderboard website for their points which will be updated on hourly basis.

• There is no need of submitting any password/passphrase to the Leaderboard website for the Bug Bounty - Web projects, only commiting to the GitHub repository is needed.

• The participants must update the ReadMe file of their GitHub repo mentioning the bug that they've solved. Failure to do so will lead to no points being awarded.

The scores of the Web Projects will be defined individually in the repo.