Shulou(Shulou.com)06/01 Report--

This article is about how Xmanager connects to the linux 5 configuration. The editor thinks it is very practical, so share it with you as a reference and follow the editor to have a look.

Redhat as 5 is configured with root users over xmanager connections

First, XMANAGER connection to REDHAT AS 5 needs to be modified.

The difference between rhel5 and rhel4 is that there is no directory / etc/X11/gdm/ in rhel5, and the configuration file of rhel5's gdm is put here / usr/share/gdm/defaults.comf, which may be troubling you.

Make sure the following sentences are configured in / usr/share/gdm/defaults.conf:

Enable=true

DisplaysPerHost=10

Port=177

Change the default level to 5 in / etc/inittab:

Id:5:initdefault:

Add one more sentence to this document:

X:5:respawn:/usr/bin/gdm

Then restart the system. Then run the Xbrowser program in xmanager2 on the windows system, create a new Xmanager Session in the console, enter the ip address here in Host, and do not change any other configurations (including port number). Be sure to exit. Then double-click the New Xmanager Session to see the login screen:

2. If you allow Root users to connect to XMANAGER, you need to modify the following:

# vi defaults.conf

[security]

# Allow root to login. It makes sense to turn this off for kiosk use, when

# you want to minimize the possibility of break in.

AllowRoot=true

# Allow login as root via XDMCP. This value will be overridden and set to

# false if the / etc/default/login file exists and contains

# "CONSOLE=/dev/login", and set to true if the / etc/default/login file exists

# and contains any other value or no value for CONSOLE.

AllowRemoteRoot=true

# This will allow remote timed login.

AllowRemoteAutoLogin=false

# 0 is the most restrictive, 1 allo

# vi / etc/securetty

.

Tty2

Tty3

Tty4

Tty5

Tty6

Tty7

Tty8

Tty9

Tty10

Tty11

Pts/0

Pts/1

Pts/2

Pts/3

Pts/4

Add these.

# vi / etc/pam.d/login

#% PAM-1.0

# auth [user_unknown=ignore success=ok ignore=ignore default=bad] pam_securetty.so

Auth include system-auth

Account required pam_nologin.so

Account include system-auth

Password include system-auth

# pam_selinux.so close should be the first session rule

Session required pam_selinux.so close

Session include system-auth

Session required pam_loginuid.so

Session optional pam_console.so

# pam_selinux.so open should only be followed by sessions to be executed in the user context

Session required pam_selinux.so open

Session optional pam_keyinit.so force revoke

~

# vi / etc/pam.d/remote

#% PAM-1.0

# auth required pam_securetty.so

Auth include system-auth

Account required pam_nologin.so

Account include system-auth

Password include system-auth

# pam_selinux.so close should be the first session rule

Session required pam_selinux.so close

Session include system-auth

Session required pam_loginuid.so

Session optional pam_console.so

# pam_selinux.so open should only be followed by sessions to be executed in the user context

Session required pam_selinux.so open

Session optional pam_keyinit.so force revoke

~

~

# vi / etc/xinetd.d/telnet

# default: on

# description: The telnet server serves telnet sessions; it uses\

# unencrypted username/password pairs for authentication.

Service telnet

{

Flags = REUSE

Socket_type = stream

Wait = no

User = root

Server = / usr/sbin/in.telnetd

Log_on_failure + = USERID

Disable = no

}

~

~

Thank you for reading! This is the end of this article on "how to connect Xmanager to linux 5 configuration". I hope the above content can be of some help to you, so that you can learn more knowledge. if you think the article is good, you can share it for more people to see!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.