Решено: Rx@etersoft server в мандрива 2010.0 (Решено)

[klarmir]

Помогите решить проблему. Имеем Мандрива повер пак 2010.0 и RX@etersoft terminal + Wine etersoft необходимоecнастроить файловый терминал.
Установка на новую систему с установленным сервером SSH.
Устанавливаю по инструкции wiki.etersoft.ru/RX
при выполнении инициализации окружения /etc/init.d/freenx-server setup получаем:
[root@OP2 ~]# /etc/init.d/freenx-server setup
------> It is recommended that you use the NoMachine key for
easier setup. If you answer "y", FreeNX creates a custom
KeyPair and expects you to setup your clients manually.
"N" is default and uses the NoMachine key for installation.

Do you want to use your own custom KeyPair? [y/N] ySetting up /etc/nxserver ...done
Setting up /var/lib/nxserver/db ...done
Setting up /var/log/nxserver.log ...done
Setting up known_hosts and authorized_keys2 ...done
Setting up permissions ...done
Setting up cups nxipp backend ...done

----> Testing your nxserver configuration ...
Warning: Invalid value "CUPS_ETC=/etc/cups/"
Users will not be able to enable printing.
Warning: Invalid value "COMMAND_START_CDE=cdwm"
Users will not be able to request a CDE session.
Warning: Invalid value "COMMAND_XTERM=xterm"
Users will not be able to request an xterm session.
Warning: Invalid value "COMMAND_SMBMOUNT=smbmount". You'll not be able to use SAMBA.
Warning: Invalid value "COMMAND_SMBUMOUNT=smbumount". You'll not be able to use SAMBA.
Warning: Invalid cupsd version of "/usr/sbin/cupsd". Need version 1.2.
Users will not be able to enable printing. Ignore if you use cups > 1.2

Warnings occured during config check.
To enable these features please correct the configuration file.

<---- done

----> Testing your nxserver connection ...
Permission denied (publickey,password,keyboard-interactive).
Fatal error: Could not connect to NX Server.

Please check your ssh setup:

The following are _examples_ of what you might need to check.

- Make sure "nx" is one of the AllowUsers in sshd_config.
(or that the line is outcommented/not there)
- Make sure "nx" is one of the AllowGroups in sshd_config.
(or that the line is outcommented/not there)
- Make sure your sshd allows public key authentication.
- Make sure your sshd is really running on port 22.
- Make sure your sshd_config AuthorizedKeysFile in sshd_config is set to authorized_keys2.
(this should be a filename not a pathname+filename)
- Make sure you allow ssh on localhost, this could come from some
restriction of:
-the tcp wrapper. Then add in /etc/hosts.allow: ALL:localhost
-the iptables. add to it:
$ iptables -A INPUT -i lo -j ACCEPT
$ iptables -A OUTPUT -o lo -j ACCEPT
[root@OP2 ~]# /etc/init.d/freenx-server setup
авторизация пользователей по системному паролю, удаленное подключение Етерсофтовским клиентом.
Как устранить фатальную ошибку

[dimbor]

[root@OP2 ~]# /etc/init.d/freenx-server setup
------> It is recommended that you use the NoMachine key for
easier setup. If you answer "y", FreeNX creates a custom
KeyPair and expects you to setup your clients manually.
"N" is default and uses the NoMachine key for installation.

Do you want to use your own custom KeyPair? [y/N] ySetting up /etc/nxserver ...done

Отвечаю по-еврейски вопросом на вопрос: Закрытый ключ от custom KeyPair на клиент отнесен?

[DjSpike]

Ты пользователя nx разблокировал ?
и покажи какие исправления делал в sshd.conf

[klarmir]

Ты пользователя nx разблокировал ?
и покажи какие исправления делал в sshd.conf

Код: Выделить всё

#    $OpenBSD: sshd_config,v 1.80 2008/07/02 02:24:18 djm Exp $

# This is the sshd server system-wide configuration file.  See
# sshd_config(5) for more information.

# This sshd was compiled with PATH=/usr/local/bin:/bin:/usr/bin

# The strategy used for options in the default sshd_config shipped with
# OpenSSH is to specify options with their default value where
# possible, but leave them commented.  Uncommented options change a
# default value.

Port 22
#AddressFamily any
#ListenAddress 0.0.0.0
#ListenAddress ::

# Disable legacy (protocol version 1) support in the server for new
# installations. In future the default will change to require explicit
# activation of protocol 1
Protocol 2

# HostKey for protocol version 1
#HostKey /etc/ssh/ssh_host_key
#HostKeys for protocol version 2
#HostKey /etc/ssh/ssh_host_rsa_key
#HostKey /etc/ssh/ssh_host_dsa_key

# Lifetime and size of ephemeral version 1 server key
#KeyRegenerationInterval 1h
#ServerKeyBits 1024

# Logging
# obsoletes QuietMode and FascistLogging
#SyslogFacility AUTH
#LogLevel INFO

# Authentication:

#LoginGraceTime 2m
#PermitRootLogin without-password
#StrictModes yes
#MaxAuthTries 6
#MaxSessions 10

#RSAAuthentication yes
PubkeyAuthentication yes
AuthorizedKeysFile    var/lib/nxserver/home/.ssh/authorized_keys
AllowUsers nx
# For this to work you will also need host keys in /etc/ssh/ssh_known_hosts
#RhostsRSAAuthentication no
# similar for protocol version 2
#HostbasedAuthentication no
# Change to yes if you don't trust ~/.ssh/known_hosts for
# RhostsRSAAuthentication and HostbasedAuthentication
#IgnoreUserKnownHosts no
# Don't read the user's ~/.rhosts and ~/.shosts files
#IgnoreRhosts yes

# To disable tunneled clear text passwords, change to no here!
#PasswordAuthentication yes
#PermitEmptyPasswords no

# Change to no to disable s/key passwords
#ChallengeResponseAuthentication yes

# Kerberos options
#KerberosAuthentication no
#KerberosOrLocalPasswd yes
#KerberosTicketCleanup yes
#KerberosGetAFSToken no

# GSSAPI options
#GSSAPIAuthentication no
#GSSAPICleanupCredentials yes

# Set this to 'yes' to enable PAM authentication, account processing,
# and session processing. If this is enabled, PAM authentication will
# be allowed through the ChallengeResponseAuthentication and
# PasswordAuthentication.  Depending on your PAM configuration,
# PAM authentication via ChallengeResponseAuthentication may bypass
# the setting of "PermitRootLogin without-password".
# If you just want the PAM account and session checks to run without
# PAM authentication, then enable this but set PasswordAuthentication
# and ChallengeResponseAuthentication to 'no'.
UsePAM no

# Accept locale-related environment variables
AcceptEnv LANG LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE LC_MONETARY LC_MESSAGES
AcceptEnv LC_PAPER LC_NAME LC_ADDRESS LC_TELEPHONE LC_MEASUREMENT
AcceptEnv LC_IDENTIFICATION LC_ALL

#AllowAgentForwarding yes
#AllowTcpForwarding yes
#GatewayPorts no
X11Forwarding yes
#X11DisplayOffset 10
#X11UseLocalhost yes
#PrintMotd yes
#PrintLastLog yes
#TCPKeepAlive yes
#UseLogin no
UsePrivilegeSeparation yes
#PermitUserEnvironment no
#Compression delayed
#ClientAliveInterval 0
#ClientAliveCountMax 3
#UseDNS yes
#PidFile /var/run/sshd.pid
#MaxStartups 10
#PermitTunnel no
#ChrootDirectory none

# no default banner path
#Banner none

# override default of no subsystems
Subsystem    sftp    /usr/lib/ssh/sftp-server

# Example of overriding settings on a per-user basis
#Match User anoncvs
#    X11Forwarding no
#    AllowTcpForwarding no
#    ForceCommand cvs server

Где не так. подправью

[DjSpike]

У тебя ошибка.
Должно быть так:

#RSAAuthentication yes
PubkeyAuthentication yes
AuthorizedKeysFile .ssh/authorized_keys2

P.S. Для оформления сообщений используй теги "код"

[klarmir]

У тебя ошибка.
Должно быть так:

#RSAAuthentication yes
PubkeyAuthentication yes
AuthorizedKeysFile .ssh/authorized_keys2

P.S. Для оформления сообщений используй теги "код"

У меня так было ошибка та-же
не пойму как ними пользоваться

[klarmir]

У тебя ошибка.
Должно быть так:

#RSAAuthentication yes
PubkeyAuthentication yes
AuthorizedKeysFile .ssh/authorized_keys2

P.S. Для оформления сообщений используй теги "код"

У меня так было счас вернул назад как ты написал
перезапустил sshd изменений нет

[DjSpike]

1) покажи вывод команды: # service sshd status
2) passwd -u -f nx
3) Скачай и поставь последнюю версию freenx ftp://ftp.etersoft.ru/pub/Etersoft/RX@Ete...0.1mdv.i586.rpm
4)отредактируй файл /etc/nxserver/node.conf.d/09-cups.conf | расскоментировав строчку ENABLE_KDE_CUPS="0"
5) покажи вывод команды nxsetup --test

p.s. все команды выполнять под рутом.

[klarmir]

1) покажи вывод команды: # service sshd status
2) passwd -u -f nx
3) Скачай и поставь последнюю версию freenx ftp://ftp.etersoft.ru/pub/Etersoft/RX@Ete...0.1mdv.i586.rpm
4)отредактируй файл /etc/nxserver/node.conf.d/09-cups.conf | расскоментировав строчку ENABLE_KDE_CUPS="0"
5) покажи вывод команды nxsetup --test

p.s. все команды выполнять под рутом.

Установил сервер выполнил манипуляции
/etc/init.d/freenx-server setup прошел на ура счас дальше пойду
Спасибо большое Будут проблемы свисну.