--[ UxBoD ]-- schrieb:

----- Original Message -----

...

Hi,

would you have any details on how you compiled OpenSSH for Windows please ? We are experiencing an issue we believe may be due to the age of the distributed SSH client and would like to update it to the latest release.

Have successfully compiled SSH, with the X2go patches, though it is throwing an error about home directory creation. Would you be able to post your configure parameters please ?

Hello, we using ssh compiled under cygwin from sources shipped with cygwin with default options:

./configure && make

regards

Oleksandr Shneyder Dipl. Informatik X2go Core Developer Team

email: oleksandr.shneyder@obviously-nice.de web: www.obviously-nice.de

--> X2go - everywhere@home

----- Original Message -----

----- Original Message -----

...

--[ UxBoD ]-- schrieb:

...

----- Original Message -----

...

Hi,

would you have any details on how you compiled OpenSSH for Windows please ? We are experiencing an issue we believe may be due to the age of the distributed SSH client and would like to update it to the latest release.

Have successfully compiled SSH, with the X2go patches, though it is throwing an error about home directory creation. Would you be able to post your configure parameters please ?

Hello, we using ssh compiled under cygwin from sources shipped with cygwin with default options:

./configure && make

Hmm, okay thanks. It must be due to using OpenSSH V5 then compared to V4 which is shipped with X2go. Darn :( Will see if can find out what is wrong.

Alex, what do the two includes patches to SSH actually do ? I see they set ASKPASS to a different value ?

Thanks, Phil

On Thu, 2010-12-02 at 08:10 +0100, Oleksandr Shneyder wrote:

--[ UxBoD ]-- schrieb:

...

Alex, what do the two includes patches to SSH actually do ? I see they set ASKPASS to a different value ?

It force ssh to use program specified in SSH_ASKPASS environment variable as "askpass" program. In Unix you can do this setting DISPLAY variable and starting ssh with setsid. But in windows the only way was to patch ssh. I think, in release x2go will use libssh instead of ssh. <snip> Very interesting. I wonder if that explains the errors Uxbod was encountering when trying to use newer ssh versions on Windows.

Uxbod, does plink provide a Windows based ASKPASS facility?

Alex and Heinz, is there any version of X2Go available yet with libssh? Using plink (assuming it supports ASKPASS) would require an awful amount of hacking and conditional formatting of parameters. A consistent, cross-platform API would be so much easier. Thanks - John

On Mon, 2010-12-06 at 20:38 +0100, Heinz-M. Graesing wrote:

Hello John,

Am 02.12.2010 17:49, schrieb John A. Sullivan III:

...

Alex and Heinz, is there any version of X2Go available yet with libssh? Using plink (assuming it supports ASKPASS) would require an awful amount of hacking and conditional formatting of parameters. A consistent, cross-platform API would be so much easier. Thanks - John

There is a first version of x2go using libssh ready for testing. You'll need to have the heuler repository added to your sources list:

# x2go testing repository: deb http://x2go.obviously-nice.de/deb/ heuler main

"heuler" is an additional reopsitory!

There too is a windows version of x2goclient using libssh ready for testing:

http://x2go.obviously-nice.de/deb/windows/x2goclient-3.01-14-setup.exe

If you are looking for the source code, you'll find it as usual as *.tar.gz file in the repository folders:

http://x2go.obviously-nice.de/deb/pool-heuler/x2goclient/x2goclient_3.01-14....

We would like to invite you to test this new version and give us feedback.

I'll post this message also to the announcement list. Please keep in mind, that we'll use this list for further announcements.

Regards,

Alex and Heinz <snip> Thanks, Heinz.

Phil, this is quite important for us at it eliminates the need to fiddle with plink and, I assume, gives us a much newer version of ssh which may address some of the timing issues we seem to be having - John

----- Original Message -----

----- Original Message -----

...

On Mon, 2010-12-06 at 20:38 +0100, Heinz-M. Graesing wrote:

...

Hello John,

Am 02.12.2010 17:49, schrieb John A. Sullivan III:

...

Alex and Heinz, is there any version of X2Go available yet with libssh? Using plink (assuming it supports ASKPASS) would require an awful amount of hacking and conditional formatting of parameters. A consistent, cross-platform API would be so much easier. Thanks - John

There is a first version of x2go using libssh ready for testing. You'll need to have the heuler repository added to your sources list:

# x2go testing repository: deb http://x2go.obviously-nice.de/deb/ heuler main

"heuler" is an additional reopsitory!

There too is a windows version of x2goclient using libssh ready for testing:

http://x2go.obviously-nice.de/deb/windows/x2goclient-3.01-14-setup.exe

If you are looking for the source code, you'll find it as usual as *.tar.gz file in the repository folders:

http://x2go.obviously-nice.de/deb/pool-heuler/x2goclient/x2goclient_3.01-14....

We would like to invite you to test this new version and give us feedback.

I'll post this message also to the announcement list. Please keep in mind, that we'll use this list for further announcements.

Regards,

Alex and Heinz <snip> Thanks, Heinz.

Phil, this is quite important for us at it eliminates the need to fiddle with plink and, I assume, gives us a much newer version of ssh which may address some of the timing issues we seem to be having - John

Heinz, does this still use the 2009.04 release of Qt or the latest one ? My computer has just spent the last 14 hours (windows vm) recompiling Qt with SSL support and the X2go client still fails to compile:

mingw32-make[1]: Entering directory C:/x2goclient-3.01' g++ -enable-stdcall-fixup -Wl,-enable-auto-import -Wl,-enable-runtime-pseudo-reloc -Wl,-s -mthreads -Wl -Wl,-subsystem,windows -o release\x2goplugin.exe object_script.x2goplugin.Release -L"c:\Qt-Static\qt\lib" -lmingw32 -lqtmain release\x2goclient_res.o -lQtSvg -lQtNetwork -lQtGui -lgdi32 -lcomdlg32 -loleaut32 -limm32 -lwinmm -lwinspool -lmsimg32 -lQtCore -lkernel32 -luser32 -lshell32 -luuid -lole32 -ladvapi32 -lws2_32 -L\cygwin\openssl\lib c:\Qt-Static\qt\lib/libqtmain.a(qtmain_win.o):qtmain_win.cpp:(.text+0x204): undefined reference to qMain(int, char**)' collect2: ld returned 1 exit status mingw32-make[1]: *** [release\x2goplugin.exe] Error 1 mingw32-make[1]: Leaving directory `C:/x2goclient-3.01' mingw32-make: *** [release] Error 2

Qt compiled fine and reported no errors so am at a bit of a loss at the moment. It would be so hopefully to us is you were able to provide help in getting a duplicate environment as to what you use built.

Right then, laptop is about to been thrown cleanly straight out of the window as I have spent to much of my companies, and my own time, attempting to compile the x2goclient. Well to qualify that it has been more of the case of compiling Qt and libssh under Windows. Qt and trying to make it static was a complete failure, and libssh under Cygwin falls into a heap aswell.

I am now going down the Linux route which in some ways appears to be just as difficult especially when attempting to build the Mingw toolchain due to my OS (64 bit Ubuntu 10.10). I believe it needs to be building as mingw-i686 and therefore 32 bit which is giving all sorts of library issues.

Am really reaching out to the devs to try and understand how they have built their own environments; as we will be attempting to also use the latest version of Qt and get X2goclient to work with it.

Please please help as my hair is short enough and cannot take anymore being pulled out ;)

Thanks, Phil

----- Original Message -----

--[ UxBoD ]-- schrieb:

...

----- Original Message -----

...

...

mingw32-make[1]: Entering directory C:/x2goclient-3.01' g++ -enable-stdcall-fixup -Wl,-enable-auto-import -Wl,-enable-runtime-pseudo-reloc -Wl,-s -mthreads -Wl -Wl,-subsystem,windows -o release\x2goplugin.exe object_script.x2goplugin.Release -L"c:\Qt-Static\qt\lib" -lmingw32 -lqtmain release\x2goclient_res.o -lQtSvg -lQtNetwork -lQtGui -lgdi32 -lcomdlg32 -loleaut32 -limm32 -lwinmm -lwinspool -lmsimg32 -lQtCore -lkernel32 -luser32 -lshell32 -luuid -lole32 -ladvapi32 -lws2_32 -L\cygwin\openssl\lib c:\Qt-Static\qt\lib/libqtmain.a(qtmain_win.o):qtmain_win.cpp:(.text+0x204): undefined reference to qMain(int, char**)' collect2: ld returned 1 exit status mingw32-make[1]: *** [release\x2goplugin.exe] Error 1 mingw32-make[1]: Leaving directory `C:/x2goclient-3.01' mingw32-make: *** [release] Error 2

Qt compiled fine and reported no errors so am at a bit of a loss at the moment. It would be so hopefully to us is you were able to provide help in getting a duplicate environment as to what you use built.

Right then, laptop is about to been thrown cleanly straight out of the window as I have spent to much of my companies, and my own time, attempting to compile the x2goclient. Well to qualify that it has been more of the case of compiling Qt and libssh under Windows. Qt and trying to make it static was a complete failure, and libssh under Cygwin falls into a heap aswell.

I am now going down the Linux route which in some ways appears to be just as difficult especially when attempting to build the Mingw toolchain due to my OS (64 bit Ubuntu 10.10). I believe it needs to be building as mingw-i686 and therefore 32 bit which is giving all sorts of library issues.

Am really reaching out to the devs to try and understand how they have built their own environments; as we will be attempting to also use the latest version of Qt and get X2goclient to work with it.

Please please help as my hair is short enough and cannot take anymore being pulled out ;)

Hi,

To build newest version of x2goclient under windows you need:

1. Qt SDK. I didn't tested newest version. 2009.04 and 2010.04 work. Use mingw version. You can also use msvc version, but you should build libssh using msvc and I have not experience how to do this. If you want link Qt statically you must reconfigure and rebuild Qt. Don't forget include ssl support by configuration of Qt.

2. Get master branch of libssh: http://git.libssh.org/projects/libssh/libssh.git/snapshot/master.zip To compile it your need cmake, libssl and zlib. You need master branch, release libssh 0.4.6 will not work with x2goclient. If you don't want to build libssh by yourself, you can download working version here: http://x2go.obviously-nice.de/deb/libssh/libssh-x2go.zip unpack this file and install libssh in mingw directory which shipped with Qt SDK.

include/libssh/* -> mingw/include/libssh/ lib/libssh.dll.a -> mingw/lib/

you must provide libssh.dll and zlib1.dll with your build of x2goclient

3. Configure x2goclient to build client, not plugin. Edit file x2goclientconfig.pri:

CONFIG += client

#uncomment this line to build x2goclient plugin #CONFIG += plugin

plugin { CONFIG -= client }

run qmake to create Makefile and mingw32-make to build x2goclient

That's all

Regards,

Oleksandr Shneyder Dipl. Informatik X2go Core Developer Team

email: oleksandr.shneyder@obviously-nice.de web: www.obviously-nice.de

--> X2go - everywhere@home

Hi Alex,

Thank you for the detailed steps. May I ask if you rebuilt Qt, statically, under Windows or has all your work been performed under Linux ? I have tried both of those Qt versions and ran configure.exe -static -openssl -I<path_to_openssl_include> -L<path_to_openssl_libs> and it failed to compile when running mingw32-make sub-src.

I must be doing something crazily wrong in the way I am rebuilding Qt :(

Thanks, Phil

----- Original Message -----

--[ UxBoD ]-- schrieb:

...

----- Original Message -----

...

Hi Alex,

Thank you for the detailed steps. May I ask if you rebuilt Qt, statically, under Windows or has all your work been performed under Linux ? I have tried both of those Qt versions and ran configure.exe -static -openssl -I<path_to_openssl_include> -L<path_to_openssl_libs> and it failed to compile when running mingw32-make sub-src.

I must be doing something crazily wrong in the way I am rebuilding Qt :(

I'm configure and build Qt always under windows. My configuration options are:

-release -static -openssl -qt-style-windowsxp -qt-style-windowsvista

openssl installed under c:\Program Files\openssl

regards,

Hi Alex,

I finally managed to build Qt! Now onto libssh in the latest x2go-client. I am guess that I need to apply the diff and then build it ? Do you perform the compile under Cygwin or use MinGW32 ?

Thanks, Phil

----- Original Message -----

--[ UxBoD ]-- schrieb:

...

----- Original Message -----

...

...

----- Original Message ----- Hi Alex,

Thank you for the detailed steps. May I ask if you rebuilt Qt, statically, under Windows or has all your work been performed under Linux ? I have tried both of those Qt versions and ran configure.exe -static -openssl -I<path_to_openssl_include> -L<path_to_openssl_libs> and it failed to compile when running mingw32-make sub-src.

I must be doing something crazily wrong in the way I am rebuilding Qt :( I'm configure and build Qt always under windows. My configuration

--[ UxBoD ]-- schrieb: options are:

-release -static -openssl -qt-style-windowsxp -qt-style-windowsvista

openssl installed under c:\Program Files\openssl

regards,

Hi Alex,

I finally managed to build Qt! Now onto libssh in the latest x2go-client. I am guess that I need to apply the diff and then build it ? Do you perform the compile under Cygwin or use MinGW32 ?

Hello,

As I wrote in my last e-mail, the changes you need for x2goclient are already in master branch of libssh. You can build it on your system using mingw shipped with Qt SDK (need cmake, libssl and zlib) or get ready for use build from us:

http://x2go.obviously-nice.de/deb/libssh/libssh-x2go.zip

Good morning, Alex

I downloaded the zip file and expanded it into the directory where the x2go client source is. I then ran qmake followed by mingw32-make release and it failed to find the lib ssh include files. It would appear they are actually in libssh/include/libssh so I copied them all upto the top directory. It got a bit further with compilation but now fails trying to find the ssh library. What am I doing so wrong Alex. This appears to be such a complicated compiled task; and I guess it is due to not having certain paths defined somewhere.

Thanks, Phil

On Wed, 2010-12-15 at 11:32 +0100, Oleksandr Shneyder wrote:

--[ UxBoD ]-- schrieb:

...

Good morning, Alex

I downloaded the zip file and expanded it into the directory where the x2go client source is. I then ran qmake followed by mingw32-make release and it failed to find the lib ssh include files. It would appear they are actually in libssh/include/libssh so I copied them all upto the top directory. It got a bit further with compilation but now fails trying to find the ssh library. What am I doing so wrong Alex. This appears to be such a complicated compiled task; and I guess it is due to not having certain paths defined somewhere.

Hello,

It is not complicate at all. Please read careful my Howto and you'll see, that it's very simple:

From Re: [X2go-dev] X2GO and SSH 09.12.2010 17:44 by Oleksandr Shneyder <oleksandr.shneyder@obviously-nice.de>

==============================

unpack this file and install libssh in mingw directory which shipped with Qt SDK.

include/libssh/* -> mingw/include/libssh/ lib/libssh.dll.a -> mingw/lib/

you must provide libssh.dll and zlib1.dll with your build of x2goclient

<snip> Thanks, Oleksandr but I'm a little confused by the above statement. If we are doing static linking, why do we need to distribute libssh.dll and zlib1.dll?

By the way, we have it working now but are just trying to tweak it, e.g., to statically link all libraries so we have a single executable. For example, just as you describe, despite specifying static linking, we seem to need dlls for not only ssh but also openssl. Thanks - John

On Tue, 2010-12-21 at 09:28 +0000, --[ UxBoD ]-- wrote:

----- Original Message -----

...

On Wed, 2010-12-15 at 11:32 +0100, Oleksandr Shneyder wrote:

...

--[ UxBoD ]-- schrieb:

...

Good morning, Alex

I downloaded the zip file and expanded it into the directory where the x2go client source is. I then ran qmake followed by mingw32-make release and it failed to find the lib ssh include files. It would appear they are actually in libssh/include/libssh so I copied them all upto the top directory. It got a bit further with compilation but now fails trying to find the ssh library. What am I doing so wrong Alex. This appears to be such a complicated compiled task; and I guess it is due to not having certain paths defined somewhere.

Hello,

It is not complicate at all. Please read careful my Howto and you'll see, that it's very simple:

From Re: [X2go-dev] X2GO and SSH 09.12.2010 17:44 by Oleksandr Shneyder <oleksandr.shneyder@obviously-nice.de>

==============================

unpack this file and install libssh in mingw directory which shipped with Qt SDK.

include/libssh/* -> mingw/include/libssh/ lib/libssh.dll.a -> mingw/lib/

you must provide libssh.dll and zlib1.dll with your build of x2goclient

<snip> Thanks, Oleksandr but I'm a little confused by the above statement. If we are doing static linking, why do we need to distribute libssh.dll and zlib1.dll?

By the way, we have it working now but are just trying to tweak it, e.g., to statically link all libraries so we have a single executable. For example, just as you describe, despite specifying static linking, we seem to need dlls for not only ssh but also openssl. Thanks - John

Really ? Once I had compiled Qt with the static option it did not list any other DLLs when running through DependancyWalker ? Yes, I wonder if it was a difference in method. I intentionally did not install any dlls in the search path when that option was presented. This way, I could isolate them more easily in preparation for creating an installer. It did not ask for the Qt dlls. It asked for libssh, zlib1, and libeay32. It also asked for gcc and libstdc++ until I learned about those static linker options. Thanks - John