futureverse / futureverse/future.p2p
SECURITY: Use content checksum to send future objects and receive results
Open
- Dominant language
- R
- Stars
- 16
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Currently, the future UUID is used as the identifier sent to workers. To lower the risk for man-in-the-middle attacks, I think it's better to use a _content_ checksum for the identifier instead. That way the receiving end can validate that the object received is indeed the intended object. For context, the identifier is communicated via the message board.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.