Maybe I’m reading this wrong, but I think it may still be a quoting issue.  Here’s what I see.  In the following debug messages, it appears to be sending a command - “export HOSTNAME && x2golistsessions” - to the server, and processing its output.  When I run this from the command line, I get the following output:

X2GODATABEGIN:7542493b-a84b-418d-994c-d640b3d91ef5
X2GODATAEND:7542493b-a84b-418d-994c-d640b3d91ef5

This is just the session frame, with no text.  However, when the x2go client runs it, it seems to see the following between those two lines:

; export PATH=/usr/local/bin:/usr/bin:/bin; export HOSTNAME

Unless I’m misinterpreting something, this is actually part of the command string, and not its output.  The relevant debug output it below.

Thanks!

David



x2go-DEBUG-../src/sshprocess.cpp:199> Executing remote command via SshProcess object 0: "export HOSTNAME && x2golistsessions"
x2go-DEBUG-../src/sshprocess.cpp:234> Evoking SSH command via SshProcess object 0: "ssh -o ServerAliveInterval=60  -K  -o GSSApiAuthentication=yes -o PasswordAuthentication=no -o PubkeyAuthentication=no -p 22 -l dritch dritch-cuda.dev.cyberpointllc.com "bash -c 'echo \"X2GODATABEGIN:7542493b-a84b-418d-994c-d640b3d91ef5\"; export PATH=\"/usr/local/bin:/usr/bin:/bin\"; export HOSTNAME && x2golistsessions; echo \"X2GODATAEND:7542493b-a84b-418d-994c-d640b3d91ef5\";'""
x2go-DEBUG-../src/sshprocess.cpp:494> SSH process exit code :0
x2go-DEBUG-../src/sshprocess.cpp:483> SSH finished: true - "; export PATH=/usr/local/bin:/usr/bin:/bin; export HOSTNAME
X2GODATAEND:7542493b-a84b-418d-994c-d640b3d91ef5;
" (0).
x2go-DEBUG-../src/onmainwindow.cpp:3458> "; export PATH=/usr/local/bin:/usr/bin:/bin; export HOSTNAME
X2GODATAEND:7542493b-a84b-418d-994c-d640b3d91ef5;
"
x2go-DEBUG-../src/onmainwindow.cpp:4289> No shadow session.
x2go-DEBUG-../src/onmainwindow.cpp:4312> "Decoding session string:; export PATH=/usr/local/bin:/usr/bin:/bin; export HOSTNAME"

On Jun 7, 2015, at 8:47 PM, Mihai Moldovan <ionic@ionic.de> wrote:

On 08.06.2015 01:44 AM, David Ritch wrote:
I was finally able to test this (had to work with IT department to have it
installed).  Unfortunately, it does not appear to fix the issue.  Now, when I
try to use Kerberos, I get a segfault.  I ran it with —debug, and captured the
output.  It’s here: https://dpaste.de/TOsT.

Thanks for your feedback!

The problem is that the returned string is halfway garbage. The client shouldn't
crash, but it looks like the parsing function isn't robust enough, that's a bug
of its own...

I'll have to setup a Kerberos test system to debug this.

The executed command(s) look alright and when I test manually on the command
line (changing PubkeyAuthentication=no to PubkeyAuthentication=yes and the
user/host values), it's executed flawlessly.



Mihai