Note: Most of this was discussed on IRC.
On Mon, Mar 31, 2014 at 6:20 PM, Michael DePaulo mikedep...@gmail.com wrote:
On Mon, Mar 31, 2014 at 10:09 AM, Mike Gabriel
mike.gabr...@das-netzwerkteam.de wrote:
Hi Michael,
On Mo 31 Mär 2014 15:19:07 CEST, Michael DePaulo wrote:
The latest
On Sun, Apr 6, 2014 at 8:58 AM, Michael DePaulo mikedep...@gmail.com wrote:
.
However, after trying lots of things out, I managed to compile VcXsrv
1.14.3 (2013-09-20) with Windows XP support, and with the fixes for
CVE-2013-4396 (2013-10-08) CVE-2013-6462 (2014-01-07).
I also determined
On Sun, Apr 6, 2014 at 10:11 AM, Michael DePaulo mikedep...@gmail.com wrote:
On Sun, Apr 6, 2014 at 8:58 AM, Michael DePaulo mikedep...@gmail.com wrote:
.
However, after trying lots of things out, I managed to compile VcXsrv
1.14.3 (2013-09-20) with Windows XP support, and with the fixes for
Now that I've also updated the approach for fixing #422 (as documented
in the BTS,) I am OK with releasing 4.0.2.0.
-Mike#2
___
X2Go-Dev mailing list
X2Go-Dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/x2go-dev
Also, I did report the vulnerability as a bug in VcXsrv's bug tracker
6 days ago:
https://sourceforge.net/p/vcxsrv/bugs/17/
On Mon, Mar 31, 2014 at 9:19 AM, Michael DePaulo mikedep...@gmail.com wrote:
The latest version of VcXsrv, 1.15.0, contains the vulnerability
CVE-2013-6462 in the
The latest version of VcXsrv, 1.15.0, contains the vulnerability
CVE-2013-6462 in the component libXfont 1.4.6.
The vulnerability is fixed in libXfont 1.4.7 and VcXsrv's master
branch contains that update/fix.
I just sent the VcXsrv developer marha a message through
SourceForge.net. I am hoping
Hi Michael,
On Mo 31 Mär 2014 15:19:07 CEST, Michael DePaulo wrote:
The latest version of VcXsrv, 1.15.0, contains the vulnerability
CVE-2013-6462 in the component libXfont 1.4.6.
The vulnerability is fixed in libXfont 1.4.7 and VcXsrv's master
branch contains that update/fix.
I just sent
On Mon, Mar 31, 2014 at 10:09 AM, Mike Gabriel
mike.gabr...@das-netzwerkteam.de wrote:
Hi Michael,
On Mo 31 Mär 2014 15:19:07 CEST, Michael DePaulo wrote:
The latest version of VcXsrv, 1.15.0, contains the vulnerability
CVE-2013-6462 in the component libXfont 1.4.6.
The vulnerability is
On Mi 19 Mär 2014 04:59:30 CET, Michael DePaulo wrote:
On Sun, Mar 16, 2014 at 1:37 PM, Michael DePaulo
mikedep...@gmail.com wrote:
On Sun, Mar 16, 2014 at 1:24 PM, Mike Gabriel
mike.gabr...@das-netzwerkteam.de wrote:
Also, since it is a regression, I would like to spend until the end of
On Wed, Mar 19, 2014 at 3:03 AM, Mike Gabriel
mike.gabr...@das-netzwerkteam.de wrote:
On Mi 19 Mär 2014 04:59:30 CET, Michael DePaulo wrote:
3. Tomorrow I would put out a nightly build out with following newer
dependencies. I would appreciate a few days for testing:
-Latest Cygwin files
On Sun, Mar 16, 2014 at 1:37 PM, Michael DePaulo mikedep...@gmail.com wrote:
On Sun, Mar 16, 2014 at 1:24 PM, Mike Gabriel
mike.gabr...@das-netzwerkteam.de wrote:
Also, since it is a regression, I would like to spend until the end of
Monday (tomorrow) night looking into bug 448 and hopefully
Mike,
As I mentioned on IRC, I accidentally applied the commit to the master
branch. Let me know how you want me to proceed.
Also, since it is a regression, I would like to spend until the end of
Monday (tomorrow) night looking into bug 448 and hopefully fixing it
by then.
On Fri, Mar 14, 2014
Hi Michael,
On So 16 Mär 2014 17:16:35 CET, Michael DePaulo wrote:
As I mentioned on IRC, I accidentally applied the commit to the master
branch. Let me know how you want me to proceed.
The way to do such a dual branch commit properly is this:
o Checkout the release/4.0.1.x branch
o
On Sun, Mar 16, 2014 at 1:24 PM, Mike Gabriel
mike.gabr...@das-netzwerkteam.de wrote:
Hi Michael,
a follow-up thought...
We should not provide 4.0.1.4 for Windows. Only 4.0.2.0.
The reason for the dual upcoming release is that distros that have an old
libssh have the choice to use a legacy
I believe I've found a simple fix for bug 422. I posted the details to
the bug tracker. Please give me until Sunday night to write, test and
commit it.
On Tue, Mar 11, 2014 at 11:56 PM, Michael DePaulo mikedep...@gmail.com wrote:
I did some more investigation today, but could not find the cause
Am 09.03.2014 16:33, schrieb Andreas Radke:
How are things going? Now that libssh 0.6.3 is out my distro wants to
update it. How's x2goclient doing? Can we expect a quick release or
how's git status?
Note: Bug #448 might be libssh-related. Not sure if it only occurs on
Windows.
Hi Andreas,
On So 09 Mär 2014 16:33:54 CET, Andreas Radke wrote:
How are things going? Now that libssh 0.6.3 is out my distro wants to
update it. How's x2goclient doing? Can we expect a quick release or
how's git status?
The current Git master's HEAD builds against and runs well with libssh
Now that we have automated builds of x2goclient, I would like to try
to fix 422 so we can include pulseaudio 5.0:
http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=422
This will be a better fix for 363, which is already marked Done:
http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=363
On Wed, Feb 19,
Hi all,
I would like to discuss a possible release date for X2Go Client 4.0.2.0.
As I see we need to fix #434 before a release is sensible. Any other
open issues that people would like to see fixed before the release?
Mike
--
DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
fon: +49
19 matches
Mail list logo
