Bug 218178

Summary: YAST's Remote Administration not accessible
Product: [openSUSE] openSUSE 10.2 Reporter: Forgotten User Drfk9mafMw <forgotten_Drfk9mafMw>
Component: YaST2Assignee: E-mail List <bnc-team-screening>
Status: RESOLVED FIXED QA Contact: Jiri Srain <jsrain>
Severity: Normal    
Priority: P5 - None    
Version: Beta 1   
Target Milestone: ---   
Hardware: i686   
OS: Other   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: I'm not sure if the log contains the proper info since I haven't been able to test Remote Administration for some time now...

Description Forgotten User Drfk9mafMw 2006-11-04 16:48:05 UTC
Enabling "Remote Administration" service in YAST > Network Services will not allow for remote access to display since the VNC client asks for a password but there has never one been set in the first place (and afaik there is no password protection at all for this feature itself).

Please check, that this service doesn't allow for remote shutdown by anybody else than root by default (no matter what security profile has been chosen), as I had to learn with bug 206676.
Comment 1 Matej Horvath 2006-11-09 11:54:43 UTC
Could you attach the YaST logs, please?

http://en.opensuse.org/Bugs/YaST
Comment 2 Forgotten User Drfk9mafMw 2006-11-09 22:21:19 UTC
Created attachment 104581 [details]
I'm not sure if the log contains the proper info since I haven't been able to test Remote Administration for some time now...
Comment 3 Forgotten User Drfk9mafMw 2006-11-12 14:45:18 UTC
I have just finished the installation of Beta 2 via network and enabled both Remote Administration in YAST and the X-sharing with sax. Both work as expected! Port 5900 asks for the password and shows the running X session, 5901 displays the login screen.

It seems that this bug can be considered resolved and closed.
Comment 4 Cyril Hrubis 2006-11-14 12:16:55 UTC
Looks like bug is already fixed in beta 2.
Comment 5 Forgotten User Drfk9mafMw 2006-11-14 12:20:00 UTC
Yes, I think so, too. Can't find no more problems with this on Beta2.