Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Packet triggers should be more identifiable #12

Open
apokusin opened this issue Aug 11, 2017 · 0 comments
Open

Packet triggers should be more identifiable #12

apokusin opened this issue Aug 11, 2017 · 0 comments

Comments

@apokusin
Copy link

It's hard to keep track of which packet triggers do what since they all look the same. Furthermore, it's unclear whether a new packet trigger is added to the top or bottom of the list, so I found myself clicking between each trigger to confirm I'm sending the right info. This was particularly important during the Man-in-the-middle attack.

My recommendation is to use a randomly generated color to identify each packet trigger. This color could also be used to identify the packet "orb" while in transit, making it easier to understand.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant