Bug#959805: libproxy1-plugin-mozjs: Passes invalid/corrupted strings to FindProxyForURL()

2020-05-06 Thread Iain Lane
On Tue, May 05, 2020 at 06:35:28PM -0400, Jeremy Bicha wrote: > On Tue, May 5, 2020 at 10:33 AM Simon McVittie wrote: > > However, this plugin has a popcon of 108 installations (compared with 27K > > for its webkit counterpart), wasn't shipped in buster, and I don't think > > we consider mozjs68

Bug#959805: libproxy1-plugin-mozjs: Passes invalid/corrupted strings to FindProxyForURL()

2020-05-05 Thread Jeremy Bicha
On Tue, May 5, 2020 at 10:33 AM Simon McVittie wrote: > However, this plugin has a popcon of 108 installations (compared with 27K > for its webkit counterpart), wasn't shipped in buster, and I don't think > we consider mozjs68 to be safe for use with untrusted content (although > PAC is probably

Bug#959805: libproxy1-plugin-mozjs: Passes invalid/corrupted strings to FindProxyForURL()

2020-05-05 Thread Simon McVittie
Package: libproxy1-plugin-mozjs Version: 0.4.15-13 Severity: important Tags: patch upstream Forwarded: https://github.com/libproxy/libproxy/issues/119 I made the mistake of trying to add an autopkgtest to libproxy1-plugin-mozjs, which revealed that it does not, in fact, work. At least when