81–90 of 118 posts
I wonder if you could make the attacker crunch out some shah-256 and you can profit by mining Bitcoin.
You can no longer profit mining Bitcoin with a CPU or GPU. ASICs are needed.
I want my tarpit to endlessly repeat "your mother is a whore" in Chinese
That said, I'm a little confused even after reading the linked RFC paragraph; it claims "The primary use of this feature is to allow TCP-wrappers to display an error message before disconnecting." but I'm not familiar with that term and there are no other occurrences of the word "wrapper" in that document.
Firefox and Chrome will spin on that server for hours before giving up.
For a web browser, this behaviour makes a lot of sense: timeouts are usually based on "I've waited for X and haven't received anything", not "this connection is like collecting water from a dripping tap". As long as there is a slow but steady stream of content coming in, you wouldn't want to abort until the user gives up or an internal limit on the data collected is hit (which is probably what happened with the author's tests --- a quick search doesn't yield the maximum size of the response headers browsers will accept, but servers usually have a configurable limit of a few KB at most for the request headers alone.)
cause we are never going to give you up ;)
Neat little tool! Since switching to Teleport I haven't had OpenSSH listening publicly for a while, just reverse proxies. Still, I'll prob spin up a small server for this to observe the patterns and IP locations. Also, don't think that posting this blog article on March 22 didn't go unnoticed :)
Could the return strings be generated by a Deep Learning powered fuzzer?
What are you trying to achieve?
Neat little tool! Since switching to Teleport I haven't had OpenSSH listening publicly for a while, just reverse proxies. Still, I'll prob spin up a small server for this to observe the patterns and IP locations. Also, don't think that posting this blog article on March 22 didn't go unnoticed :)
What is significant about March 22?
This is the Internet equivalent of keeping phone scammers on the line by not just refusing to hang up, but actively interacting with them until they hang up (search YouTube for "tech support scammer trolling" for some entertainment...) That said, I'm a little confused even after reading the linked RFC paragraph; it claims "The primary use of this feature is to allow TCP-wrappers to display an error message before dis…
It does a number of things in userspace (with a simple minimalist code base) that people might nowadays more often do in a firewall.
> Captures and holds incoming TCP connections using no local per-connection resources. Connections are accepted, but immediately switched to the persist state (0 byte window), in which the remote side stops sending data and asks to continue every 60-240 seconds. Attempts to close the connection are ignored, forcing the remote side to time out the connection in 12-24 minutes.