chr15m / chr15m/PodSixNet

Required callbacks?

Open
#33 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
175
Forks
34
PR merge metrics
No merged PRs in 30d

Description

I have used a packet sniffer and to my shock, the packets are perfectly unprotected and are out there just waiting to be misused. Can you please add an ability to have a callback for both incoming and outgoing data for encryption purposes?

Contributor guide

No contributing guide indexed for this repository

Research direction

No files, tests, or entry points are named. First trace how PodSixNet handles incoming and outgoing data, then determine the callback contract and encryption responsibilities; done means both directions can be processed through callbacks without breaking normal networking.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
networking, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.