One of my customers found that if he used a clean PATH and did not
change it in his .profile he could connect. Then I determined which
directories included in the PATH made it fail, and then he realized those
directories would be prohibited if perl was run tainted, and he knew enough
about monkeysphere to know it would do this. So we took the start up out
of the X2Go Xession directory and that made it work.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting.
Knowledgeable human assistance, not telephone trees or script readers.
See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.
On Sun, 25 Mar 2018, John Stoffel wrote:
Date: Sun, 25 Mar 2018 19:32:38 -0400
From: John Stoffel <j...@stoffel.org>
To: Robert Dinse <nan...@eskimo.com>
Cc: "x2go-user@lists.x2go.org" <x2go-user@lists.x2go.org>
Subject: Re: [X2Go-User] MxLinux
"Robert" == Robert Dinse <nan...@eskimo.com> writes:
Robert> Found the issue with MxLinux, had monkeysphere
Robert> installed, it causes perl to be called with the -T flag, and
Robert> this made having insecure directories such as /etc or '.' in
Robert> your $PATH problematic.
So how did you debug this? Did you find the problem in the x2go logs?
Or somewhere else? Please share your expertise, since it's a pain to
debug otherwise.
_______________________________________________
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user
