weakphish / hackpack-bot

NC State's Hackpack Discord Bot

Hi there 👋 I'm Jack!

I'm a graduate of NC State University, where I majored in Political Science with a minor in Computer Programming. My senior year (2021-2022), I served as the President of HackPack, NCSU's student hacking/cybersecurity group.

Currently, I work as a software engineer in Cisco's CollabAI organization, making collaboration smarter and more efficient.

Before that, I worked as an SRE in Cisco's Network Services, automating data center networks and developing supporting microservices.

hackpack-bot's Issues

Add way to leave CTF

This can be another button attached to the ctf listing.

Grab upcoming CTF-Time events and drop them in a channel. Teddy has code for this that can maybe be salvaged???

code may be found @ https://github.com/tcheinen/ctftime-bot

Possibly drop them in #organizers and have a button to go ahead and create a CTF out of it.

Allow users to verify via slash command their email to gain access to the server

Users, when prompting for verification, will be asked their email. If the email domain is whitelisted, they'll be sent a verification code. Once the correct code is supplied, they will be added to the verified role.

Admins should be able to add emails to the whitelist

This can be accomplished using an ephemeral slash command with an email as an argument in order to hide the user's emails and encapsulate them to the given server.

Reactions for more efficient joining of channels

It may be interesting to let others react with a specific emoji to a !join command to let them join as well. This would reduce the overall amount of clutter in the channel from people joining certain CTFs.

One potential approach is to have the bot automatically react with the appropriate reaction when someone types the command, and then other people would simply have to click on that reaction to perform the same action.

Choose language for bot rewrite

After discussion with @ProfDoof , we've decided to rewrite this bot in a less painful environment.

Some considerations:

• Available libraries for language
• Maturity of bot in said language
• documentation quality
• ease of deployment

Feel free to add to discussion below.

Create CTF channels on demand with a slash command

This should create a new channel under the CTF category and an associated role that is the only role that can see the channel, aside from admins.

React to join CTF channel

This will build off of #6 and drop a message into a ctf-listing channel of some sort. There should be a button attached that any user can click to be added to the CTF role that was created.

CTF Archive command (admin only?)

Create a way to deploy bot through CI/CD

Configure dockerfile

Check w/ Dr. Kap about archiving student information

Explore email verification flows.

Constrain to one server? Think about architecting for multiple guilds?

Create a CONTRIBUTING.md

• How do I setup my local environment and run stuff locally?
• Do I need to write automated tests?
• What sort of style do we expect?
• How much and what kind of documentation do we required?
• What needs to happen before we merge a PR in?

Add some sort of crypto or utility commands, such as basic conversions across formats?

Create a CTF channel upon creation of a role

It should be only visible to users in the role and be placed in the CTF category

add polling functionality

specify question and possible answers and allow people to select answers. use emojis or buttons?

Create wiki and set up guide

We need more documentation for contributors to get started with. Once we come up with some form of architecture, the code should also be thoroughly.

Add a contributing.md and linter config for rustfmt

In order to maintain consistency among future maintainers, we should specify the contribution process and set our linter settings in a configuration that is agreed upon.