Bug#122929: tramspap.pl, possible replacement for wpoison
If I'd known headers would be up on the BTS, I would have started with
the also-valid mail address above. 8-( Never mind.
On Tue, Jul 16, 2002 at 12:31:41PM +0200, Robert Millan wrote:
> On Tue, Jul 16, 2002 at 02:41:16AM +0100, Matthew Astley wrote:
> > I've pulled this down from http://bugs.debian.org/122929 , forgive
> > me for the confusion. I'm not a Debian maintainer, but I probably
> > should be. 9-)
>
> Are you taking this RFP? In that case please retitle the bug to
> start with "ITP"
No, I meant "pull down" in the sense of stealing the message-id and
subject line, really. I think I expected some different flavour of
confusion. 8-}
> This is great news. I gave up on wpoison because it had very
> unproper license restrictions, and upstream wasn't maintaining it.
IMHO doing something moderately useful is likely to create better
publicity than insisting on getting links up all over.
> > If you're still interested in this sort of thing, you can prod it from
> > http://www.t8o.org/ .
>
> It's down at the moment.
For a change, it's not NTL. http://bugs.debian.org/133790 8-(
Oh whoops, I should've hit that with the browser first, rather than
taking reportbug's perspective (ie. first message only). D'ya think I
should file against reportbug? Seems a bit trigger-happy, but a "don't
forget to read the whole thing" warning might save some embarrassment
for someone.
> > Subject to seeing the spambots reaction to the thing when it next
> > visits, I've probably lost interest in the thing for now though,
> > sorry.
>
> Do you have a sponsor to get it in Debian?
No. I know a couple of maintainers, but I've not asked for
sponsorship. I don't know exactly what this requires them to do, or
what sort of standing they require. Will read stuff "later".
Also, I think "tramspap" should have a few more tricks up its sleeve
before being turned loose on the world. For example, I've just
discovered that any sort of multi-threaded crawler will very
effectively DoS the Apache by using up all eight threads. Oops.
I can't see a sane answer to this one. You _have_ to tie up the Apache
process while you're returning HTML at 1cps.
Perhaps the tarpitting aspect could be handled by a special Apache
module which accepts a bufferful of data and returns it slowly, while
still accepting the next connection?
It would appear to be valid to fork off some trivial process to handle
the squirt of data. All that's required is "feed this data out slowly,
until they go away or you run out of data". There's no reason to
accept input, provided the keep-alive has been disabled.
Matthew #8-)
--
To UNSUBSCRIBE, email to debian-wnpp-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: