All the Perl that's Practical to Extract and Report
use Perl Log In
barbie (2653)
reversethis-{ku. ... m} {ta} {eibrab}
http://barbie.missbarbell.co.uk/
Leader of Birmingham.pm [pm.org] and a CPAN author [cpan.org]. Co-organised YAPC::Europe in 2006 and the 2009 QA Hackathon, responsible for the YAPC Conference Surveys [yapc-surveys.org] and the QA Hackathon [qa-hackathon.org] websites. Also the current caretaker for the CPAN Testers websites and data stores.
If you really want to find out more, buy me a Guinness
Links:
Memoirs of a Roadie [missbarbell.co.uk]
[pm.org]
CPAN Testers Reports [cpantesters.org]
YAPC Conference Surveys [yapc-surveys.org]
QA Hackathon [qa-hackathon.org]
No PHP here, mate
I'm not sure whether this is amusing or embarrassing:
80.93.48.103 - - [13/Jul/2009:16:30:21 +0200] "GET
In case you're wondering, the above is an entry from the access logs on the CPAN Testers server. The script they are trying to access doesn't exist, and from what I can tell it's a poor attempt at crashing a server. The bit that amused me is that they're using LWP to run a PHP app. The bit that's embarrassing is that Perl is being used for undesirable purposes
--Larry Wall in stab.c from the perl source code
Bog standard (Score:1)
That’s just an automated trying to exploit some known hole or other in WordPress. PHP’s
requirecan load libraries from remote machines over HTTP, and many PHP programs use dynamicrequires` without sufficiently sanitising the input, resulting in a holes exploitable in the way you see in your logs.As for Perl being used for that purpose, eh, so what? If it wasn’t, it’d be
wget, or something Python, or in Ruby, or in Java, or whatever.