kde 4.4 with BOB's packages did /etc/kde/kdm/kdmrc get modified?

damgar · 02-27-2010, 11:57 PM

I was looking to post my kdmrc file in another thread regarding xdmcp. I did not recognize the file as the one I modified to enable xdmcp sessions. There are several files that appear as .new .old and the only thing I can thinkof, is that when I installed the 4.4 packages the file was replaced. But that is odd since xdmcp is normally disabled by defaut and I know that it is working on my system?

Also the form of the kdmrc file is much different from all of the kdmrc.new kdmr.old etc. files. Does anyone know what this is all about?

Alien Bob · 02-28-2010, 06:29 AM

The kdmrc file in the KDE 4.4 packages does not enable XDMCP by default. It has these lines:

Code:

[Xdmcp]
# Whether KDM should listen to incoming XDMCP requests.
# Default is true
Enable=false

Perhaps another program you recently installed came with a modified version of kdmrc?

Eric

damgar · 02-28-2010, 09:09 AM

Does the file that comes with 4.4 simply overwrite the existing kdmrc or is there some method in place to keep the current configuration?

Alien Bob · 02-28-2010, 10:30 AM

Quote:

Originally Posted by damgar

Does the file that comes with 4.4 simply overwrite the existing kdmrc or is there some method in place to keep the current configuration?

The kdebase-workspace package installs that file as

Code:

/etc/kde/kdm/kdmrc.new

so it will never just overwrite your current configuration.

Eric

damgar · 02-28-2010, 10:40 AM

Thanks. I'm not sure what has happened. I have this README in the /etc/kde/kdm directory

Code:

This automatically generated configuration consists of the following files:
- /usr/share/config/kdm/kdmrc
- /usr/share/config/kdm/Xaccess
- /usr/share/config/kdm/Xwilling
- /usr/share/config/kdm/Xsetup
- /usr/share/config/kdm/Xstartup
- /usr/share/config/kdm/Xreset
- /usr/share/config/kdm/Xsession
- /usr/share/config/kdm/backgroundrc
All files destined for /usr/share/config/kdm were actually saved in
/tmp/package-kdebase-workspace/usr/share/config/kdm; this config will not be
workable until moved in place.

This config was derived from existing files. As the used algorithms are
pretty dumb, it may be broken.
Information from these files was extracted:
- /etc/inittab

Try 'genkdmconf --help' if you want to generate another configuration.

You may delete this README.

And then kdmrc looks like

Code:

[General]
ConfigVersion=2.4
ConsoleTTYs=tty1,tty2,tty3,tty4,tty5,tty6
PidFile=/var/run/kdm.pid
ReserveServers=:1,:2,:3
ServerVTs=-7
StaticServers=:0

[Shutdown]
BootManager=None
HaltCmd=/sbin/halt
RebootCmd=/sbin/reboot

[X-*-Core]
AllowNullPasswd=false
AllowRootLogin=true
AllowShutdown=Root
AutoReLogin=false
ClientLogFile=.xsession-errors-%d
Reset=/usr/share/config/kdm/Xreset
Session=/usr/share/config/kdm/Xsession
SessionsDirs=/usr/share/config/kdm/sessions,/usr/share/apps/kdm/sessions
Setup=/usr/share/config/kdm/Xsetup
Startup=/usr/share/config/kdm/Xstartup

[X-*-Greeter]
AntiAliasing=false
ColorScheme=
FaceSource=AdminOnly
FailFont=Sans Serif,10,-1,5,75,0,0,0,0,0
ForgingSeed=1261021638
GUIStyle=
GreetFont=Serif,20,-1,5,50,0,0,0,0,0
GreetString=Welcome to %s at %n
GreeterPos=50,50
HiddenUsers=
Language=en_US
LogoArea=Logo
LogoPixmap=/usr/share/apps/kdm/pics/kdelogo.png
MaxShowUID=65000
MinShowUID=500
Preloader=/usr/bin/preloadkde
SelectedUsers=
ShowUsers=NotHidden
SortUsers=true
StdFont=Sans Serif,10,-1,5,50,0,0,0,0,0
Theme=/usr/share/apps/kdm/themes/Elegant-Air_KDM
UseBackground=true
UseTheme=true
UserCompletion=false
UserList=true

[X-:*-Core]
AllowNullPasswd=true
AllowShutdown=All
NoPassEnable=false
NoPassUsers=
ServerArgsLocal=-nolisten tcp
ServerCmd=/usr/bin/X -br -novtswitch -quiet

[X-:*-Greeter]
AllowClose=false
DefaultUser=dtest
FocusPasswd=true
LoginMode=DefaultLocal
PreselectUser=Previous

[X-:0-Core]
AutoLoginEnable=false
AutoLoginLocked=false
AutoLoginUser=
ClientLogFile=.xsession-errors

[Xdmcp]
Willing=/usr/share/config/kdm/Xwilling

and I'm just not sure how I got there, unless it was when I used the kde tools to change the greeter screen, but that seems like a lot of ediiting for such a simple change. I guess the thing to do is change the current file to one of known origin and monitor the situation. I don't see any obvious security risks greater than enabling xdmcp to begin with. It's quite odd.