Jay Berkenbilt wrote:
> Jay Berkenbilt wrote:
>
>> So basically, as far as I can tell, the only remaining actions to get us
>> caught up are to apply CVE-2013-1961 to tiff in squeeze. I can prepare
>> a security upload for that.
>
> Oops, I meant to say to apply the patch from tiff in squeeze t
Jay Berkenbilt wrote:
> So basically, as far as I can tell, the only remaining actions to get us
> caught up are to apply CVE-2013-1961 to tiff in squeeze. I can prepare
> a security upload for that.
Oops, I meant to say to apply the patch from tiff in squeeze to tiff3 in
sid.
--
To UNSUBSCR
Michael Gilbert wrote:
> package: src:tiff3
> severity: grave
> version: 3.9.6-11
> tag: security
>
> The tiff package has had multiple security issues recently. tiff3,
> being an old version, is also affected by a subset of them, of which I
> haven't fully checked yet:
> https://security-tracke
Michael Gilbert wrote:
> package: src:tiff3
> severity: grave
> version: 3.9.6-11
> tag: security
>
> The tiff package has had multiple security issues recently. tiff3,
> being an old version, is also affected by a subset of them, of which I
> haven't fully checked yet:
> https://security-tracke
package: src:tiff3
severity: grave
version: 3.9.6-11
tag: security
The tiff package has had multiple security issues recently. tiff3,
being an old version, is also affected by a subset of them, of which I
haven't fully checked yet:
https://security-tracker.debian.org/tracker/source-package/tiff
5 matches
Mail list logo
