Re: CVE-2016-1238: Important unsafe module load path flaw

On Mon, Jul 25, 2016 at 03:11:40PM -0700, Andrew Fresh wrote:
> I didn't find a good way to update Porting/Maintainers.PL so that I did
> skip due to lack of time, but that didn't seem *too* important.
> (If someone knows how to bump that other than manually, I'd love to know)

I've attached the tool I used when generating the customized entries
for the patches in 5.24/5.22.

You still need to manually update Maintainers.pl (and -regen for
customized.dat), but it saves having to mess around with formatting.

I'll put this into Porting/ in blead at some point.

Tony

• CVE-2016-1238: Important unsafe module load path flaw by Sawyer X
• Re: CVE-2016-1238: Important unsafe module load path flaw by Craig A. Berry
• Re: CVE-2016-1238: Important unsafe module load path flaw by Dominic Hargreaves
• Re: CVE-2016-1238: Important unsafe module load path flaw by John Lightsey
• Re: CVE-2016-1238: Important unsafe module load path flaw by Andrew Fresh
• Re: CVE-2016-1238: Important unsafe module load path flaw by Tony Cook
• Re: CVE-2016-1238: Important unsafe module load path flaw by Tony Cook
• Re: CVE-2016-1238: Important unsafe module load path flaw by Father Chrysostomos
• Re: CVE-2016-1238: Important unsafe module load path flaw by Sawyer X
• Re: CVE-2016-1238: Important unsafe module load path flaw by Father Chrysostomos