Closed ghost closed 6 years ago
This is indeed an important issue. It applies to all pSpaces implementations. Together with other security aspects (authentication, access control, secure communications, encryption, ...) it is on my list of future features.
This issue has been temporarily solved in commit 6e4bea2979e88bb19840a6bf365ea4611a497cb1 in the aggregation-policy
.
The implementation is slightly throttled, incuring a performance penalty.
Reopen this issue when a proper solution is needed.
Using
go
on any of the operators can perform a DoS attack locally or across the network.There are several ways of fixing this:
go
by proceeding when many operations are called. This could be an operation queue or counter of how many operations are allowed, throttling the performance of the operations.The following will code will create simple flooding mechanism for a localhost:
Output:
Changing to do it this across network is trivial.
Clearly this depends on protocol and the underlying tuple space implementation, but future tuple space implementations should avoiding opening many connections in order to send of tuples.