Perlmonks is a place where people should ask questions. Usually when asking a question you don't expect it to be a bug in Perl. Or if it is you expect someone else to have found it already and there to be a workaround. Therefore it is perfectly appropriate to ask on Perlmonks about things that might be bugs in Perl.
Now new bugs obviously should be reported through the proper channels. But you should encourage people to do that in addition to having asked the appropriate question here rather than telling them to do it instead of posting here. | [reply] |
Yes I reported the problem, bug and fix via perlbug, before sending the news to perlmonks. It seemed appropriate to close out the thread by reporting it here too. The problem will hit anyone who tries to use 5.8.9 for SUID operation.
The problem was described by my previous messages in the thread...
| [reply] |
You did well, but you're out of luck here. Perl-5.8.9 is the last maintenance release of the 5.8 series, so there is no further release that will contain your fix.
Since Nicholas also noted that there's no way to reliably smoke-test setuidperl (because it requires root privileges), its stableness can't be guaranteed, so it will be removed from bleadperl, unless somebody provides the means to test it reliably.
In case you found Nicholas' reply to the ticket a bit harsh, also consider that he spent much of his free time to prepare the release and with calling for real-world testing of the release candidates to prevent exactly the sort of bug you uncovered.
Nobody who used suidperl cared enough to test it before the release, now it's too late.
| [reply] |