[Bug 390478] New: VNC - persistent session is not possible - "wait = yes" is not working - openSUSE Bugs

[Bug 390478] New: VNC - persistent session is not possible - "wait = yes" is not working

bugzilla_noreply＠novell.com

14 May 2008 14 May '08

21:11

https://bugzilla.novell.com/show_bug.cgi?id=390478 Summary: VNC - persistent session is not possible - "wait = yes" is not working Product: openSUSE 11.0 Version: Factory Platform: x86-64 OS/Version: openSUSE 11.0 Status: NEW Severity: Blocker Priority: P5 - None Component: X11 Applications AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: vodicka.petr@email.cz QAContact: sndirsch@novell.com Found By: Beta-Customer Hi, I want to connect to my OpenSUSE 11 pc via VNC, but I need to leave session opened after disconnect. This can be done with "wait = yes" argument in xinetd vnc configuration (/etc/xinet.d/vnc) and it's working in OpenSUSE 10.3, but not in OpenSUSE 11. Client just creates connection on TCP/IP (only 3 packets visible in Wireshark) and then nothing is happening on client side, just waiting. But on server side is happening something weird. Xvnc process starts, but dies immediately and another starts again. This is happening hundreds times per second. This is my configuration: service vnc2 { socket_type = stream protocol = tcp wait = yes user = nobody server = /usr/bin/Xvnc server_args = -inetd -once -query localhost -geometry 1024x768 -depth 16 type = UNLISTED port = 5902 } If I change "wait = yes" to "wait = no", connection is working, but persistent session not (as it should with this configuration). Than you for your time, Petr -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

Show replies by date

bugzilla_noreply＠novell.com

14 May 14 May

21:24

New subject: [Bug 390478] VNC - persistent session is not possible - "wait = yes" is not working

https://bugzilla.novell.com/show_bug.cgi?id=390478 User vodicka.petr@email.cz added comment https://bugzilla.novell.com/show_bug.cgi?id=390478#c1 --- Comment #1 from Petr Vodicka 2008-05-14 15:24:55 MST --- This is part of my xinetd.log: 08/5/14@21:52:06: START: vnc2 from=<no address> 08/5/14@21:52:06: EXIT: vnc2 signal=13 duration=0(sec) 08/5/14@21:52:06: START: vnc2 from=<no address> 08/5/14@21:52:06: EXIT: vnc2 signal=13 duration=0(sec) 08/5/14@21:52:06: START: vnc2 from=<no address> 08/5/14@21:52:06: EXIT: vnc2 signal=13 duration=0(sec) 08/5/14@21:52:06: START: vnc2 from=<no address> 08/5/14@21:52:06: EXIT: vnc2 signal=13 duration=0(sec) 08/5/14@21:52:06: START: vnc2 from=<no address> 08/5/14@21:52:06: EXIT: vnc2 signal=13 duration=0(sec) 08/5/14@21:52:06: START: vnc2 from=<no address> 08/5/14@21:52:06: EXIT: vnc2 signal=13 duration=0(sec) 08/5/14@21:52:06: START: vnc2 from=<no address> 08/5/14@21:52:06: EXIT: vnc2 signal=13 duration=0(sec) 08/5/14@21:52:06: START: vnc2 from=<no address> 08/5/14@21:52:06: EXIT: vnc2 signal=13 duration=0(sec) 08/5/14@21:52:06: START: vnc2 from=<no address> 08/5/14@21:52:06: EXIT: vnc2 signal=13 duration=0(sec) 08/5/14@21:52:06: START: vnc2 from=<no address> 08/5/14@21:52:06: EXIT: vnc2 signal=13 duration=0(sec) 08/5/14@21:52:06: START: vnc2 from=<no address> 08/5/14@21:52:06: EXIT: vnc2 signal=13 duration=0(sec) 08/5/14@21:52:06: START: vnc2 from=<no address> 08/5/14@21:52:06: EXIT: vnc2 signal=13 duration=0(sec) 08/5/14@21:52:06: START: vnc2 from=<no address> 08/5/14@21:52:06: EXIT: vnc2 signal=13 duration=0(sec) 08/5/14@21:52:06: START: vnc2 from=<no address> 08/5/14@21:52:06: EXIT: vnc2 signal=13 duration=0(sec) 08/5/14@21:52:06: START: vnc2 from=<no address> 08/5/14@21:52:06: EXIT: vnc2 signal=13 duration=0(sec) 08/5/14@21:52:06: START: vnc2 from=<no address> 08/5/14@21:52:06: EXIT: vnc2 signal=13 duration=0(sec) 08/5/14@21:52:06: START: vnc2 from=<no address> 08/5/14@21:52:06: EXIT: vnc2 signal=13 duration=0(sec) 08/5/14@21:52:06: START: vnc2 from=<no address> 08/5/14@21:52:06: EXIT: vnc2 signal=13 duration=0(sec) 08/5/14@21:52:06: START: vnc2 from=<no address> 08/5/14@21:52:06: EXIT: vnc2 signal=13 duration=0(sec) 08/5/14@21:52:06: START: vnc2 from=<no address> 08/5/14@21:52:06: EXIT: vnc2 signal=13 duration=0(sec) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

22:22

New subject: [Bug 390478] VNC - persistent session is not possible - "wait = yes" is not working

https://bugzilla.novell.com/show_bug.cgi?id=390478 User sndirsch@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=390478#c2 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |DUPLICATE --- Comment #2 from Stefan Dirsch 2008-05-14 16:22:06 MST --- *** This bug has been marked as a duplicate of bug 385677 *** https://bugzilla.novell.com/show_bug.cgi?id=385677 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

31 May 31 May

12:22

New subject: [Bug 390478] VNC - persistent session is not possible - "wait = yes" is not working

https://bugzilla.novell.com/show_bug.cgi?id=390478 User vodicka.petr@email.cz added comment https://bugzilla.novell.com/show_bug.cgi?id=390478#c3 Petr Vodicka changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|DUPLICATE | --- Comment #3 from Petr Vodicka 2008-05-31 06:22:58 MDT --- Bug is not solved. I have upgraded OpenSUSE 11 to RC1 and then to Factory version and still same bahaviour. Only xinetd.log changed slightly. 08/5/31@12:56:46: START: vnc2 from=<no address> 08/5/31@12:56:47: EXIT: vnc2 status=0 duration=1(sec) 08/5/31@12:56:47: START: vnc2 from=<no address> 08/5/31@12:56:47: EXIT: vnc2 status=0 duration=0(sec) 08/5/31@12:56:47: START: vnc2 from=<no address> 08/5/31@12:56:47: EXIT: vnc2 status=0 duration=0(sec) 08/5/31@12:56:47: START: vnc2 from=<no address> 08/5/31@12:56:47: EXIT: vnc2 status=0 duration=0(sec) 08/5/31@12:56:47: START: vnc2 from=<no address> 08/5/31@12:56:47: EXIT: vnc2 status=0 duration=0(sec) 08/5/31@12:56:47: START: vnc2 from=<no address> 08/5/31@12:56:48: EXIT: vnc2 status=0 duration=1(sec) 08/5/31@12:56:48: START: vnc2 from=<no address> 08/5/31@12:56:48: EXIT: vnc2 status=0 duration=0(sec) 08/5/31@12:56:48: START: vnc2 from=<no address> 08/5/31@12:56:48: EXIT: vnc2 status=0 duration=0(sec) 08/5/31@12:56:48: START: vnc2 from=<no address> 08/5/31@12:56:48: EXIT: vnc2 status=0 duration=0(sec) 08/5/31@12:56:48: START: vnc2 from=<no address> 08/5/31@12:56:48: EXIT: vnc2 status=0 duration=0(sec) 08/5/31@12:56:48: START: vnc2 from=<no address> 08/5/31@12:56:48: EXIT: vnc2 status=0 duration=0(sec) 08/5/31@12:56:48: START: vnc2 from=<no address> 08/5/31@12:56:49: EXIT: vnc2 status=0 duration=1(sec) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

19:22

New subject: [Bug 390478] VNC - persistent session is not possible - "wait = yes" is not working

https://bugzilla.novell.com/show_bug.cgi?id=390478 Stephan Kulow changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Blocker |Major Flag| |SHIP_STOPPER- -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

2 Jun 2 Jun

13:27

New subject: [Bug 390478] VNC - persistent session is not possible - "wait = yes" is not working

https://bugzilla.novell.com/show_bug.cgi?id=390478 Robert Vojcik changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |sndirsch@novell.com Status|REOPENED |NEW -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

14:12

New subject: [Bug 390478] VNC - persistent session is not possible - "wait = yes" is not working

https://bugzilla.novell.com/show_bug.cgi?id=390478 User sndirsch@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=390478#c4 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sndirsch@novell.com AssignedTo|sndirsch@novell.com |max@novell.com --- Comment #4 from Stefan Dirsch 2008-06-02 08:12:16 MDT --- Indeed I can reproduce this issue with RC1. Reinhard, can you investigate? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

13 Aug 13 Aug

16:17

New subject: [Bug 390478] VNC - persistent session is not possible - "wait = yes" is not working

https://bugzilla.novell.com/show_bug.cgi?id=390478 User max@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=390478#c6 Reinhard Max changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #6 from Reinhard Max 2008-08-13 10:17:21 MDT --- 10.3 and 11.0 use entirely different implementations for Xvnc. The one in 10.3 contains code to make it work with wait=yes, the one in 11.0 does not. I think supporting wait=yes would defeat the purpose of the -inetd switch to allow an arbitrary number of on-the-fly generated one-shot vnc sessions. It would even be a security risk, because vnc sessions created through xinetd are not password protected. A user who disconnects from such a session without explicitly locking it at the X level would leave it open for an attacker. You can use the vncserver script from the tightvnc package or call Xvnc directly to start persistent vnc sessions that are independent of xinetd. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

16 Aug 16 Aug

18:09

New subject: [Bug 390478] VNC - persistent session is not possible - "wait = yes" is not working

https://bugzilla.novell.com/show_bug.cgi?id=390478 User vodicka.petr@email.cz added comment https://bugzilla.novell.com/show_bug.cgi?id=390478#c7 --- Comment #7 from Petr Vodicka 2008-08-16 12:09:33 MDT --- :( Easy way how to solve bug... I don't agree with you. Connection to vnc can be easily secured with password. Just rfbauth argument must be added. So I dont think that it's security risk. If I use tightvnc script It only starts plain X with xterm in default, so use xinetd was the easiest way how to start Xvnc with KDE running. Yes, I can change xstartup script to start xinitrc script, but it's not easy to find this solution on internet. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

18 Aug 18 Aug

14:56

New subject: [Bug 390478] VNC - persistent session is not possible - "wait = yes" is not working

https://bugzilla.novell.com/show_bug.cgi?id=390478 User max@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=390478#c8 --- Comment #8 from Reinhard Max 2008-08-18 08:56:36 MDT --- (In reply to comment #7 from Petr Vodicka)

...

:( Easy way how to solve bug...

It's not a bug, it's just a (from our side) unintended feature that is gone again, but we are open for patches to re-add it.

...

Connection to vnc can be easily secured with password. Just rfbauth argument must be added. So I dont think that it's security risk.

Right, I oversaw that part. OTOH, that would have to be a per-system VNC password, while normally VNC passwords are per user. And still, doing this all would defeat the purpose of the whole xinetd based setup.

...

If I use tightvnc script It only starts plain X with xterm in default, so use xinetd was the easiest way how to start Xvnc with KDE running. Yes, I can change xstartup script to start xinitrc script, but it's not easy to find this solution on internet.

You can also just start Xvnc by hand and use the -query option to get a persistent session with KDM login screen: Xvnc :1 -query localhost -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

21 Aug 21 Aug

15:55

New subject: [Bug 390478] VNC - persistent session is not possible - "wait = yes" is not working

https://bugzilla.novell.com/show_bug.cgi?id=390478 User vodicka.petr@email.cz added comment https://bugzilla.novell.com/show_bug.cgi?id=390478#c9 --- Comment #9 from Petr Vodicka 2008-08-21 09:55:39 MDT --- (In reply to comment #8 from Reinhard Max)

...

(In reply to comment #7 from Petr Vodicka)

...
:( Easy way how to solve bug...

It's not a bug, it's just a (from our side) unintended feature that is gone again, but we are open for patches to re-add it.

Sorry, I was looking on that from wrong side. I appreciate your work you made for us.

...

...
Connection to vnc can be easily secured with password. Just rfbauth argument must be added. So I dont think that it's security risk.

Right, I oversaw that part. OTOH, that would have to be a per-system VNC password, while normally VNC passwords are per user. And still, doing this all would defeat the purpose of the whole xinetd based setup.

You are right. Per-user password is not secure enough.

...

...
If I use tightvnc script It only starts plain X with xterm in default, so use xinetd was the easiest way how to start Xvnc with KDE running. Yes, I can change xstartup script to start xinitrc script, but it's not easy to find this solution on internet.

You can also just start Xvnc by hand and use the -query option to get a persistent session with KDM login screen:

Xvnc :1 -query localhost

Thank you for your advice. It's so easy, but I was unable to find it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

5735

Age (days ago)

5834

Last active (days ago)

List overview

Download

10 comments

1 participants

participants (1)

bugzilla_noreply＠novell.com

[Bug 390478] New: VNC - persistent session is not possible - "wait = yes" is not working

tags

participants (1)