On Wed, Aug 16, 2017 at 10:37:40PM +0200, Thomas Danckaert wrote:
> With some delay... here's a patch to revert freerdp to the tip of upstream
> branch 1.1 (which includes the CVE fixes, backported by the FreeRDP
> maintainers), and allow vinagre to build against that. Vinagre is the only
> Guix
Thomas Danckaert <p...@thomasdanckaert.be> writes:
> From: Leo Famulari <l...@famulari.name>
> Subject: Re: bug#27939: FreeRDP CVE-2017-2834 CVE-2017-2835
> CVE-2017-2836 CVE-2017-2837 CVE-2017-2838 CVE-2017-2839
> Date: Fri, 4 Aug 2017 10:56:15 -0400
>
>> O
From: Leo Famulari <l...@famulari.name>
Subject: Re: bug#27939: FreeRDP CVE-2017-2834 CVE-2017-2835
CVE-2017-2836 CVE-2017-2837 CVE-2017-2838 CVE-2017-2839
Date: Fri, 4 Aug 2017 10:56:15 -0400
On Fri, Aug 04, 2017 at 10:34:55AM +0200, Thomas Danckaert wrote:
Unfortunately, vinagre d
On Fri, Aug 04, 2017 at 10:34:55AM +0200, Thomas Danckaert wrote:
> Unfortunately, vinagre doesn't build against freerdp 2. I'll try to fix
> that, or otherwise try to backport the patches to freerdp 1.x.
I think it should not be too hard to backport the patches if that's what
we need to do, but
From: Marius Bakke <mba...@fastmail.com>
Subject: Re: bug#27939: FreeRDP CVE-2017-2834 CVE-2017-2835
CVE-2017-2836 CVE-2017-2837 CVE-2017-2838 CVE-2017-2839
Date: Fri, 04 Aug 2017 01:22:01 +0200
Leo Famulari <l...@famulari.name> writes:
The bugs corresponding to CVE-2017-2834 C
Leo Famulari writes:
> The bugs corresponding to CVE-2017-2834 CVE-2017-2835 CVE-2017-2836
> CVE-2017-2837 CVE-2017-2838 CVE-2017-2839 were recently fixed in the
> FreeRDP Git repo:
>
> https://github.com/FreeRDP/FreeRDP/commit/03ab68318966c3a22935a02838daaea7b7fbe96c
>
> The
The bugs corresponding to CVE-2017-2834 CVE-2017-2835 CVE-2017-2836
CVE-2017-2837 CVE-2017-2838 CVE-2017-2839 were recently fixed in the
FreeRDP Git repo:
https://github.com/FreeRDP/FreeRDP/commit/03ab68318966c3a22935a02838daaea7b7fbe96c
The most serious of these bugs allow the remote server (or