Hello dear maintainer(s),
the Debian LTS team would like to fix the security issues which are
currently open in the Wheezy version of chicken:
https://security-tracker.debian.org/tracker/CVE-2016-6830
https://security-tracker.debian.org/tracker/CVE-2016-6831
Would you like to take care of this yo
Hello dear maintainer(s),
the Debian LTS team would like to fix the security issues which are
currently open in the Wheezy version of chicken:
https://security-tracker.debian.org/tracker/source-package/chicken
Would you like to take care of this yourself?
If yes, please follow the workflow we ha
Dear maintainer(s),
The Debian LTS team would like to fix the security issues which are
currently open in the Wheezy version of chicken:
https://security-tracker.debian.org/tracker/CVE-2017-9334
Would you like to take care of this yourself?
If yes, please follow the workflow we have defined here
I just had a look at CVE-2016-6830.
https://security-tracker.debian.org/tracker/CVE-2016-6830
refers to:
http://lists.nongnu.org/archive/html/chicken-announce/2016-08/msg1.html
Which has the following text:
"A fix has been implemented in master d866ac1 and chicken-5 c598381.
The patch for
Brian May writes:
> I just had a look at CVE-2016-6830.
I was going to look at CVE-2016-6831 seperately, however it looks like
this was fixed at the same time as CVE-2016-6830
http://seclists.org/oss-sec/2016/q3/308
--
Brian May
Brian May wrote:
> It looks like this patch involves refactoring of the code. Which is
> going to make it more complicated applying it to the wheezy version.
Indeed. In fact, when I was working back from this patch it was not
immediately obvious that wheezy was vulnerable due to the changes...
Brian May writes:
> I just had a look at CVE-2016-6830.
>
> https://security-tracker.debian.org/tracker/CVE-2016-6830
>
> refers to:
>
> http://lists.nongnu.org/archive/html/chicken-announce/2016-08/msg1.html
I checked this again.
Now refers to
https://lists.nongnu.org/archive/html/chicken-
