11–20 of 28 posts
So it's something that's good for Heroku apps?
This seems like a vulnerability in their implementation: "configure your proxy to set the X-Forwarded-For header with the source IP"
Nice. I was really hoping it protected me from a very different kind of "abusive client" though. I guess there are somethings that even in ruby you can't do easily.
My wallet nearly hit me in the face such was its velocity upon breach of my pocket.
Nice. I was really hoping it protected me from a very different kind of "abusive client" though. I guess there are somethings that even in ruby you can't do easily.
My wallet nearly hit me in the face such was its velocity upon breach of my pocket.
Maybe I'm missing something, but this seem like something that would only be useful in situations where you don't have access to anything "closer" to the network requests (router, firewall, webserver) that you can tweak to handle these types of things. So it's something that's good for Heroku apps?
It's a good way when you don't have privilege access to the server OR skills to do it manually on Nginx etc.
Earlier quoted context omitted.
| blocking ports where there are no services doesn't | do much True, but it can be a useful 'just in-case' against things listening on ports that you were unaware of. It's obviously bad for you not to know about services that are listening on your box, but you could view it as a safety net.
Agree, I also block all unused incoming ports as a safety net as you say.
Maybe I'm missing something, but this seem like something that would only be useful in situations where you don't have access to anything "closer" to the network requests (router, firewall, webserver) that you can tweak to handle these types of things. So it's something that's good for Heroku apps?
So if your user authentication code was also a Rack middleware, and you inserted Rack::Attack after it in the middleware stack, you could rate limit based on user account as well as IP address. That would be harder to do at the firewall or web server level.
This isn't for preventing DOS attacks (for which you'd want to completely avoid hitting application code), it's just for preventing unauthorised or excessive usage.
Nice. I was really hoping it protected me from a very different kind of "abusive client" though. I guess there are somethings that even in ruby you can't do easily.
Haha I also saw the kickstarter.com domain and thought: "tell me more about this!" probably thinking the same as you..
Maybe I'm missing something, but this seem like something that would only be useful in situations where you don't have access to anything "closer" to the network requests (router, firewall, webserver) that you can tweak to handle these types of things. So it's something that's good for Heroku apps?
Maybe I'm missing something, but this seem like something that would only be useful in situations where you don't have access to anything "closer" to the network requests (router, firewall, webserver) that you can tweak to handle these types of things. So it's something that's good for Heroku apps?