On 2004.5.3, at 09:36 AM, Sherm Pendley wrote:
On May 2, 2004, at 8:17 PM, Joel Rees wrote:
I think I was told by someone that Perl's input buffer would adjust to this kind of insanely long line. Does it slow the input down much to have to re-allocate the buffer?
I doubt it. This sort of stuff is precisely what Perl was originally made to do. Larry Wall needed to merge and filter log files from several JPL sites, and sed wasn't quite flexible enough for the job. Thus, Perl was born.
That's what I've heard, but nothing comes for free. Well, instead of asking about what might go wrong, I suppose I should just try it.
8-o
(And sometime I'd like to build an error page script that would dump 64K from /random back at the zombie.
I *completely* agree with the sentiment, but beware of collateral damage.
Yeah, dumping from /random really isn't very sporting, strategic, or effective. I'm just thinking about this itch I want to scratch.
With the low probability of getting the admin user's attention, and the low probability of the admin user knowing what to if you did, the sensible solution is just making sure apache doesn't get taken down by the malformed queries, rotating and compressing the logs, and writing a tool to make the other accesses visible around the sight-blocking attack vector.
A lot of this stuff comes from third-party machines that have been hijacked. The owners are often innocent dupes who aren't even aware their machines are spewing this stuff.
I know that. But there's a limit to the innocence in being a dupe. And it still itches. :-/
I'm wasting bandwidth daydreaming, I think.
--
Joel Rees
It's not the "Here's a button, click it!" attitude,
It's Bill saying he has to be free to invent our technological future.
(But I'm just as glad it's not Steve's company with the 95%.)
