Re^2: Perl 5.16 binary filename security problem?

Replies are listed 'Best First'.
Re^3: Perl 5.16 binary filename security problem? by Your Mother (Archbishop) on Jul 17, 2012 at 02:55 UTC
I must say, I don't think keeping the exploits secret, when the software is not going to be ~~changes~~ changed to address them, is a good idea. Apparently the appropriate line of defense (I agree with what Chip Salzenberg said at the end of the thread) is with the dev anyway. I R DEV. THIS THREAD IS IN MY INTREST.	[reply]
Re^3: Perl 5.16 binary filename security problem? by Anonymous Monk on Jul 17, 2012 at 05:40 UTC
And how many $s does it take to corrupt a perl dev on that list and get a zero day?	[reply]
Re^4: Perl 5.16 binary filename security problem? by chip (Curate) on Sep 06, 2012 at 03:42 UTC
There is no basis to insinuate corruption in Perl's security list. this is a red herring. Responsible disclosure has two parts: RESPONSIBLE and DISCLOSURE. Reini has failed at disclosure, and his continued baseless rumormongering fails at responsibility.	[reply]


Do you know where your variables are?
	PerlMonks