On Sun, Aug 02, 2020 at 01:09:18PM -0700, Ryan Freeman wrote:
> On Sat, Aug 01, 2020 at 03:47:19AM +, Brian Callahan wrote:
> > Hi ports and Ryan --
> >
> > I noticed via Repology that our version of chocolate-doom is
> > vulnerable to CVE-2020-14983 [0].
> >
> > The simple solution is to
On Sat, Aug 01, 2020 at 03:47:19AM +, Brian Callahan wrote:
> Hi ports and Ryan --
>
> I noticed via Repology that our version of chocolate-doom is
> vulnerable to CVE-2020-14983 [0].
>
> The simple solution is to update to version 3.0.1, which contains the
> fix [1].
>
> Doom works here
On Sat, Aug 01, 2020 at 10:32:53AM -0700, Ryan Freeman wrote:
> On Sat, Aug 01, 2020 at 03:47:19AM +, Brian Callahan wrote:
> > Hi ports and Ryan --
> >
> > I noticed via Repology that our version of chocolate-doom is
> > vulnerable to CVE-2020-14983 [0].
> >
> > The simple solution is to
On Sat, Aug 01, 2020 at 03:47:19AM +, Brian Callahan wrote:
> Hi ports and Ryan --
>
> I noticed via Repology that our version of chocolate-doom is
> vulnerable to CVE-2020-14983 [0].
>
> The simple solution is to update to version 3.0.1, which contains the
> fix [1].
>
> Doom works here
Hi ports and Ryan --
I noticed via Repology that our version of chocolate-doom is
vulnerable to CVE-2020-14983 [0].
The simple solution is to update to version 3.0.1, which contains the
fix [1].
Doom works here for me.
OK?
~Brian
[0] https://nvd.nist.gov/vuln/detail/CVE-2020-14983
[1]
Brian Callahan writes:
> Hi ports and Ryan --
>
> I noticed via Repology that our version of chocolate-doom is
> vulnerable to CVE-2020-14983 [0].
>
> The simple solution is to update to version 3.0.1, which contains the
> fix [1].
>
> Doom works here for me.
In my testing singleplayer and
