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

Inclusion of another communication protocol for security #66

Open
EduardoLR10 opened this issue Nov 20, 2024 · 0 comments
Open

Inclusion of another communication protocol for security #66

EduardoLR10 opened this issue Nov 20, 2024 · 0 comments
Labels
client Client-related issues help wanted Extra attention is needed server Server-related issues

Comments

@EduardoLR10
Copy link
Member

Summary

As mentioned here, OTP was not made for communication with potentially hostile nodes. Hence, we need to introduce another communication layer, e.g., TCP, UDP, Protobuf etc, to handle initial communication with the server node from the client. To continue to use Zerl, as suggested by @z-silver, we can still send the payload in OTP format, but that within the payload of another protocol.

Observations

  • This is a big refactor;
  • New libraries on both sides (client and server) will be required;
  • Being able to run the Demo is the main criteria for the Definition of Done.
@EduardoLR10 EduardoLR10 added help wanted Extra attention is needed client Client-related issues server Server-related issues labels Nov 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
client Client-related issues help wanted Extra attention is needed server Server-related issues
Projects
None yet
Development

No branches or pull requests

1 participant