feat: Implement secure client and server for Python and Go#7
Merged
Merged
Conversation
This commit introduces a secure TCP client and server implementation for Python and Go, based on the MultixAI protocol specification. The implementation includes: - Packet serialization and deserialization logic compliant with the RFC. - Secure communication using TLS. - A simple client that sends a packet and receives a response. - A server that handles multiple clients concurrently. - A comprehensive test suite for both unit and integration testing. The test vectors for CBOR have been corrected, and the TLS certificate has been updated to include a Subject Alternative Name (SAN) for compatibility with modern TLS clients.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This commit introduces a secure TCP client and server implementation for Python and Go, based on the MultixAI protocol specification.
The implementation includes:
The test vectors for CBOR have been corrected, and the TLS certificate has been updated to include a Subject Alternative Name (SAN) for compatibility with modern TLS clients.