Inspiration
Taking our love for fighting games, we brought to the world an idea of pure ingenuity. Machines can brute force hundred thousands or even millions of passwords in seconds - not anymore. Presenting the headless security timing-based interpretation system, making brute force and password execution harder for machines and humans alike.
What it does
The headless security timing based interpreter allows user to set a password using motion inputs (some directional input) and a button (an attack). After the password is set, the user can use that input to log in - as long as they complete the motions correctly and within a certain timing threshold for each. In non-fighting game terms, imagine we have combination of keyboard buttons needing a certain timing for a series within the combination in order for that section and therefore the whole input string to be valid.
How we built it
Using C++, we read user keyboard inputs mapping them to valid motion input. For simplicity of the project we only considered twelve motion input and six button.
Challenges we ran into
One of the biggest issues we faced was scope, as we had to cut back on many features to be able to submit and make the program on time. For example, being able to set the password in the app, as well as detect specific timings for each of the inputs, to make sure the timings of the inputs seem human.
Accomplishments that we're proud of
The input interpreter is the focus of the project that took us the most time. Being able to compile a series of directional inputs to a degree similar to the leniency of modern fighting games definitely took more time than we thought it would, but it now works as well as current implementations in recent fighting games.
What we learned
We learned the value of planning and dedicating work to members, making sure each one knows their specific task and the necessities of how they connect with the modules other members are working on.
What's next for Headless Security Timing-Based Interpreter
Adding a timing classifier model analyzer to be able to tell the individual quirks and timings between different people's input habits. It would add yet another layer of security to be able to identify if the right person is trying to access the protected information.
Log in or sign up for Devpost to join the conversation.