Slow Loris Attack - Computerphile
Why Stack Overflow recommends it
Stack Overflow users link it as the standard short explanation of Slowloris whenever slow clients, connection-per-thread servers or timeouts come up.
Recommended by 0 people across 0 different months, 2018 to 2023.
What it is
A Computerphile explainer in which Dr Mike Pound describes the Slow Loris denial-of-service attack. Instead of flooding a server with data, the attacker holds many connections open with painfully slow partial requests until the server runs out of capacity. Filmed at the University of Nottingham.
What people said
Cites Christopher · 2018-10 · Stack Overflow · on “How do I stream a large file from api to api without using disk and running out of memory?”
If you could stream it directly to the other servers input, you might minimize the memory footprint. That might require you to undo a bunch of the code that is doing work for you however. Also a danger here is that this might trigger some "Slow Lorris" defense code if the source is delivering too slow (and thus the sendon is to slow): [this video]
Cites Patrick · 2019-06 · Stack Overflow · on “Spring WebFlux differences when Netty vs. Tomcat is used under the hood”
Currently there are 2 basic concepts to handle parallel access to a web-server with various advantages and disadvantages: Blocking Non-Blocking Blocking Web-Servers The first concept of blocking, multi-threaded server has a finite set amount of threads in a pool. Every request will get assigned to specific thread and this thread will be assigned until the request has been fully served. This is basically the same as how a the checkout queues in a super market works, a customer at a time with possible parallel lines. In most circumstances a request in a web server will be cpu-idle for the majority of the time while processing the request. This is due the fact that it has to wait for I/O: read
Cites Christopher · 2019-11 · Stack Overflow · on “SqlDataAdapter object CommandTimeOut does not work in C#”
With Database Operations, there is a whole bunch of timeouts to consider: The Command has a timeout [LINK] . The connection has a timeout. [LINK] Every layer of the Networking part has a timeout. The server on the other end has a timeout. The server on the other end might have slow loris protection [this video] . The locks and transaction might time out (because at some point, somebody else might want to work with that table too). According to your comments, your stored procedure returns "millions of records". Wich is propably where the issue lies. That is not a useable query. That is so much data it exceeds being a mere Network or DB Problem - and possibly becomes a memory problem on the client.
Cites sibi · 2019-12 · Stack Overflow · on “python socket GET”
@james: you did a SlowLoris attack there without aware of it. I can't explain better than here, [this video] I assumed that you found the solution from all the above answers but I just answered to bring this to your knowledge. :)
Cites root · 2020-05 · Stack Overflow · on “non network based dos attack”
That kind of attack is based on vulnerabilities in the server implementation. One of the awesome ones is Slowloris [LINK] , which attacks the single-connection-per-thread design of Apache [this video] .
Cites Pablo Yaggi · 2020-07 · Stack Overflow · on “Performance of multithreaded TCP networking”
Multi-Threading vs Single-Threading is a hard topic, and I think it all depends on the point of view of your implementation. If you have a good event-driven system on one thread probably using single thread for low level network IO will be better. Spawning threads have on itself a performance penalty as the system will need to attend them, of course it will be helpful to use the extra processors, but as you said when finally getting into the low level all threads will need some kind of synchronization, penalty again, unless you are using one socket per thread. One mayor drawback of multi-threading (one socket per thread) on networks is that most of the time you system will be subject to 'slo
Cites stevec · 2023-05 · Stack Overflow · on “High-severity vulnerabilities in Docker images”
This is a great question. I used a downstream image from the one you mentioned (rocker/shiny) and it had many more vulnerabilities because it uses so much javascript. I ran a scan of the image with two security scanning softwares (grype and snyk). They found 13 critical vulnerabilities (!!). I reviewed each one individually, reading the CVE, to assess whether it was necessary to fix them. Here are some things I learned: 'Critical' doesn't necessarily mean your data is at risk. It could simply mean that someone could DDOS your app easily, if they know exactly how to exploit the vulnerability. E.g., instead of making 1000's of requests (to flood your app), they may only need to make, say, 20 (