Yes I downloaded the tarball - the CGI.pm contained within does not have this METHOD. Nor does it have the string $content_length. As noted the only place $POST_MAX appears is in the pod with a reference to the missing initialise_globals() sub.
iakobski points out that Object.pm uses State.pm. In State.pm you can find the missing references to $POST_MAX. It must therfore be an installation problem. The pod has just not been updated yet to reflect the new postioning of $POST_MAX. The fact that you seem to be able to do a hand install that gives a functioning (sort of) CGI.pm is a bit worrying as *some* people still insist on hand installs and CGI.pm is so popular this is bound to happen. Oh well what do you expect if you don't read the instructions!
I was having nightmares as I have been pestering my sysadmin to upgrade from 2.75 to 3.01 as the upload method is broken on our 2.75 (you just have to get your file handle the old way).
cheers
tachyon
s&&rsenoyhcatreve&&&s&n.+t&"$'$`$\"$\&"&ee&&y&srve&&d&&print
In reply to Re: Re: A serious security problem with CGI.pm 3.01?
by tachyon
in thread A serious security problem with CGI.pm 3.01?
by tachyon
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |