4 ms·
I don't know how to feel about this. Any production app should already use a reverse-proxy (e.g. NGinx or Varnish), and blocking and similar logic can already b
by pmalynin 12y ago
I don't know how to feel about this.
Any production app should already use a reverse-proxy (e.g. NGinx or Varnish), and blocking and similar logic can already be done there. I think that the problem does not warrant its own solution at this level.
- andrewfong 12y agoSome context for this: The developer of this is also the developer of Meteor Cluster, which aims to reduce or eliminate the need for a reverse proxies (and dedicated load balancers) outside of Meteor.
- arunoda 12y agoThis attack can't solves with Reverse proxies or similar. For proxies, this is just a simple WebSocket message. So, it's hard (or can't) detect in the proxy layer or with something like Cloudflare. That's why we need a something like Sikka, which understand DDP, the protocol behind Meteor. Anyway, only we detect bad IPs. It's a good idea to ban them from the network layer.