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

feat: add at_test_proxy tool #437

Draft
wants to merge 2 commits into
base: trunk
Choose a base branch
from
Draft

feat: add at_test_proxy tool #437

wants to merge 2 commits into from

Conversation

XavierChanth
Copy link
Member

- What I did

Created a new tool which can be used for testing and debugging tcp / tls clients.
The intended use of this tool is with a locally running atServer, atDirectory and/or shrd.

Every time the tool receives a new message, it blocks waiting for a command on stdin, the command tells the tool how to handle the message.

The available commands are also listed in the README.md along with usage & examples:

  • forward
  • modify
  • respond
  • skip

- How I did it

- How to verify it

To be used for debugging at_c and c sshnpd.
Can be used for functional tests in at_c later (if we find need to further formalize tests)

- Description for the changelog
feat: add at_test_proxy tool

@XavierChanth XavierChanth requested review from gkc and cpswan January 10, 2025 20:32
@XavierChanth
Copy link
Member Author

@gkc This is still work in progress, open to feedback if you think a use-case is missing.

Comment on lines +3 to +7
enum MessageStatus {
response, // from client to server
request, // from server to client
none,
}
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some of the naming is unnatural because it's a proxy...

e.g. the atServer response comes from the clientSocket to the serverSocket.

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

Successfully merging this pull request may close these issues.

1 participant