fixed 670586 3.5.16-13
thanks
And so, we've been corresponding on the wrong bug report :( Sorry, I
forgot to change the bug number in the subject line and so I confused
the Cc: address as well.
Please change the bug number to 673053 in the Subject: and Cc: in any
follow-ups on Taylor's issue.
On Fri, May 11, 2012 at 09:27:51AM +0200, Mike Hommey wrote:
> On Fri, May 11, 2012 at 09:10:24AM +0200, Mike Hommey wrote:
> > On Thu, May 10, 2012 at 08:34:21PM +0100, Steven Chamberlain wrote:
> > > Hi Mike,
> > >
> > > Are we sure that iceweasel 3.5.x needed this security fix in the first
> >
On Fri, May 11, 2012 at 09:10:24AM +0200, Mike Hommey wrote:
> On Thu, May 10, 2012 at 08:34:21PM +0100, Steven Chamberlain wrote:
> > Hi Mike,
> >
> > Are we sure that iceweasel 3.5.x needed this security fix in the first
> > place? Any ideas which issue bug #732951 referred to and if it was
> >
On Thu, May 10, 2012 at 08:34:21PM +0100, Steven Chamberlain wrote:
> Hi Mike,
>
> Are we sure that iceweasel 3.5.x needed this security fix in the first
> place? Any ideas which issue bug #732951 referred to and if it was
> exploitable here?
>
> The CVE's only refer to versions 4.x through 11.x
Hi Mike,
Are we sure that iceweasel 3.5.x needed this security fix in the first
place? Any ideas which issue bug #732951 referred to and if it was
exploitable here?
The CVE's only refer to versions 4.x through 11.x (I guess because those
are the maintained ones, though).
Regards,
--
Steven Cha
On Thu, May 10, 2012 at 09:21:19PM +0200, Mike Hommey wrote:
> On Wed, May 09, 2012 at 01:58:27PM +0100, Steven Chamberlain wrote:
> > On 09/05/12 08:43, Mike Hommey wrote:
> > > On Tue, May 08, 2012 at 11:51:45PM +0100, Steven Chamberlain wrote:
> > >> I've narrowed the regression down to this (so
On Wed, May 09, 2012 at 01:58:27PM +0100, Steven Chamberlain wrote:
> On 09/05/12 08:43, Mike Hommey wrote:
> > On Tue, May 08, 2012 at 11:51:45PM +0100, Steven Chamberlain wrote:
> >> I've narrowed the regression down to this (somewhat secretive) patch:
> >> squeeze-patches/Bug-732951.-r-bsmedberg
On 09/05/12 08:43, Mike Hommey wrote:
> On Tue, May 08, 2012 at 11:51:45PM +0100, Steven Chamberlain wrote:
>> I've narrowed the regression down to this (somewhat secretive) patch:
>> squeeze-patches/Bug-732951.-r-bsmedberg-a-akeybl.patch
> Could you check with the attached patch?
Sorry, hasn't w
On Tue, May 08, 2012 at 11:51:45PM +0100, Steven Chamberlain wrote:
> Hi again,
>
> I've narrowed the regression down to this (somewhat secretive) patch:
>
> squeeze-patches/Bug-732951.-r-bsmedberg-a-akeybl.patch
>
> I verified that on my own build of iceweasel 3.5.16-14 I could reproduce
> the
Hi again,
I've narrowed the regression down to this (somewhat secretive) patch:
squeeze-patches/Bug-732951.-r-bsmedberg-a-akeybl.patch
I verified that on my own build of iceweasel 3.5.16-14 I could reproduce
the crash; and that reverting that commit prevents it.
Regards,
--
Steven Chamberlain
Hi,
Here is a new backtrace, with the necessary debug symbols this time:
> Program terminated with signal 11, Segmentation fault.
> #0 0x7f65008c0ebb in raise (sig=) at
> ../nptl/sysdeps/unix/sysv/linux/pt-raise.c:41
> 41../nptl/sysdeps/unix/sysv/linux/pt-raise.c: No such file or direct
retitle 670586 iceweasel: [regression 3.5.16-13 > 14] JavaScript SIGSEGV
tags 670586 + squeeze security
reassign 670586 src:iceweasel
fixed 670586 iceweasel/3.5.16-13
found 670586 iceweasel/3.5.16-14
thanks
Hi,
I separately observed this crash, triggered reproducibly on the eBay
website, and real
12 matches
Mail list logo
