jimmycrapcorn / neatx

Automatically exported from code.google.com/p/neatx
0 stars 0 forks source link

nxserver-login: error: no such option: -c #6

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. compile & install with --prefix=/usr
2. create user nx (getent passwd nx
nx:x:129:65:NX System
User:/var/lib/nxserver/home/:/usr/lib/neatx/nxserver-login-wrapper)
3. try with original nxclient 3.3.0-6

What is the expected output? What do you see instead?
"nxserver-login: error: no such option: -c" in syslog

What version of the product are you using? On what operating system?
neatx svn rev9

Original issue reported on code.google.com by boris.sa...@gmail.com on 9 Jul 2009 at 8:03

GoogleCodeExporter commented 8 years ago
change shell to /bin/sh
create symlink from /usr/lib/neatx/nxserver-login-wrapper to /usr/bin/nxserver

works perfectly!
But not secure with shell /bin/sh in nx user-(

Original comment by boris.sa...@gmail.com on 9 Jul 2009 at 9:01

GoogleCodeExporter commented 8 years ago
this seems like a bad solution all over.
could you give us more information regarding the distribution you're using and
versions of nx-agent and other related information?

Original comment by robert.r...@gmail.com on 9 Jul 2009 at 11:38

GoogleCodeExporter commented 8 years ago
distribution altlinux (www.altlinux.org)
nx -- latest with some pathes ( rpm spec
http://git.altlinux.org/people/boris/packages/?p=nx.git;a=blob;f=nx.spec;h=85609
9cb15f1c98e920ebfda8a2debc369bbf2ca;hb=HEAD)

some changes in constans.py for ALT
http://git.altlinux.org/people/boris/packages/?p=neatx.git;a=commitdiff;h=f704f5
273fdb892aaf09df1c88879e04b981d0ed

config like this --
http://git.altlinux.org/people/boris/packages/?p=neatx.git;a=blob;f=neatx.conf;h
=2075608da7119c534a7a0958c443ec8f5ee07559;hb=HEAD

neatx configure string (generate by rpmbuild):
./configure --build=i586-alt-linux --host=i586-alt-linux --prefix=/usr
--exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc
--datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib
--libexecdir=/usr/lib --localstatedir=/var/lib --sharedstatedir=/usr/com
--mandir=/usr/share/man --infodir=/usr/share/info --disable-dependency-tracking
--without-included-gettext --localstatedir=/var

directory /var/lib/neatx/sessions have perm 2770 for secure and all needed 
users in
group nx.
world writable directory /var/lib/neatx/sessions is not a good idea i think...
perm 777 cant resolve this issue.
sorry for english-(

Original comment by boris.sa...@gmail.com on 9 Jul 2009 at 11:51

GoogleCodeExporter commented 8 years ago
original nxclient 3.3.0-6 for linux, i forgot
( http://www.nomachine.com/download-client-linux.php )

Original comment by boris.sa...@gmail.com on 9 Jul 2009 at 11:54

GoogleCodeExporter commented 8 years ago
I modify /usr/lib/neatx/nxserver-login-wrapper:
 # Duplicate stdout to fd 3
 exec 3>&1
+echo $@ > `mktemp -p /tmp`
 exec /usr/lib/neatx/nxserver-login "$@" 2>&1 >&3 | {

and look at result
cat /tmp/tmp.qzXTGsSoKF
-c /usr/bin/nxserver

may be it help

Original comment by boris.sa...@gmail.com on 9 Jul 2009 at 12:03

GoogleCodeExporter commented 8 years ago
Apparently sshd passes -c to the shell to run a command specified by the client 
(I
couldn't explain why, but that's what it looks like). nxserver-login could just
ignore it by implementing "-c" in neatx.app.NxServerLoginProgram.BuildOptions 
(see
nxserver.NxServer.BuildOptions for reference). The wrapper is generated and 
shouldn't
contain special cases.

Original comment by ims...@gmail.com on 9 Jul 2009 at 12:17

GoogleCodeExporter commented 8 years ago
solved for me
i have authorized_keys2 from freenx installation. its contains:
no-port-forwarding,no-agent-forwarding,command="/usr/bin/nxserver" ...

after replace my authorized_keys2 with neatx authorized_keys error dont 
reproduce.

unfortunately neatx authorized_keys not compat with freenx authorized_keys... 
think
about it-))

Original comment by boris.sa...@gmail.com on 9 Jul 2009 at 3:00

GoogleCodeExporter commented 8 years ago
That's unfortunate alright - however due to how nxclient expects to connect to 
the
server (via the nx user), there will always be conflicts between using 
different nx
servers. All of them (!M's nxserver, FreeNX, Neatx) all depend on setting the nx
user's shell, for example.

Thanks for hunting this down, i expect that will help other people in the 
future.

Original comment by kormat on 9 Jul 2009 at 7:23